It's always my preference to put our policies on the table. Spam is tough to be open about, though: the way we fight spam is constantly changing; it's a mix of manual and automated tools; and if we document exactly how we catch spammers, the spammers can work around the document constraints. We're talking to our spam and support folks about how to ensure that this doesn't happen to our developers. Differentiating between legitimate bot/testing behavior and spammy mass-posting is tough, particularly for a small team of folks who are under pressure to catch as many spammers as they possibly can every day.
Sincere apologies for the hassle with Louie's account. On Wed, Jun 24, 2009 at 09:43, Craig Hockenberry < [email protected]> wrote: > > One of the guys I work with recently had his account suspended: > > <http://mantia.me/blog/twitter-suspension/> > > We've been having a bit of fun with it: creating a #freemantia hash > tag and even a website <http://freemantia.com> > > But at the bottom of it all, I realized that we (third-party > developers) don't really know what causes an account to be suspended. > And yet we all have users of our products/services who can have an > account suspended. I'd like to be able to tell them why it happened. > > I'm so clueless about what's going on that I don't know whether > suspension is an automated or manual process. In either case, the > decisions being made by man or machine appear to be flawed: Louie > Mantia may be prolific, but he's not a spammer or a robot. > > Can you guys shed a little light on the situation? > > -ch > > P.S. If anyone can speed up the process of reinstating the @mantia > account, I know it would make someone very happy :-) > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
