So, how do you prevent that from basically being the same as "everyone flip a coin?", I'm not sure what kind of guidance you could usefully give there.
"Everyone" would know which is the real chain. It is saying that the rule in that case is that it requires manual discussion.
You need to go to forums etc to say which is the "real" chain.
Quote
I might, with enough effort and thinking into how you do something useful with the instructions there be convinced that there could be something useful along those lines— or at least, no more harmful than any other rearrangement of the titanic's deckchairs— but then there is the issue of if someone has enough computing power to create a 10k reorg, the could constantly reorg 9999 blocks over and and over again. "This isn't any better".
Maybe they are willing to do it once, but not over and over. In fact, maybe even 10k is to high, perhaps the node could auto-checkpoint all blocks that are at least 24 hours old.
A 24 hour reversal inherently requires manual intervention.
You connect daily and your client tells you a reversal has happened and manual intervention is required.
95% of users would be on the historical chain. The reversal would have to be short to not trigger the warning.
), doublespends that require immense hashrates should not be a concern for you at all (unless you happen to be good at making enemies among major pool operators 
) 
