Why couldn't one of the core developers simply include the 8mb code into the core and publish it? Did the blockstream developers block that from happening? Then gavin should have done this and create his own fork and not join forces with hearn and his dangerous ideas.
Because bitcoin community is smart enough to check bitcoinXT source code and see there is nothing "dangerous"Dont let the anti big blockers smear BS on your judgment.
OpenSSL has been open source for years and years and years...
This is a good point. The simple fact that anyone CAN check the source code and find critical bugs is, as the openssl clusterfuck showed, not a sufficient guarantee that enough competent people WILL check the source code and find critical bugs.
Of course, that caveat applies equally well to both XT and Core.
indeed. however, one aspect that comes into play here is a more rigorous auditing/testing process for pulls. the fact that the XT code was primarily peer-reviewed by one person before it was released was reason enough never to run it.
indeed, Peter Todd exhibited this point well when he pointed out this bug in an XT patch:
https://www.reddit.com/r/Bitcoin/comments/3kenp1/stress_test_commence_as_of_now_were_seeing_23/cuwxvbzYour mempool limiting technique creates a cheap network bandwidth DoS attack.
The problem is Gavin's patch evicts random transactions (and their descendants) from the mempool without regard to what fees anything paid; in Bitcoin we use paying fees to limit DoS attacks, so anytime a transaction can be broadcast without having a high probability of eventually paying the fee is very bad. Evicted transactions aren't recorded, so if a peer rebroadcasts them to you you'll redownload them. Equally that makes up a bunch of space for different rebroadcasted transactions respending UTXO's that were previously spent. Either way, bandwidth is being used that isn't being paid for.
This is all very well known stuff, and dealing with it is most of the reason why Core is actively working towards implementing a mempool sorted by fees. That you quickly merged Gavin's patch is a sign you don't have much peer review, given that a multiple simpler, working, alternatives exist if you just want something fast to implement. (e.g. the feerate tier idea discussed on IRC/github)
Yeah, tinfoil hat. But i don't understand his stupid acts otherwise.
....(hint: both are the same) 
