oh - i apologise, i think i misunderstood your question. yes - if you send a duplicate tweet while using the twitter.com website, we put up an error on the web page. however, if you send a duplicate tweet through our API, we will silently fail and return a 200 response.
i'm not positive what you are saying when you say "If I use Tweet# and do the same...", but i suspect it falls into the latter of what i said. On Tue, Dec 8, 2009 at 8:52 AM, Stuart Smith <stuartmartinsm...@btinternet.com> 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 <ra...@twitter.com> 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 <stuartmartinsm...@btinternet.com >> >> > 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, > -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
