Hi, To answer your questions: 1) There is currently no limit. It is up to the user or application to determine if they should delete the direct messages.
2) It seems that the best thing to do when sending DMs programmatically is to attempt to send and gracefully handle any failure that comes your way. That would involve a single API call as opposed to two. Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 24, 2009 at 5:03 AM, Nial <[email protected]> wrote: > > I did a search but couldn't find anything of relevance. Here are a few > questions on best practice: > > 1) I'm developing a Twitter bot which accepts commands via Direct > Message and was wondering if there's a hard limit to the number of DMs > a user can store. Essentially: should I be deleting the DMs after I > receive and parse them? Will I reach a point where the account is > flooded with Direct Messages and I cannot receive anymore? > > 2) The bot is also capable of sending Direct Messages back to users. > At present, there's no check to see whether or not that particular > user is following the bot account. Is it considered best practice to > perform this check, or just to attempt to send the Direct Message and > fail gracefully if Twitter blocks the message? There seems to be some > difficulty with Twitter not returning valid following data, at > present. I'm just worried that if Twitter see an account sending > numerous DMs to accounts which are not following them, they'll label > the bot as spam. > > Thanks! >
