When you create a status you get a 200 response and the current user/status object which includes the status id. If you try to create a duplicate status it should return the same status object with a status id that matches the previous one.
Abraham On Tue, Dec 8, 2009 at 10:52, Stuart Smith <[email protected] > wrote: > Hi Raffi, thanks for the reply but I'm still unsure of the process. > > If I send a tweet with the same text more than once via twitter.com I > get a pop-upm saying to try some other text as I've sent that text > before and the tweet is not created so there is no id. > > If I use Tweet# and do the same I get a 200 OK response which suggests > that the tweet was created but it never gets sent to the recipient and > again I have no id. > > Can you explain a bit more. > > Cheers, > > On Dec 8, 4:23 pm, Raffi Krikorian <[email protected]> wrote: > > Currently, we recommend people look at the tweet ID and just > > "remember" it. It is on the short list to get an appropriate error > > code returned if we reject a tweetx > > > > On Dec 8, 2009, at 1:10 AM, Stuart Smith < > [email protected] > > > > > wrote: > > > Is there any way to check via the api that the tweet you tried to send > > > was not sent because it was a duplicate? I get a 200 OK response so > > > maybe there is another way? BTW I am using Tweet#. > > > > > Thanks, > -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | Awesome Lists | http://twitterli.st This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, WI, United States
