two things to note.
1, advocating for methods of sybil attacking is not a good way to go(one person running more then one node for no other purpose then to skew stats)
it doesnt matter if its a core fanboy or a classic fanboy. both parties should not try sybil attacks. or ddos, or transaction spam attacks

2. though classic is one implementation. there is alot of background drama involved. so what could be done better is to get the programmers of bitcoinj, btcd, and the other main implementations to go for 2mb aswell. and find a way to get blockstream to come to their senses to have 2mb aswell.

things like debunking the 12month grace hard fork contention argument, by using luke jr's proposal of a different hard fork(difficulty drop) that he feels can happily become active in 3 months after code release.(if luke thinks 3months is acceptable. then no reason to go for 12, if luke wants hiscode in april then 2mb can be in april too)

things like debunking validation issues by highlighting that libsecp256k1 offers 5x validation speeds. making total of 10,000 signatures validate in april 2016, in the same time it takes 2000 signatures to validate in january 2016. thus allowing for more then a small bit of growth

things like debunking the hard drive storage bloat, with stats that 1mb has maxmimum yearly 100% filled blocks rate of 52.5gb. 2mb=105gb 4mb=210mb
so a 2tb hard drive at $100 can store 40 years of 1mb, 20 years of 2mb and 10 years of 4mb(2mb+segwit)

things like debunking user upload speeds causing relay delays. by stating that millions of people can happily play an online game, while in a voiceoverIP group chat. while livestreaming the game to youtube or twitch, all of which are upload activities. 750kbps= ~93 kByte/s = ~56mb every 10 minutes