I assume the attack may be someone trying to make a point. Probably with bad intensions but possibly to forcibly up the client devs priority on handling spam before another "twitter migration" type event happens. 

 I think you're right, someone is trying to make a point one way or another. It is fair criticism, censorship resistance applies to everything, including spam, so it's a tricky thing to solve.