[twitter-dev] Re: How to detect 'Duplicate text' failure to send tweet
Hi Dave, I wasnt too sure if every tweet had a unique id but since it obviuosly does then your approach works fine. I'm not too sure I would agree that my bot is '.. pretty spammy ..' as it is involved in a real interaction with the user but I do agree that none of the followers would at be interested in the 'conversation'. [I suppose I could go down the route of DM] This is my first foray into Twitter development, C# and webapps in general and, as such, I've enjoyed the experience and learned something from it :-) However, Twitter is probably not the ideal choice of platform for this type of thing and it's entirely possible that no-one is interested in playing ancient text adventures anymore. But as I said, this was an experiment for me so it has added some fun into my life for few days whilst I learnt about the Twitter API, Tweet# and C# and a bit of MVC. Looks like I'll need to find another Twitter project to work on Cheers, On Dec 9, 9:43 am, Dave Sherohman d...@fishtwits.com wrote: On Tue, Dec 08, 2009 at 10:08:14AM -0800, Stuart Smith wrote: Hi Abraham, so I should keep a list of all of the tweets I send and check the id of each and every status I send to see if it matches a previously sent id? That's quite a lot of additional processing. Not necessarily... What I've been doing is just keeping a record of the highest status ID my application has seen and checking whether the returned ID is larger than that highest-seen ID or not. Very quick, simple, and effective. Is this what I have heard called 'recurring tweets'? If so, I read somewhere that they are going to be allowed to re-occur at some point soon - is this correct? Related, but distinct. What you've described is repeated tweets sent manually for a game, probably in short bursts. The recurring tweets (mis-)feature offered by some sites is automatically tweet this text once every three hours for the next month. Either way, though, it sounds pretty spammy to me (would your users' friends really want to see their timelines clogged up with N, N, E, S...?) and I'm all for Twitter doing what they can to suppress it. It just would have been nice if rejected updates had been reported as errors (which they are) from square one. -- Dave Sherohman
Re: [twitter-dev] Re: How to detect 'Duplicate text' failure to send tweet
On Tue, Dec 08, 2009 at 10:08:14AM -0800, Stuart Smith wrote: Hi Abraham, so I should keep a list of all of the tweets I send and check the id of each and every status I send to see if it matches a previously sent id? That's quite a lot of additional processing. Not necessarily... What I've been doing is just keeping a record of the highest status ID my application has seen and checking whether the returned ID is larger than that highest-seen ID or not. Very quick, simple, and effective. Is this what I have heard called 'recurring tweets'? If so, I read somewhere that they are going to be allowed to re-occur at some point soon - is this correct? Related, but distinct. What you've described is repeated tweets sent manually for a game, probably in short bursts. The recurring tweets (mis-)feature offered by some sites is automatically tweet this text once every three hours for the next month. Either way, though, it sounds pretty spammy to me (would your users' friends really want to see their timelines clogged up with N, N, E, S...?) and I'm all for Twitter doing what they can to suppress it. It just would have been nice if rejected updates had been reported as errors (which they are) from square one. -- Dave Sherohman
[twitter-dev] Re: How to detect 'Duplicate text' failure to send tweet
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,
Re: [twitter-dev] Re: How to detect 'Duplicate text' failure to send tweet
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 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, -- 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
[twitter-dev] Re: How to detect 'Duplicate text' failure to send tweet
Hi Abraham, so I should keep a list of all of the tweets I send and check the id of each and every status I send to see if it matches a previously sent id? That's quite a lot of additional processing. Does this 'duplicate text' have a time period for which it is invalid? i.e. how long do I have to wait before sending the same text? Is this what I have heard called 'recurring tweets'? If so, I read somewhere that they are going to be allowed to re-occur at some point soon - is this correct? Cheers, On Dec 8, 5:38 pm, Abraham Williams 4bra...@gmail.com wrote: 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 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, -- 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
Re: [twitter-dev] Re: How to detect 'Duplicate text' failure to send tweet
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
Re: [twitter-dev] Re: How to detect 'Duplicate text' failure to send tweet
Does this 'duplicate text' have a time period for which it is invalid? i.e. how long do I have to wait before sending the same text? we currently reject tweets that have an exact string match to any tweet sent recently (a few hours). Is this what I have heard called 'recurring tweets'? If so, I read somewhere that they are going to be allowed to re-occur at some point soon - is this correct? i'm not sure what you mean by allowed to re-occur at some point soon. i don't think we're going to change the logic around duplicate tweets, but what we are working on is better error messaging when we reject a tweet. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: How to detect 'Duplicate text' failure to send tweet
Hi Raffi, I read on a blog somewhere that the recurring tweets (which I believe are the same as tweets with duplicate text) are going to be allowed i.e. the logic that rejects them will no longer be active. From what you say this is unlikely to happen. The reason I am so interested in this particular test is that I had been working on a twitter bot that allows you to play the orginal Colossal Cave text adventure and the user would use a lot of tweets with text like N, S, E, W etc to indicate a direction to move in (I was unaware of the duplicate text rejection). This would appear to be a complete and utter waste of time now - c'est la vie!!! I was going to put it live tonight but there is probably no point now. Cheers, On Dec 8, 6:28 pm, Raffi Krikorian ra...@twitter.com wrote: Does this 'duplicate text' have a time period for which it is invalid? i.e. how long do I have to wait before sending the same text? we currently reject tweets that have an exact string match to any tweet sent recently (a few hours). Is this what I have heard called 'recurring tweets'? If so, I read somewhere that they are going to be allowed to re-occur at some point soon - is this correct? i'm not sure what you mean by allowed to re-occur at some point soon. i don't think we're going to change the logic around duplicate tweets, but what we are working on is better error messaging when we reject a tweet. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Re: How to detect 'Duplicate text' failure to send tweet
On Tue, Dec 8, 2009 at 10:43 AM, Stuart Smith stuartmartinsm...@btinternet.com wrote: Hi Raffi, I read on a blog somewhere that the recurring tweets (which I believe are the same as tweets with duplicate text) are going to be allowed i.e. the logic that rejects them will no longer be active. From what you say this is unlikely to happen. The reason I am so interested in this particular test is that I had been working on a twitter bot that allows you to play the orginal Colossal Cave text adventure and the user would use a lot of tweets with text like N, S, E, W etc to indicate a direction to move in (I was unaware of the duplicate text rejection). This would appear to be a complete and utter waste of time now - c'est la vie!!! I was going to put it live tonight but there is probably no point now. Cheers, On Dec 8, 6:28 pm, Raffi Krikorian ra...@twitter.com wrote: Does this 'duplicate text' have a time period for which it is invalid? i.e. how long do I have to wait before sending the same text? we currently reject tweets that have an exact string match to any tweet sent recently (a few hours). Is this what I have heard called 'recurring tweets'? If so, I read somewhere that they are going to be allowed to re-occur at some point soon - is this correct? i'm not sure what you mean by allowed to re-occur at some point soon. i don't think we're going to change the logic around duplicate tweets, but what we are working on is better error messaging when we reject a tweet. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
