Erm, it's showing on both.

http://monerochain.info/tx/e977b3ba1a9bee5e6f1d1164f75a7e1ab3f72607536934beb3d813a71f64bc3e

http://chainradar.com/xmr/transaction/e977b3ba1a9bee5e6f1d1164f75a7e1ab3f72607536934beb3d813a71f64bc3e

i agree, insinuating that the devs of bbr had a hand in this attack is pretty low life with out any facts..

CZ is an excelent dev so it is not so hard to believe that he could find a solution so fast.

So, i have time to calmly research the problem.

Noobish question: Does all this new information mean that this "tx-fork bug" only caused a simple -not very enduring- fork? That's all it did? If so, is that a major problem, or simply something that can be fixed easily?

My gut! This will be MOON (with capital letters) for boolberry!

Monero devs should act as fast as possible.

Zoidberg admitted to having the same weakness in Boolberry.

you forgot to mention the part where he says he can mitigate an attack because it takes so long and that a solution has already be thought of.

Bad news is that Boolbery also have this flaw. (Like every Cryptonote).
Good news - that this attack need pretty long period of preparation, because to achive big amount of transactions per block attackers need to move median, it's a day or more. That means that even if i see that attack is starting i have enought time to update network with workaround rule, that won't let grow transactions count per block too much to fail.