I've updated the docs. There's no limit per se, we just discard statuses with text that are identical to the updating user's current status text. So, don't post "foo bar baz" twice in a row, as it's not guaranteed to post.
On Mon, Dec 8, 2008 at 22:38, Corey Menscher <[EMAIL PROTECTED]> wrote: > > No documentation update yet...can you please just tell me what the > subsequent update limit is so I can update my code to prevent > redundant posts? In the meantime I'm going to limit identical posts > to no more than one a minute. (Don't worry, I don't expect the app to > update nearly that often...but it may happen while testing.) > > > On Dec 6, 6:34 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote: >> It's not new, and we haven't had any other reports of updates lagging. >> >> On Sat, Dec 6, 2008 at 15:25, tweetip <[EMAIL PROTECTED]> wrote: >> >> > I've been guessing this new check is why posting an update is taking >> > so long? >> >> -- >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
