Hi Pythonista, You are on the right track about rate limiting. We allow for scheduled tweets as long as the system you build for dispatching them cannot be easily abused. If your application has some abusive users, it's most likely your application would only get a temporary suspension while you fixed whatever hole, or took other measures to block the offending parties.
Our Automation Rules are great resource: http://twitter.zendesk.com/forums/26810/entries/76915 as well as our "Abuse prevention and security guidelines for developers" http://help.twitter.com/entries/79901-api-developers-abuse-prevention-and-security <http://help.twitter.com/entries/79901-api-developers-abuse-prevention-and-security> Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Fri, May 21, 2010 at 5:51 PM, mcfnord <mcfn...@gmail.com> wrote: > If you spent 45 minutes browsing discussions about Dean Collins, then > you studied how spammers caused a made-for-spammers app to get banned. > > If you prevent people from using your app in an abusive way, you won't > end up like Dean Collins. >