[twitter-dev] Re: Is the rate limiting on IP or User a/c
Thank you Chris. It did worked. Victor J. C. -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Chris Thomson Sent: Thursday, July 16, 2009 2:27 AM To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: Is the rate limiting on IP or User a/c Victor, email twitter-development-talk+unsubscr...@googlegroups.com to unsubscribe. -- Chris Thomson On 2009-07-16, at 2:15 AM, victor castleton wrote: > > Hello All, can anybody tell how to stop me unwanted mail from > coming, I am > getting hundreds of mails and I cannot find the way to stop them. > Thanks VJC
[twitter-dev] Re: Is it possible to control the source name
Thank you for the info; @ any rate is has slow down considerably, it seems to be manageable for the time being. VJC -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of victor castleton Sent: Wednesday, July 15, 2009 10:11 PM To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: Is it possible to control the source name Hi, how do I cut myself out of this group, or better yet control or change the type of mail that I am getting? Can you help? Sincerely, Victor -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of AccountingSoftwareGuy Sent: Wednesday, July 15, 2009 7:46 PM To: Twitter Development Talk Subject: [twitter-dev] Is it possible to control the source name Hi I am using the new oAuth method for communicating with the Twitter API. It appears the default behavior is to include the application name as the source of a post. For instance... [date/time] from DynamicTweets This is fine in most cases but in certain cases we want to make a post look like it came from the web and not display our application name... [date/time] from web Is this possible, I've looked through many threads and I can't seem to find a way to do this and the "source=" parameter doesn't seem to work.
[twitter-dev] no-mail
I have no use for this group, kindly do take my name out of the listing and stop any communication. I have already applied to stop receiving mail to no avail. What else can I do? Thank you all. VJC
[twitter-dev] unsubscribe
I am getting hundreds of unwanted mail. I would like to unsubscribe. Thanks
[twitter-dev] unsubscribe
I would like to unsubscribe.Thanks
[twitter-dev] Re: Is the rate limiting on IP or User a/c
Hello All, can anybody tell how to stop me unwanted mail from coming, I am getting hundreds of mails and I cannot find the way to stop them. Thanks VJC -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of LEE Sent: Wednesday, July 15, 2009 11:56 PM To: Twitter Development Talk Subject: [twitter-dev] Is the rate limiting on IP or User a/c Hi All, I would like to ask, the default rate limit for calls to the REST API is 150 requests per hour, is the rate limiting on IP (client) or on User A/C? I have a web application to get the friend's status. I didn't a testing to on this web application, using an A/C "ABC" to keep on getting the friend's status. It ran about 70++ time to got the result successfully, after that twitter returned exceed rate limiting. Then i tried to use another A/C "DEF" to continue to get the friend's status, but twitter returned exceed rate limiting. Guys, do you have any idea on this rate limiting is on IP or A/C? Thanks and Regards,
[twitter-dev] Re: OAuth related bug with signature "Woah there!"
-Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of test test Sent: Wednesday, July 15, 2009 9:51 PM To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: OAuth related bug with signature "Woah there!" +1 Even I keep hitting this issue.Hope twitter guys make oauth registration solid. On Wed, Jul 15, 2009 at 8:48 AM, Bill Kocik wrote: > > > I've seen this same (I believe) bug manifested in different ways, and > it's come up on this list before. Twitter are apparently storing some > sort of "return_to" URL or similar in your session, and sending you to > it at inopportune times. > > A great way to see it in action is to click on the "Block this user" > link when you get a new follower email; after confirming the block, > you wind up at some random page you visited in the past (well, not > completely random, it'll generally be the most recent page you visited > besides the block page). > > > On Jul 15, 9:52 am, Scott Carter wrote: >> I believe that I have discovered a reproducible OAuth related bug. >> >> 1. Sign out of your Twitter account (from Twitter.com). >> 2. Authenticate an app using OAuth (haven't tried authorize flow with >> this issue). >> 3. Go to Twitter.com and login to a different account than used in >> step 2. >> >> I see the message: >> >> "Woah there! >> >> This page requires some information that was not provided. Please >> return to the site that sent you to this page and try again it was >> probably an honest mistake." >> >> with the page URL showing: https://twitter.com/oauth/authenticate >> >> When I revisit twitter.com, I am logged into the account from step 3. >> >> - Scott >> @scott_carter -- Spike Milligan - "All I ask is the chance to prove that money can't make me happy." - http://www.brainyquote.com/quotes/authors/s/spike_milligan.html
[twitter-dev] Re: OAuth related bug with signature "Woah there!"
-Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of test test Sent: Wednesday, July 15, 2009 9:51 PM To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: OAuth related bug with signature "Woah there!" +1 Even I keep hitting this issue.Hope twitter guys make oauth registration solid. On Wed, Jul 15, 2009 at 8:48 AM, Bill Kocik wrote: > > > I've seen this same (I believe) bug manifested in different ways, and > it's come up on this list before. Twitter are apparently storing some > sort of "return_to" URL or similar in your session, and sending you to > it at inopportune times. > > A great way to see it in action is to click on the "Block this user" > link when you get a new follower email; after confirming the block, > you wind up at some random page you visited in the past (well, not > completely random, it'll generally be the most recent page you visited > besides the block page). > > > On Jul 15, 9:52 am, Scott Carter wrote: >> I believe that I have discovered a reproducible OAuth related bug. >> >> 1. Sign out of your Twitter account (from Twitter.com). >> 2. Authenticate an app using OAuth (haven't tried authorize flow with >> this issue). >> 3. Go to Twitter.com and login to a different account than used in >> step 2. >> >> I see the message: >> >> "Woah there! >> >> This page requires some information that was not provided. Please >> return to the site that sent you to this page and try again it was >> probably an honest mistake." >> >> with the page URL showing: https://twitter.com/oauth/authenticate >> >> When I revisit twitter.com, I am logged into the account from step 3. >> >> - Scott >> @scott_carter -- Spike Milligan - "All I ask is the chance to prove that money can't make me happy." - http://www.brainyquote.com/quotes/authors/s/spike_milligan.html
[twitter-dev] Re: OAuth related bug with signature "Woah there!"
-Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of test test Sent: Wednesday, July 15, 2009 9:51 PM To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: OAuth related bug with signature "Woah there!" +1 Even I keep hitting this issue.Hope twitter guys make oauth registration solid. On Wed, Jul 15, 2009 at 8:48 AM, Bill Kocik wrote: > > > I've seen this same (I believe) bug manifested in different ways, and > it's come up on this list before. Twitter are apparently storing some > sort of "return_to" URL or similar in your session, and sending you to > it at inopportune times. > > A great way to see it in action is to click on the "Block this user" > link when you get a new follower email; after confirming the block, > you wind up at some random page you visited in the past (well, not > completely random, it'll generally be the most recent page you visited > besides the block page). > > > On Jul 15, 9:52 am, Scott Carter wrote: >> I believe that I have discovered a reproducible OAuth related bug. >> >> 1. Sign out of your Twitter account (from Twitter.com). >> 2. Authenticate an app using OAuth (haven't tried authorize flow with >> this issue). >> 3. Go to Twitter.com and login to a different account than used in >> step 2. >> >> I see the message: >> >> "Woah there! >> >> This page requires some information that was not provided. Please >> return to the site that sent you to this page and try again it was >> probably an honest mistake." >> >> with the page URL showing: https://twitter.com/oauth/authenticate >> >> When I revisit twitter.com, I am logged into the account from step 3. >> >> - Scott >> @scott_carter -- Spike Milligan - "All I ask is the chance to prove that money can't make me happy." - http://www.brainyquote.com/quotes/authors/s/spike_milligan.html
[twitter-dev] Re: OAuth related bug with signature "Woah there!"
-Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of test test Sent: Wednesday, July 15, 2009 9:51 PM To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: OAuth related bug with signature "Woah there!" +1 Even I keep hitting this issue.Hope twitter guys make oauth registration solid. On Wed, Jul 15, 2009 at 8:48 AM, Bill Kocik wrote: > > > I've seen this same (I believe) bug manifested in different ways, and > it's come up on this list before. Twitter are apparently storing some > sort of "return_to" URL or similar in your session, and sending you to > it at inopportune times. > > A great way to see it in action is to click on the "Block this user" > link when you get a new follower email; after confirming the block, > you wind up at some random page you visited in the past (well, not > completely random, it'll generally be the most recent page you visited > besides the block page). > > > On Jul 15, 9:52 am, Scott Carter wrote: >> I believe that I have discovered a reproducible OAuth related bug. >> >> 1. Sign out of your Twitter account (from Twitter.com). >> 2. Authenticate an app using OAuth (haven't tried authorize flow with >> this issue). >> 3. Go to Twitter.com and login to a different account than used in >> step 2. >> >> I see the message: >> >> "Woah there! >> >> This page requires some information that was not provided. Please >> return to the site that sent you to this page and try again it was >> probably an honest mistake." >> >> with the page URL showing: https://twitter.com/oauth/authenticate >> >> When I revisit twitter.com, I am logged into the account from step 3. >> >> - Scott >> @scott_carter -- Spike Milligan - "All I ask is the chance to prove that money can't make me happy." - http://www.brainyquote.com/quotes/authors/s/spike_milligan.html
[twitter-dev] Re: OAuth related bug with signature "Woah there!"
I don't know whether or no it will help, but I will try it any way. Thanks -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of test test Sent: Wednesday, July 15, 2009 9:51 PM To: twitter-development-talk@googlegroups.com Subject: [twitter-dev] Re: OAuth related bug with signature "Woah there!" +1 Even I keep hitting this issue.Hope twitter guys make oauth registration solid. On Wed, Jul 15, 2009 at 8:48 AM, Bill Kocik wrote: > > > I've seen this same (I believe) bug manifested in different ways, and > it's come up on this list before. Twitter are apparently storing some > sort of "return_to" URL or similar in your session, and sending you to > it at inopportune times. > > A great way to see it in action is to click on the "Block this user" > link when you get a new follower email; after confirming the block, > you wind up at some random page you visited in the past (well, not > completely random, it'll generally be the most recent page you visited > besides the block page). > > > On Jul 15, 9:52 am, Scott Carter wrote: >> I believe that I have discovered a reproducible OAuth related bug. >> >> 1. Sign out of your Twitter account (from Twitter.com). >> 2. Authenticate an app using OAuth (haven't tried authorize flow with >> this issue). >> 3. Go to Twitter.com and login to a different account than used in >> step 2. >> >> I see the message: >> >> "Woah there! >> >> This page requires some information that was not provided. Please >> return to the site that sent you to this page and try again it was >> probably an honest mistake." >> >> with the page URL showing: https://twitter.com/oauth/authenticate >> >> When I revisit twitter.com, I am logged into the account from step 3. >> >> - Scott >> @scott_carter -- Spike Milligan - "All I ask is the chance to prove that money can't make me happy." - http://www.brainyquote.com/quotes/authors/s/spike_milligan.html
[twitter-dev] Re: Is it possible to control the source name
-Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of AccountingSoftwareGuy Sent: Wednesday, July 15, 2009 7:46 PM To: Twitter Development Talk Subject: [twitter-dev] Is it possible to control the source name Hi I am using the new oAuth method for communicating with the Twitter API. It appears the default behavior is to include the application name as the source of a post. For instance... [date/time] from DynamicTweets This is fine in most cases but in certain cases we want to make a post look like it came from the web and not display our application name... [date/time] from web Is this possible, I've looked through many threads and I can't seem to find a way to do this and the "source=" parameter doesn't seem to work.
[twitter-dev] Re: Is it possible to control the source name
Hi, how do I cut myself out of this group, or better yet control or change the type of mail that I am getting? Can you help? Sincerely, Victor -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of AccountingSoftwareGuy Sent: Wednesday, July 15, 2009 7:46 PM To: Twitter Development Talk Subject: [twitter-dev] Is it possible to control the source name Hi I am using the new oAuth method for communicating with the Twitter API. It appears the default behavior is to include the application name as the source of a post. For instance... [date/time] from DynamicTweets This is fine in most cases but in certain cases we want to make a post look like it came from the web and not display our application name... [date/time] from web Is this possible, I've looked through many threads and I can't seem to find a way to do this and the "source=" parameter doesn't seem to work.
