Cypherdoc's thread was locked after the discussion turned heavily towards XT. A Forum Administrator claimed the reason for locking the thread was that it was too broad in scope, so maybe you won't count this as "punished here for mentioning XT":
https://bitcointalksearch.org/topic/m.12199651
-snip-
Definitely, not! The thread was about Gold vs Bitcoin and thread was filled with XT discussions. You do know that off-topic posts are against forum rules, right? You are acting like a stupid person to support XT and you don't strike me as a fool, Peter!
Let me make my position clear:
(1) I view the block size limit as an anti-spam measure and I support increasing it.
(2) I believe Bitcoin's greatest point of centralization is presently in development and I support measures to reduce this centralization.
By supporting XT, I help push for both larger block sizes and help move us away from our dependency on Bitcoin Core.
If another credible team forks Bitcoin Core into a third implementation that also supports larger blocks, I will support that implementation too.
Peter, the way you're biting every worm Hearn casts toward you is very disturbing.
This newly created issue of "developer centralization" is completely disingenuous and grounded in plain ignorance. Of course I am especially tired of seeing you rehashing the same tired concern (I imagine that's how GMax felt when you kept publicly supporting the false and misguiding conclusions of your paper) so allow me to quote myself again.
The centralization issue you refer to is nothing more than a lack of man power. That is, only a scarce amount of people are reliable and technically able enough to handle the highly fragile development of Bitcoin. It is no wonder the guys currently leading core are some of the world's most advanced experts in their own field. This expertise cannot be easily replaced or dismissed "because decentralization". It is absolutely unproductive and irresponsible to try to advance decentralization of Bitcoin development by encouraging incapable people to start messing around with their own implementations and risk breaking consensus.