I still don't get how evan could make this revert-decision based on a non-stabilized environment with massive entropy, just one hour after a hard fork. I mean, you devs did expect orphans and concurrent blocks after a hard fork, dint't you?
I'm a bit concerned. This is why.
I'm binge-watching The Walking Dead until the dust settles.
Agreed. Doesn't make sense. I get that it took "too long" - however, the case that 25% of the network didn't update and thus were creating forks - isn't this okay ....isn't that an edge case that won't happen often?