By Ben's own description of how the @StratecheryINT account was operated [0] -- i.e. "a new account that has posted a bunch of links (all Stratechery interviews) in a short amount of time, from multiple locations around the world." -- this is exactly the kind of low-hanging fruit that we'd want Twitter spam-detectors to cull with minimal time and resources.
Not only b/c of the obvious spam characteristics, but because it was a days-old account with few (if any) followers/followings. Even if it were a mistake, very little of value has been lost, since every tweet was the result of an automated script (i.e. simple to make a new account, and recreate the content that had thus far zero engagement).
Do people seriously think every such case -- an empty days-old account suddenly doing spam-like activity -- should be manually reviewed? That's a daily waste of human resources for tens of thousands (edit: actually it's millions [1]) of trivial permaban decisions -- exactly the kind of thing that an autoban algorithm can efficiently handle.
> For the rest of us peasants: good luck getting help.
I have the same sentiment, but with a different angle. Verified accounts like Thompson's get a lot of leeway with bending/breaking the rules before facing actual punishment. If a lesser known user deployed a selenium-twitter-spam-bot on AWS, it's possible both their spam bot and their real account would be permanently suspended
[0] https://twitter.com/benthompson/status/1583062865116041229
[1] https://twitter.com/paraga/status/1526237583058952192?ref_sr...