you can't bait and switch me with xt. try and trick me to use a client because you are currently using my blockchain then switch to your own blockchain and expect to keep me using the client. anything that is scheduled to become an altcoin in the future is already an altcoin. xt is not bitcoin.
using your logic then that means
the current bitcoin (core) is an altcoin as it is vastly different than the original bitcoin satoshi released in 2009.
Logic fail. LOL!
Therefore Bitcoin core is not Bitcoin right?
Nope, logic win:
Activating a hardfork based on what miners do is really bad. You could easily have a situation where 75% of miners support XT but none of the big Bitcoin exchanges or businesses do. Then miners would start mining coins that they couldn't spend anywhere useful, and SPV users would find that they can't transact with the businesses they want to deal with. The currency would be split, and in this case XT would be in a far weaker position than Bitcoin.
The possibility of this sort of network/currency split is what makes XT not a "legitimate hardfork", but rather the programmed creation of an altcoin. A consensus hardfork can only go forward once it has been determined that it's nearly impossible for the Bitcoin economy to split in any significant way. Not every Bitcoin user on Earth has to agree, but enough that there won't be a noticeable split.
Bitcoin is not ruled by miners. In a hardfork, miners barely matter at all. (Softforks are different.) What's important is what the economy does.
LOL!
What Heam doesn't want you to know about XT:
https://www.reddit.com/r/Bitcoin/comments/3h5heu/so_what_exactly_are_the_changes_in_bitcoinxt/ In Core, several committers and usually a few other people eyeball the changes; does XT have that attention yet? I don't know enough on the patched functionality to give a useful opinion, but I strongly believe people should look closely at what's getting in under the radar here.
a bug fix
If "relay the first observed double spend" were generally accepted as a bug with a clean fix available, it'd be fixed in Core; superficial searching says it got reverted as problematic and contentious but I don't know the whole story, nor do I have an opinion on the change.
two minor things
One is for Hearn's Lighthouse project, and also got merged, found buggy, and reverted. Without those eyeballs, would the lack of testing have been addressed and the bug in getutxos have been spotted before it was widely rolled out?
The other is adding back the bitnodes seed node that was removed for behaving in fishy ways, and adding a seed run by Mike that (unlike any others) gets to know the connecting node's IP address (which would never be accepted into Core).
Is XT basically going to be every patch Mike Hearn ever had refused by NACKs in Core? Where does that road take you as a user of XT?
Edit: Conspicuous by its absence from the README is that (AFAICT from the commit comment) incoming clearnet connections will kick a Tor peer off. /u/luke-jr pointed this out below. So don't just trust the description of diffs.
Good luck with your NACKcoin, full of buggy/shitty ideas Heam couldn't get through the rigorous BIP process!
LOL!