Re: [twitter-dev] Re: 403 on duplicate post - when?
And a whole load of other people! It's cut down the spam, and that can only be a good thing. On 24 March 2010 01:41, Tim Haines tmhai...@gmail.com wrote: Learnt something here. I knew you couldn't post the same tweet twice in a row. But Twitter is also blocking you from repeating a tweet you posted earlier in the day? So you can't Tweet: A B AThis one won't go through? If this is the case, how far back does it check for duplicates? Guy Kawasaki must hate this. :-) Tim. On Wed, Mar 24, 2010 at 5:28 AM, Mark McBride mmcbr...@twitter.comwrote: Yes, that's a hole in the current logic. I'll work on getting the N-n case handled. ---Mark http://twitter.com/mccv On Tue, Mar 23, 2010 at 6:12 AM, Dewald Pretorius dpr...@gmail.comwrote: Mark, Here is what appears to happen. When you try and duplicate the newest tweet (N), you get the expected new behavior with a 403 and Status is a duplicate. When you try and duplicate tweet N-1, you get the old behavior with 200 OK and the details of tweet N. I have not tested tweet N-2, N-3, etc. On Mar 22, 6:27 pm, Mark McBride mmcbr...@twitter.com wrote: I just tried it and got a 403. Can you give me a screen name you're using, the data posted, and the data returned? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 2:14 PM, Dewald Pretorius dpr...@gmail.com wrote: Yes, I just tried it again. URL:https://api.twitter.com/1/statuses/update.json Headers: Date: Mon, 22 Mar 2010 21:09:39 GMT Server: hi Status: 200 OK X-Transaction: 1269292179-62279-30903 ETag: 05ef33cb30cec1cfa0c5887d4862c9df Last-Modified: Mon, 22 Mar 2010 21:09:39 GMT X-Runtime: 0.26340 Content-Type: application/json; charset=utf-8 Content-Length: 1274 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Set-Cookie: guest_id=1269292179683; path=/ Set-Cookie: lang=en; path=/ Set-Cookie: [snipped] Vary: Accept-Encoding Connection: close The id and text returned were the latest successful tweet, not the duplicate text I was trying to post. On Mar 22, 6:08 pm, Mark McBride mmcbr...@twitter.com wrote: On api.twitter.com/1/statuses/update.json? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius dpr...@gmail.com wrote: When is the change going live to return a 403 response code on a duplicate post? I'm still getting the old behavior. A 200 OK is returned with the details of the latest successful tweet on the account. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: 403 on duplicate post - when?
Mark, Here is what appears to happen. When you try and duplicate the newest tweet (N), you get the expected new behavior with a 403 and Status is a duplicate. When you try and duplicate tweet N-1, you get the old behavior with 200 OK and the details of tweet N. I have not tested tweet N-2, N-3, etc. On Mar 22, 6:27 pm, Mark McBride mmcbr...@twitter.com wrote: I just tried it and got a 403. Can you give me a screen name you're using, the data posted, and the data returned? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 2:14 PM, Dewald Pretorius dpr...@gmail.com wrote: Yes, I just tried it again. URL:https://api.twitter.com/1/statuses/update.json Headers: Date: Mon, 22 Mar 2010 21:09:39 GMT Server: hi Status: 200 OK X-Transaction: 1269292179-62279-30903 ETag: 05ef33cb30cec1cfa0c5887d4862c9df Last-Modified: Mon, 22 Mar 2010 21:09:39 GMT X-Runtime: 0.26340 Content-Type: application/json; charset=utf-8 Content-Length: 1274 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Set-Cookie: guest_id=1269292179683; path=/ Set-Cookie: lang=en; path=/ Set-Cookie: [snipped] Vary: Accept-Encoding Connection: close The id and text returned were the latest successful tweet, not the duplicate text I was trying to post. On Mar 22, 6:08 pm, Mark McBride mmcbr...@twitter.com wrote: On api.twitter.com/1/statuses/update.json? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius dpr...@gmail.com wrote: When is the change going live to return a 403 response code on a duplicate post? I'm still getting the old behavior. A 200 OK is returned with the details of the latest successful tweet on the account. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: 403 on duplicate post - when?
Yes, that's a hole in the current logic. I'll work on getting the N-n case handled. ---Mark http://twitter.com/mccv On Tue, Mar 23, 2010 at 6:12 AM, Dewald Pretorius dpr...@gmail.com wrote: Mark, Here is what appears to happen. When you try and duplicate the newest tweet (N), you get the expected new behavior with a 403 and Status is a duplicate. When you try and duplicate tweet N-1, you get the old behavior with 200 OK and the details of tweet N. I have not tested tweet N-2, N-3, etc. On Mar 22, 6:27 pm, Mark McBride mmcbr...@twitter.com wrote: I just tried it and got a 403. Can you give me a screen name you're using, the data posted, and the data returned? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 2:14 PM, Dewald Pretorius dpr...@gmail.com wrote: Yes, I just tried it again. URL:https://api.twitter.com/1/statuses/update.json Headers: Date: Mon, 22 Mar 2010 21:09:39 GMT Server: hi Status: 200 OK X-Transaction: 1269292179-62279-30903 ETag: 05ef33cb30cec1cfa0c5887d4862c9df Last-Modified: Mon, 22 Mar 2010 21:09:39 GMT X-Runtime: 0.26340 Content-Type: application/json; charset=utf-8 Content-Length: 1274 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Set-Cookie: guest_id=1269292179683; path=/ Set-Cookie: lang=en; path=/ Set-Cookie: [snipped] Vary: Accept-Encoding Connection: close The id and text returned were the latest successful tweet, not the duplicate text I was trying to post. On Mar 22, 6:08 pm, Mark McBride mmcbr...@twitter.com wrote: On api.twitter.com/1/statuses/update.json? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius dpr...@gmail.com wrote: When is the change going live to return a 403 response code on a duplicate post? I'm still getting the old behavior. A 200 OK is returned with the details of the latest successful tweet on the account. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: 403 on duplicate post - when?
Learnt something here. I knew you couldn't post the same tweet twice in a row. But Twitter is also blocking you from repeating a tweet you posted earlier in the day? So you can't Tweet: A B AThis one won't go through? If this is the case, how far back does it check for duplicates? Guy Kawasaki must hate this. :-) Tim. On Wed, Mar 24, 2010 at 5:28 AM, Mark McBride mmcbr...@twitter.com wrote: Yes, that's a hole in the current logic. I'll work on getting the N-n case handled. ---Mark http://twitter.com/mccv On Tue, Mar 23, 2010 at 6:12 AM, Dewald Pretorius dpr...@gmail.comwrote: Mark, Here is what appears to happen. When you try and duplicate the newest tweet (N), you get the expected new behavior with a 403 and Status is a duplicate. When you try and duplicate tweet N-1, you get the old behavior with 200 OK and the details of tweet N. I have not tested tweet N-2, N-3, etc. On Mar 22, 6:27 pm, Mark McBride mmcbr...@twitter.com wrote: I just tried it and got a 403. Can you give me a screen name you're using, the data posted, and the data returned? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 2:14 PM, Dewald Pretorius dpr...@gmail.com wrote: Yes, I just tried it again. URL:https://api.twitter.com/1/statuses/update.json Headers: Date: Mon, 22 Mar 2010 21:09:39 GMT Server: hi Status: 200 OK X-Transaction: 1269292179-62279-30903 ETag: 05ef33cb30cec1cfa0c5887d4862c9df Last-Modified: Mon, 22 Mar 2010 21:09:39 GMT X-Runtime: 0.26340 Content-Type: application/json; charset=utf-8 Content-Length: 1274 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Set-Cookie: guest_id=1269292179683; path=/ Set-Cookie: lang=en; path=/ Set-Cookie: [snipped] Vary: Accept-Encoding Connection: close The id and text returned were the latest successful tweet, not the duplicate text I was trying to post. On Mar 22, 6:08 pm, Mark McBride mmcbr...@twitter.com wrote: On api.twitter.com/1/statuses/update.json? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius dpr...@gmail.com wrote: When is the change going live to return a 403 response code on a duplicate post? I'm still getting the old behavior. A 200 OK is returned with the details of the latest successful tweet on the account. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: 403 on duplicate post - when?
Several tweets back, with a several hour cool down. So you could tweet A, B, A, providing they're several hours a part. ---Mark http://twitter.com/mccv On Tue, Mar 23, 2010 at 6:41 PM, Tim Haines tmhai...@gmail.com wrote: Learnt something here. I knew you couldn't post the same tweet twice in a row. But Twitter is also blocking you from repeating a tweet you posted earlier in the day? So you can't Tweet: A B AThis one won't go through? If this is the case, how far back does it check for duplicates? Guy Kawasaki must hate this. :-) Tim. On Wed, Mar 24, 2010 at 5:28 AM, Mark McBride mmcbr...@twitter.comwrote: Yes, that's a hole in the current logic. I'll work on getting the N-n case handled. ---Mark http://twitter.com/mccv On Tue, Mar 23, 2010 at 6:12 AM, Dewald Pretorius dpr...@gmail.comwrote: Mark, Here is what appears to happen. When you try and duplicate the newest tweet (N), you get the expected new behavior with a 403 and Status is a duplicate. When you try and duplicate tweet N-1, you get the old behavior with 200 OK and the details of tweet N. I have not tested tweet N-2, N-3, etc. On Mar 22, 6:27 pm, Mark McBride mmcbr...@twitter.com wrote: I just tried it and got a 403. Can you give me a screen name you're using, the data posted, and the data returned? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 2:14 PM, Dewald Pretorius dpr...@gmail.com wrote: Yes, I just tried it again. URL:https://api.twitter.com/1/statuses/update.json Headers: Date: Mon, 22 Mar 2010 21:09:39 GMT Server: hi Status: 200 OK X-Transaction: 1269292179-62279-30903 ETag: 05ef33cb30cec1cfa0c5887d4862c9df Last-Modified: Mon, 22 Mar 2010 21:09:39 GMT X-Runtime: 0.26340 Content-Type: application/json; charset=utf-8 Content-Length: 1274 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Set-Cookie: guest_id=1269292179683; path=/ Set-Cookie: lang=en; path=/ Set-Cookie: [snipped] Vary: Accept-Encoding Connection: close The id and text returned were the latest successful tweet, not the duplicate text I was trying to post. On Mar 22, 6:08 pm, Mark McBride mmcbr...@twitter.com wrote: On api.twitter.com/1/statuses/update.json? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius dpr...@gmail.com wrote: When is the change going live to return a 403 response code on a duplicate post? I'm still getting the old behavior. A 200 OK is returned with the details of the latest successful tweet on the account. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: 403 on duplicate post - when?
Yes, I just tried it again. URL: https://api.twitter.com/1/statuses/update.json Headers: Date: Mon, 22 Mar 2010 21:09:39 GMT Server: hi Status: 200 OK X-Transaction: 1269292179-62279-30903 ETag: 05ef33cb30cec1cfa0c5887d4862c9df Last-Modified: Mon, 22 Mar 2010 21:09:39 GMT X-Runtime: 0.26340 Content-Type: application/json; charset=utf-8 Content-Length: 1274 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Set-Cookie: guest_id=1269292179683; path=/ Set-Cookie: lang=en; path=/ Set-Cookie: [snipped] Vary: Accept-Encoding Connection: close The id and text returned were the latest successful tweet, not the duplicate text I was trying to post. On Mar 22, 6:08 pm, Mark McBride mmcbr...@twitter.com wrote: On api.twitter.com/1/statuses/update.json? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius dpr...@gmail.com wrote: When is the change going live to return a 403 response code on a duplicate post? I'm still getting the old behavior. A 200 OK is returned with the details of the latest successful tweet on the account. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
Re: [twitter-dev] Re: 403 on duplicate post - when?
I just tried it and got a 403. Can you give me a screen name you're using, the data posted, and the data returned? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 2:14 PM, Dewald Pretorius dpr...@gmail.com wrote: Yes, I just tried it again. URL: https://api.twitter.com/1/statuses/update.json Headers: Date: Mon, 22 Mar 2010 21:09:39 GMT Server: hi Status: 200 OK X-Transaction: 1269292179-62279-30903 ETag: 05ef33cb30cec1cfa0c5887d4862c9df Last-Modified: Mon, 22 Mar 2010 21:09:39 GMT X-Runtime: 0.26340 Content-Type: application/json; charset=utf-8 Content-Length: 1274 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Set-Cookie: guest_id=1269292179683; path=/ Set-Cookie: lang=en; path=/ Set-Cookie: [snipped] Vary: Accept-Encoding Connection: close The id and text returned were the latest successful tweet, not the duplicate text I was trying to post. On Mar 22, 6:08 pm, Mark McBride mmcbr...@twitter.com wrote: On api.twitter.com/1/statuses/update.json? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius dpr...@gmail.com wrote: When is the change going live to return a 403 response code on a duplicate post? I'm still getting the old behavior. A 200 OK is returned with the details of the latest successful tweet on the account. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject. To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: 403 on duplicate post - when?
I will email the details to a...@twitter.com, so be on the look out for a ticket from me. On Mar 22, 6:27 pm, Mark McBride mmcbr...@twitter.com wrote: I just tried it and got a 403. Can you give me a screen name you're using, the data posted, and the data returned? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 2:14 PM, Dewald Pretorius dpr...@gmail.com wrote: Yes, I just tried it again. URL:https://api.twitter.com/1/statuses/update.json Headers: Date: Mon, 22 Mar 2010 21:09:39 GMT Server: hi Status: 200 OK X-Transaction: 1269292179-62279-30903 ETag: 05ef33cb30cec1cfa0c5887d4862c9df Last-Modified: Mon, 22 Mar 2010 21:09:39 GMT X-Runtime: 0.26340 Content-Type: application/json; charset=utf-8 Content-Length: 1274 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Set-Cookie: guest_id=1269292179683; path=/ Set-Cookie: lang=en; path=/ Set-Cookie: [snipped] Vary: Accept-Encoding Connection: close The id and text returned were the latest successful tweet, not the duplicate text I was trying to post. On Mar 22, 6:08 pm, Mark McBride mmcbr...@twitter.com wrote: On api.twitter.com/1/statuses/update.json? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius dpr...@gmail.com wrote: When is the change going live to return a 403 response code on a duplicate post? I'm still getting the old behavior. A 200 OK is returned with the details of the latest successful tweet on the account. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.
[twitter-dev] Re: 403 on duplicate post - when?
Ticket #915557 On Mar 22, 6:27 pm, Mark McBride mmcbr...@twitter.com wrote: I just tried it and got a 403. Can you give me a screen name you're using, the data posted, and the data returned? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 2:14 PM, Dewald Pretorius dpr...@gmail.com wrote: Yes, I just tried it again. URL:https://api.twitter.com/1/statuses/update.json Headers: Date: Mon, 22 Mar 2010 21:09:39 GMT Server: hi Status: 200 OK X-Transaction: 1269292179-62279-30903 ETag: 05ef33cb30cec1cfa0c5887d4862c9df Last-Modified: Mon, 22 Mar 2010 21:09:39 GMT X-Runtime: 0.26340 Content-Type: application/json; charset=utf-8 Content-Length: 1274 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Set-Cookie: guest_id=1269292179683; path=/ Set-Cookie: lang=en; path=/ Set-Cookie: [snipped] Vary: Accept-Encoding Connection: close The id and text returned were the latest successful tweet, not the duplicate text I was trying to post. On Mar 22, 6:08 pm, Mark McBride mmcbr...@twitter.com wrote: On api.twitter.com/1/statuses/update.json? ---Mark http://twitter.com/mccv On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius dpr...@gmail.com wrote: When is the change going live to return a 403 response code on a duplicate post? I'm still getting the old behavior. A 200 OK is returned with the details of the latest successful tweet on the account. To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+ unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.- Hide quoted text - - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words REMOVE ME as the subject.