[twitter-dev] Re: Getting too many login attempts error though my app uses per user auth apis
Just in case someone with a similar problem lands on this thread, I would like you to know that there is a limit on the number of unfollows per IP and distributing this over multiple IPs helped me solve my problem. However, you really do not need to bother much about it unless you start making thousands of requests per hour. FYI, @episod and I exchanged a few more emails and with his help and advice I could solve this problem. The twitter API team is insanely fast(considering the scale at which they operate) when it comes to helping out devs like me when in trouble. This is the second time I've had quick responses over a critical issue. Kudos to you guys. -Nischal On Apr 8, 7:55 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Can you tell me how many unfollows you're doing per minute/per 5 minutes/per 10 minutes and per hour? Do you track these metrics? Are there means to automate the UI of your site that it could be being abused? It's not possible for us to rate limit your application specifically for this single method, it's purely based on IP address -- so that's not what's happening -- an unpublished, subject to change limit on unfollows will always apply to each and every IP address. @episod http://twitter.com/episod - Taylor Singletary On Fri, Apr 8, 2011 at 7:26 AM, Nischal Shetty nischalshett...@gmail.comwrote: Help! I guess my ordeals are not over yet :( It's painful. I created a new module and hosted it on aws. I opened it up to a subset of followers and bang, the rate limit error appears again! Now I'm confident it's my app that is being rate limited and rate limited ONLY for Unfollow calls. I haven't had any peace from the last 48 hours due to this. I request you to please look into this. Should I try resetting the twitter keys of my app? Will doing that help? Please help me out, things look all gloomy right now. It's the same Error code 420. -N On 8 April 2011 15:09, Nischal Shetty nischalshett...@gmail.com wrote: Moved the unfollow tasks out of GAE. Hoping things go smooth now. Allowing only a subset of users to unfollow. Will gradually allow everyone. Keeping fingers crossed. -Nischal On 8 April 2011 06:52, Nischal Shetty nischalshett...@gmail.com wrote: Oh, so if I send in unfollows from a different IP this would work! Nice, I'll do that. I've been monitoring my logs, and as you said the blocks are happening at intervals in bursts. Alright, what I will do is set up some service on aws which would do the unfollowing and at the same time I will contact GAE too. Though I guess a good long term solution is to keep these intensive api calls to a dedicated IP? Thank you so much for the support, I really appreciate it. -Nischal On 8 April 2011 06:40, Taylor Singletary taylorsinglet...@twitter.comwrote: We've tested this scenario thoroughly and the limiting ceases after a short period of time when the maximum levels are reached. We couldn't reproduce any out of the ordinary behavior. The most likely culprit in your case is another application performing unfollows on the same GAE IP address you are on; this happens. Consider contacting GAE support to see if your app can be moved to a different IP or some other solution on their side. Consider moving to a hosting environment that allows you to have your own dedicated IP addresss. Taylor On Thursday, April 7, 2011, nischalshetty nischalshett...@gmail.com wrote: I'm making around 50-60 unfollow requests per minute and it's still throwing the error. Did you have a chance to look at it? My site is unsable :( -N On Apr 8, 1:11 am, Nischal Shetty nischalshett...@gmail.com wrote: Thank you so much for getting back. I'm using twitter4j version 2.2.1 , it uses all the latest api endpoints. I could not get the raw response data as there's no easy way to do that using the API and I've been busy trying to work around the errors my app has been getting. Here's the message that I get in my log: 420:Returned by the Search and Trends API when you are being rate limited (http://dev.twitter.com/pages/rate-limiting). Returned by the Streaming API: Too many login attempts in a short period of time. Running too many copies of the same application authenticating with the same account name. This is the URL being used : http://api.twitter.com/1/friendships/destroy.json?include_entities=fa. .. -N On 8 April 2011 00:37, Matt Harris thematthar...@twitter.com wrote: Does the error you get back have any message in the response body? Also, just so we are absolutely clear which API method you are calling, can you share the exact URL you are hitting and parameters you are sending (obscuring any secure information) On Thu, Apr 7, 2011 at 10:58 AM, nischalshetty nischalshett...@gmail.comwrote: It's just not working. No matter how
[twitter-dev] Re: Getting too many login attempts error though my app uses per user auth apis
I'm implementing queuing right now. That will hopefully settle things a little. Once that is done I will provide whatever info I can to get this thing sorted. @Taylor I would like to specifically thank you for getting back to me. Considering the amount of distress calls you guys get, a response time this quick is awesome. I'm hoping queuing would help me stop all the 420 error codes. The way I'll be implementing this is : 1. First 420 error occurs, start adding unfollows to Queue 2. Queue would try to unfollow, if error, defer for 10s 3. Keep doubling the check time till it reaches say 10 minutes 4. Keep trying every 10 minutes I hope this will ease things out and make my app look good to your abuse detection algorithm :) I tried searching but did not get any definite write up. Is it advisable to back off even when there are 502/503/500 error? The reason I ask is because these errors are quite common and if an app really starts backing off on these errors then there would be a lot of lag. But I have a feeling not backing off on these errors is one of the reasons for the 420 error that my apps encountering, though you would be the right person to answer this. -Nischal On Apr 7, 6:14 am, nischalshetty nischalshett...@gmail.com wrote: Another thing I would like to add is along with these errors I also am getting a lot of 502 and 503 requests. Do they have to do something with this? -N On Apr 7, 5:58 am, nischalshetty nischalshett...@gmail.com wrote: Even as I wrote this and got my servers back up, the 420 errors started all over again :( Please, can you check on your end using my app code or something. I can mail you the app id if you want. The app is justunfollow.com -N On Apr 7, 5:55 am, nischalshetty nischalshett...@gmail.com wrote: There may be others on the IP address you are using abusing the system and making you suffer as a result. Probably but then this had happened twice as I said earlier and both the times none of the api's worked until one of you guys removed the ips from the blacklist. Do you get a HTTP status code 420 just for unfollow requests or is it for all requests? Have you attempted to perform the operation in isolation from your servers (not tied to your application business logic, perhaps using command line tools or Curl, Twurl, etc.)? I'm getting it for Unfollow requests only. It does not throw errors when I try it individually even on my own server. I had a test url set up and it did not throw error on unfollowing around 200 users. That's the time I made it live for everyone but it started giving the errors in a few minutes of going live again. Can you do the following: 1) Issue one of the API calls you're trying to make, taking note of the exact API URL you're executing (tell me which it is) (may as well at this time verify that you're using the proper URL structures, including api.twitter.com as the domain /1/ prepending all resource URLs to indicate the API version) 2) When/if you get the the error response, capture the exact HTTP status code and the raw/exact HTTP body you get in response? (Not as interpreted by any library you're using). I will do this and revert back. I am using the latest version of twitter4j and it uses api.twitter.com as the end point. I had put the servers off for the last 5-6 hours now. I just turned them back up. I'm hoping the same thing does not start again :( -N On Apr 7, 12:44 am, Taylor Singletary taylorsinglet...@twitter.com wrote: There may be others on the IP address you are using abusing the system and making you suffer as a result. Do you get a HTTP status code 420 just for unfollow requests or is it for all requests? Have you attempted to perform the operation in isolation from your servers (not tied to your application business logic, perhaps using command line tools or Curl, Twurl, etc.)? Can you do the following: 1) Issue one of the API calls you're trying to make, taking note of the exact API URL you're executing (tell me which it is) (may as well at this time verify that you're using the proper URL structures, including api.twitter.com as the domain /1/ prepending all resource URLs to indicate the API version) 2) When/if you get the the error response, capture the exact HTTP status code and the raw/exact HTTP body you get in response? (Not as interpreted by any library you're using). @episod http://twitter.com/episod - Taylor Singletary On Wed, Apr 6, 2011 at 12:07 PM, nischalshetty nischalshett...@gmail.comwrote: I cooled down my servers for more than 2 hours now. There were no activities happening through my app. I turned it back on just a few minutes back. The same problem, getting 420 error codes :( Cooling it off again, can you do
[twitter-dev] Re: Getting too many login attempts error though my app uses per user auth apis
It's just not working. No matter how much I wait, as soon as unfollow requests start I get the Error Code 420. I have no clue what to do. Can you please check on your end if my app JustUnfollow.com is being rate limited for some reason. I've been trying from more than 24 hours. Thousands of users use the app everyday. This is causing a lot of problem and making me lose users. I request you, please have a check, I have not changed any code, nor am I making any new API calls and my API calls did not increase drastically. I've been running this app over a year now. It's only the unfollow requests that get the 420 error. My app also has follow requests which seem to be working fine. -N On Apr 7, 11:10 am, nischalshetty nischalshett...@gmail.com wrote: I'm implementing queuing right now. That will hopefully settle things a little. Once that is done I will provide whatever info I can to get this thing sorted. @Taylor I would like to specifically thank you for getting back to me. Considering the amount of distress calls you guys get, a response time this quick is awesome. I'm hoping queuing would help me stop all the 420 error codes. The way I'll be implementing this is : 1. First 420 error occurs, start adding unfollows to Queue 2. Queue would try to unfollow, if error, defer for 10s 3. Keep doubling the check time till it reaches say 10 minutes 4. Keep trying every 10 minutes I hope this will ease things out and make my app look good to your abuse detection algorithm :) I tried searching but did not get any definite write up. Is it advisable to back off even when there are 502/503/500 error? The reason I ask is because these errors are quite common and if an app really starts backing off on these errors then there would be a lot of lag. But I have a feeling not backing off on these errors is one of the reasons for the 420 error that my apps encountering, though you would be the right person to answer this. -Nischal On Apr 7, 6:14 am, nischalshetty nischalshett...@gmail.com wrote: Another thing I would like to add is along with these errors I also am getting a lot of 502 and 503 requests. Do they have to do something with this? -N On Apr 7, 5:58 am, nischalshetty nischalshett...@gmail.com wrote: Even as I wrote this and got my servers back up, the 420 errors started all over again :( Please, can you check on your end using my app code or something. I can mail you the app id if you want. The app is justunfollow.com -N On Apr 7, 5:55 am, nischalshetty nischalshett...@gmail.com wrote: There may be others on the IP address you are using abusing the system and making you suffer as a result. Probably but then this had happened twice as I said earlier and both the times none of the api's worked until one of you guys removed the ips from the blacklist. Do you get a HTTP status code 420 just for unfollow requests or is it for all requests? Have you attempted to perform the operation in isolation from your servers (not tied to your application business logic, perhaps using command line tools or Curl, Twurl, etc.)? I'm getting it for Unfollow requests only. It does not throw errors when I try it individually even on my own server. I had a test url set up and it did not throw error on unfollowing around 200 users. That's the time I made it live for everyone but it started giving the errors in a few minutes of going live again. Can you do the following: 1) Issue one of the API calls you're trying to make, taking note of the exact API URL you're executing (tell me which it is) (may as well at this time verify that you're using the proper URL structures, including api.twitter.com as the domain /1/ prepending all resource URLs to indicate the API version) 2) When/if you get the the error response, capture the exact HTTP status code and the raw/exact HTTP body you get in response? (Not as interpreted by any library you're using). I will do this and revert back. I am using the latest version of twitter4j and it uses api.twitter.com as the end point. I had put the servers off for the last 5-6 hours now. I just turned them back up. I'm hoping the same thing does not start again :( -N On Apr 7, 12:44 am, Taylor Singletary taylorsinglet...@twitter.com wrote: There may be others on the IP address you are using abusing the system and making you suffer as a result. Do you get a HTTP status code 420 just for unfollow requests or is it for all requests? Have you attempted to perform the operation in isolation from your servers (not tied to your application business logic, perhaps using command line tools or Curl, Twurl, etc.)? Can you do the following: 1) Issue one of the API calls you're trying to make
[twitter-dev] Re: Getting too many login attempts error though my app uses per user auth apis
I'm making around 50-60 unfollow requests per minute and it's still throwing the error. Did you have a chance to look at it? My site is unsable :( -N On Apr 8, 1:11 am, Nischal Shetty nischalshett...@gmail.com wrote: Thank you so much for getting back. I'm using twitter4j version 2.2.1 , it uses all the latest api endpoints. I could not get the raw response data as there's no easy way to do that using the API and I've been busy trying to work around the errors my app has been getting. Here's the message that I get in my log: 420:Returned by the Search and Trends API when you are being rate limited (http://dev.twitter.com/pages/rate-limiting). Returned by the Streaming API: Too many login attempts in a short period of time. Running too many copies of the same application authenticating with the same account name. This is the URL being used : http://api.twitter.com/1/friendships/destroy.json?include_entities=fa... -N On 8 April 2011 00:37, Matt Harris thematthar...@twitter.com wrote: Does the error you get back have any message in the response body? Also, just so we are absolutely clear which API method you are calling, can you share the exact URL you are hitting and parameters you are sending (obscuring any secure information) On Thu, Apr 7, 2011 at 10:58 AM, nischalshetty nischalshett...@gmail.comwrote: It's just not working. No matter how much I wait, as soon as unfollow requests start I get the Error Code 420. I have no clue what to do. Can you please check on your end if my app JustUnfollow.com is being rate limited for some reason. I've been trying from more than 24 hours. Thousands of users use the app everyday. This is causing a lot of problem and making me lose users. I request you, please have a check, I have not changed any code, nor am I making any new API calls and my API calls did not increase drastically. I've been running this app over a year now. It's only the unfollow requests that get the 420 error. My app also has follow requests which seem to be working fine. -N On Apr 7, 11:10 am, nischalshetty nischalshett...@gmail.com wrote: I'm implementing queuing right now. That will hopefully settle things a little. Once that is done I will provide whatever info I can to get this thing sorted. @Taylor I would like to specifically thank you for getting back to me. Considering the amount of distress calls you guys get, a response time this quick is awesome. I'm hoping queuing would help me stop all the 420 error codes. The way I'll be implementing this is : 1. First 420 error occurs, start adding unfollows to Queue 2. Queue would try to unfollow, if error, defer for 10s 3. Keep doubling the check time till it reaches say 10 minutes 4. Keep trying every 10 minutes I hope this will ease things out and make my app look good to your abuse detection algorithm :) I tried searching but did not get any definite write up. Is it advisable to back off even when there are 502/503/500 error? The reason I ask is because these errors are quite common and if an app really starts backing off on these errors then there would be a lot of lag. But I have a feeling not backing off on these errors is one of the reasons for the 420 error that my apps encountering, though you would be the right person to answer this. -Nischal On Apr 7, 6:14 am, nischalshetty nischalshett...@gmail.com wrote: Another thing I would like to add is along with these errors I also am getting a lot of 502 and 503 requests. Do they have to do something with this? -N On Apr 7, 5:58 am, nischalshetty nischalshett...@gmail.com wrote: Even as I wrote this and got my servers back up, the 420 errors started all over again :( Please, can you check on your end using my app code or something. I can mail you the app id if you want. The app is justunfollow.com -N On Apr 7, 5:55 am, nischalshetty nischalshett...@gmail.com wrote: There may be others on the IP address you are using abusing the system and making you suffer as a result. Probably but then this had happened twice as I said earlier and both the times none of the api's worked until one of you guys removed the ips from the blacklist. Do you get a HTTP status code 420 just for unfollow requests or is it for all requests? Have you attempted to perform the operation in isolation from your servers (not tied to your application business logic, perhaps using command line tools or Curl, Twurl, etc.)? I'm getting it for Unfollow requests only. It does not throw errors when I try it individually even on my own server. I had a test url set up and it did not throw error on unfollowing around 200 users. That's the time I made it live for everyone but it started giving the errors in a few
[twitter-dev] Re: Getting too many login attempts error though my app uses per user auth apis
I am getting this for the Unfollow method. This shouldn't happen for the unfollow API. Can someone at twitter look into it? -N On Apr 6, 8:24 pm, nischalshetty nischalshett...@gmail.com wrote: 420:Returned by the Search and Trends API when you are being rate limited (http://dev.twitter.com/pages/rate-limiting). Returned by the Streaming API: Too many login attempts in a short period of time. Running too many copies of the same application authenticating with the same account name. I'm getting the above error. It's in large numbers. Can someone help? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Getting too many login attempts error though my app uses per user auth apis
Hi, It's my app http://justunfollow.com It's been running from more than a year now. I did not see any sudden increase in traffic or any of that sort. It's hosted on the Google Appengine and there were 2 cases in the entire year when appengine ips were blocked by twitter. I have more than 200,000 users. Your advice would be greatly appreciated. I do not make use of any search or trends api. -N On Apr 6, 8:41 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Unfollowing is not rate limited by the API, but we have organic limits on most write actions service-wide to prevent certain kinds of bursty behavior. Best to back off from retrying requests when you get an error like this for an exponentially increasing amount of time -- first 30 seconds, then a minute, then a few minutes, then 10 minutes, etc. @episod http://twitter.com/episod - Taylor Singletary On Wed, Apr 6, 2011 at 8:31 AM, nischalshetty nischalshett...@gmail.comwrote: I am getting this for the Unfollow method. This shouldn't happen for the unfollow API. Can someone at twitter look into it? -N On Apr 6, 8:24 pm, nischalshetty nischalshett...@gmail.com wrote: 420:Returned by the Search and Trends API when you are being rate limited (http://dev.twitter.com/pages/rate-limiting). Returned by the Streaming API: Too many login attempts in a short period of time. Running too many copies of the same application authenticating with the same account name. I'm getting the above error. It's in large numbers. Can someone help? -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Getting too many login attempts error though my app uses per user auth apis
I just checked my log. The first error was encountered around 6.5 hours ago. Since then it's been occurring in loads continuously : ( This is the first time in the entire year that I'm seeing something like this and no new code has been pushed to production. I request you to check if my app is being rate limited or if appengine ips are being rate limited. My app tries to stay within the limits for each user and has never been rate limited. -N On Apr 6, 8:47 pm, nischalshetty nischalshett...@gmail.com wrote: Hi, It's my apphttp://justunfollow.comIt's been running from more than a year now. I did not see any sudden increase in traffic or any of that sort. It's hosted on the Google Appengine and there were 2 cases in the entire year when appengine ips were blocked by twitter. I have more than 200,000 users. Your advice would be greatly appreciated. I do not make use of any search or trends api. -N On Apr 6, 8:41 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Unfollowing is not rate limited by the API, but we have organic limits on most write actions service-wide to prevent certain kinds of bursty behavior. Best to back off from retrying requests when you get an error like this for an exponentially increasing amount of time -- first 30 seconds, then a minute, then a few minutes, then 10 minutes, etc. @episod http://twitter.com/episod - Taylor Singletary On Wed, Apr 6, 2011 at 8:31 AM, nischalshetty nischalshett...@gmail.comwrote: I am getting this for the Unfollow method. This shouldn't happen for the unfollow API. Can someone at twitter look into it? -N On Apr 6, 8:24 pm, nischalshetty nischalshett...@gmail.com wrote: 420:Returned by the Search and Trends API when you are being rate limited (http://dev.twitter.com/pages/rate-limiting). Returned by the Streaming API: Too many login attempts in a short period of time. Running too many copies of the same application authenticating with the same account name. I'm getting the above error. It's in large numbers. Can someone help? -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Getting too many login attempts error though my app uses per user auth apis
Though I have so many users, each user has an internal limit of 100 unfollows per day which is well within any sort of limits. That is one of the reasons why I never implemented any queuing mechanism, such short number of unfollows can be done instantly. Besides, there were no sudden spikes in traffic so this sudden rate limiting baffles me. And automated unfollows are not allowed so I thought queuing wouldn't be a good idea. I'll try to implement something like that but what's the short term solution? Can you do something on your end to remove the rate limit if any that might have been put on my app? I have always adhered to twitter limits and rules never going out of my way. Please help me with this. -Nischal On Apr 6, 9:00 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: By running on Google App Engine, or any host where you share IP addresses with another service, you're going to be at a disadvantage when it comes to abuse detection -- my advice would be to ensure you have a queue system in place for API actions you take (really any application servicing anywhere near as many users as you do should have this in place), especially actions applied in bulk -- you will have times that you need to queue up your actions until you can resume making requests -- the best way to detect if you can resume making requests is by intermittently trying a single item at the top of the queue once every few seconds, increasing the duration you wait with every failed request. You never want to continue bursting when faced with an error like this, it would only make your application appear more abusive to the metrics-oriented unfeeling eye of an abuse detection algorithm. @episod http://twitter.com/episod - Taylor Singletary On Wed, Apr 6, 2011 at 8:47 AM, nischalshetty nischalshett...@gmail.comwrote: Hi, It's my apphttp://justunfollow.comIt's been running from more than a year now. I did not see any sudden increase in traffic or any of that sort. It's hosted on the Google Appengine and there were 2 cases in the entire year when appengine ips were blocked by twitter. I have more than 200,000 users. Your advice would be greatly appreciated. I do not make use of any search or trends api. -N On Apr 6, 8:41 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Unfollowing is not rate limited by the API, but we have organic limits on most write actions service-wide to prevent certain kinds of bursty behavior. Best to back off from retrying requests when you get an error like this for an exponentially increasing amount of time -- first 30 seconds, then a minute, then a few minutes, then 10 minutes, etc. @episod http://twitter.com/episod - Taylor Singletary On Wed, Apr 6, 2011 at 8:31 AM, nischalshetty nischalshett...@gmail.com wrote: I am getting this for the Unfollow method. This shouldn't happen for the unfollow API. Can someone at twitter look into it? -N On Apr 6, 8:24 pm, nischalshetty nischalshett...@gmail.com wrote: 420:Returned by the Search and Trends API when you are being rate limited (http://dev.twitter.com/pages/rate-limiting). Returned by the Streaming API: Too many login attempts in a short period of time. Running too many copies of the same application authenticating with the same account name. I'm getting the above error. It's in large numbers. Can someone help? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Getting too many login attempts error though my app uses per user auth apis
I cooled down my servers for more than 2 hours now. There were no activities happening through my app. I turned it back on just a few minutes back. The same problem, getting 420 error codes :( Cooling it off again, can you do something to get me out of this trouble? -N On Apr 6, 9:07 pm, nischalshetty nischalshett...@gmail.com wrote: Though I have so many users, each user has an internal limit of 100 unfollows per day which is well within any sort of limits. That is one of the reasons why I never implemented any queuing mechanism, such short number of unfollows can be done instantly. Besides, there were no sudden spikes in traffic so this sudden rate limiting baffles me. And automated unfollows are not allowed so I thought queuing wouldn't be a good idea. I'll try to implement something like that but what's the short term solution? Can you do something on your end to remove the rate limit if any that might have been put on my app? I have always adhered to twitter limits and rules never going out of my way. Please help me with this. -Nischal On Apr 6, 9:00 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: By running on Google App Engine, or any host where you share IP addresses with another service, you're going to be at a disadvantage when it comes to abuse detection -- my advice would be to ensure you have a queue system in place for API actions you take (really any application servicing anywhere near as many users as you do should have this in place), especially actions applied in bulk -- you will have times that you need to queue up your actions until you can resume making requests -- the best way to detect if you can resume making requests is by intermittently trying a single item at the top of the queue once every few seconds, increasing the duration you wait with every failed request. You never want to continue bursting when faced with an error like this, it would only make your application appear more abusive to the metrics-oriented unfeeling eye of an abuse detection algorithm. @episod http://twitter.com/episod - Taylor Singletary On Wed, Apr 6, 2011 at 8:47 AM, nischalshetty nischalshett...@gmail.comwrote: Hi, It's my apphttp://justunfollow.comIt'sbeen running from more than a year now. I did not see any sudden increase in traffic or any of that sort. It's hosted on the Google Appengine and there were 2 cases in the entire year when appengine ips were blocked by twitter. I have more than 200,000 users. Your advice would be greatly appreciated. I do not make use of any search or trends api. -N On Apr 6, 8:41 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Unfollowing is not rate limited by the API, but we have organic limits on most write actions service-wide to prevent certain kinds of bursty behavior. Best to back off from retrying requests when you get an error like this for an exponentially increasing amount of time -- first 30 seconds, then a minute, then a few minutes, then 10 minutes, etc. @episod http://twitter.com/episod - Taylor Singletary On Wed, Apr 6, 2011 at 8:31 AM, nischalshetty nischalshett...@gmail.com wrote: I am getting this for the Unfollow method. This shouldn't happen for the unfollow API. Can someone at twitter look into it? -N On Apr 6, 8:24 pm, nischalshetty nischalshett...@gmail.com wrote: 420:Returned by the Search and Trends API when you are being rate limited (http://dev.twitter.com/pages/rate-limiting). Returned by the Streaming API: Too many login attempts in a short period of time. Running too many copies of the same application authenticating with the same account name. I'm getting the above error. It's in large numbers. Can someone help? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Getting too many login attempts error though my app uses per user auth apis
There may be others on the IP address you are using abusing the system and making you suffer as a result. Probably but then this had happened twice as I said earlier and both the times none of the api's worked until one of you guys removed the ips from the blacklist. Do you get a HTTP status code 420 just for unfollow requests or is it for all requests? Have you attempted to perform the operation in isolation from your servers (not tied to your application business logic, perhaps using command line tools or Curl, Twurl, etc.)? I'm getting it for Unfollow requests only. It does not throw errors when I try it individually even on my own server. I had a test url set up and it did not throw error on unfollowing around 200 users. That's the time I made it live for everyone but it started giving the errors in a few minutes of going live again. Can you do the following: 1) Issue one of the API calls you're trying to make, taking note of the exact API URL you're executing (tell me which it is) (may as well at this time verify that you're using the proper URL structures, including api.twitter.com as the domain /1/ prepending all resource URLs to indicate the API version) 2) When/if you get the the error response, capture the exact HTTP status code and the raw/exact HTTP body you get in response? (Not as interpreted by any library you're using). I will do this and revert back. I am using the latest version of twitter4j and it uses api.twitter.com as the end point. I had put the servers off for the last 5-6 hours now. I just turned them back up. I'm hoping the same thing does not start again :( -N On Apr 7, 12:44 am, Taylor Singletary taylorsinglet...@twitter.com wrote: There may be others on the IP address you are using abusing the system and making you suffer as a result. Do you get a HTTP status code 420 just for unfollow requests or is it for all requests? Have you attempted to perform the operation in isolation from your servers (not tied to your application business logic, perhaps using command line tools or Curl, Twurl, etc.)? Can you do the following: 1) Issue one of the API calls you're trying to make, taking note of the exact API URL you're executing (tell me which it is) (may as well at this time verify that you're using the proper URL structures, including api.twitter.com as the domain /1/ prepending all resource URLs to indicate the API version) 2) When/if you get the the error response, capture the exact HTTP status code and the raw/exact HTTP body you get in response? (Not as interpreted by any library you're using). @episod http://twitter.com/episod - Taylor Singletary On Wed, Apr 6, 2011 at 12:07 PM, nischalshetty nischalshett...@gmail.comwrote: I cooled down my servers for more than 2 hours now. There were no activities happening through my app. I turned it back on just a few minutes back. The same problem, getting 420 error codes :( Cooling it off again, can you do something to get me out of this trouble? -N On Apr 6, 9:07 pm, nischalshetty nischalshett...@gmail.com wrote: Though I have so many users, each user has an internal limit of 100 unfollows per day which is well within any sort of limits. That is one of the reasons why I never implemented any queuing mechanism, such short number of unfollows can be done instantly. Besides, there were no sudden spikes in traffic so this sudden rate limiting baffles me. And automated unfollows are not allowed so I thought queuing wouldn't be a good idea. I'll try to implement something like that but what's the short term solution? Can you do something on your end to remove the rate limit if any that might have been put on my app? I have always adhered to twitter limits and rules never going out of my way. Please help me with this. -Nischal On Apr 6, 9:00 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: By running on Google App Engine, or any host where you share IP addresses with another service, you're going to be at a disadvantage when it comes to abuse detection -- my advice would be to ensure you have a queue system in place for API actions you take (really any application servicing anywhere near as many users as you do should have this in place), especially actions applied in bulk -- you will have times that you need to queue up your actions until you can resume making requests -- the best way to detect if you can resume making requests is by intermittently trying a single item at the top of the queue once every few seconds, increasing the duration you wait with every failed request. You never want to continue bursting when faced with an error like this, it would only make your application appear more abusive to the metrics-oriented unfeeling eye of an abuse detection algorithm. @episod http://twitter.com/episod - Taylor Singletary
[twitter-dev] Re: Getting too many login attempts error though my app uses per user auth apis
Even as I wrote this and got my servers back up, the 420 errors started all over again :( Please, can you check on your end using my app code or something. I can mail you the app id if you want. The app is justunfollow.com -N On Apr 7, 5:55 am, nischalshetty nischalshett...@gmail.com wrote: There may be others on the IP address you are using abusing the system and making you suffer as a result. Probably but then this had happened twice as I said earlier and both the times none of the api's worked until one of you guys removed the ips from the blacklist. Do you get a HTTP status code 420 just for unfollow requests or is it for all requests? Have you attempted to perform the operation in isolation from your servers (not tied to your application business logic, perhaps using command line tools or Curl, Twurl, etc.)? I'm getting it for Unfollow requests only. It does not throw errors when I try it individually even on my own server. I had a test url set up and it did not throw error on unfollowing around 200 users. That's the time I made it live for everyone but it started giving the errors in a few minutes of going live again. Can you do the following: 1) Issue one of the API calls you're trying to make, taking note of the exact API URL you're executing (tell me which it is) (may as well at this time verify that you're using the proper URL structures, including api.twitter.com as the domain /1/ prepending all resource URLs to indicate the API version) 2) When/if you get the the error response, capture the exact HTTP status code and the raw/exact HTTP body you get in response? (Not as interpreted by any library you're using). I will do this and revert back. I am using the latest version of twitter4j and it uses api.twitter.com as the end point. I had put the servers off for the last 5-6 hours now. I just turned them back up. I'm hoping the same thing does not start again :( -N On Apr 7, 12:44 am, Taylor Singletary taylorsinglet...@twitter.com wrote: There may be others on the IP address you are using abusing the system and making you suffer as a result. Do you get a HTTP status code 420 just for unfollow requests or is it for all requests? Have you attempted to perform the operation in isolation from your servers (not tied to your application business logic, perhaps using command line tools or Curl, Twurl, etc.)? Can you do the following: 1) Issue one of the API calls you're trying to make, taking note of the exact API URL you're executing (tell me which it is) (may as well at this time verify that you're using the proper URL structures, including api.twitter.com as the domain /1/ prepending all resource URLs to indicate the API version) 2) When/if you get the the error response, capture the exact HTTP status code and the raw/exact HTTP body you get in response? (Not as interpreted by any library you're using). @episod http://twitter.com/episod - Taylor Singletary On Wed, Apr 6, 2011 at 12:07 PM, nischalshetty nischalshett...@gmail.comwrote: I cooled down my servers for more than 2 hours now. There were no activities happening through my app. I turned it back on just a few minutes back. The same problem, getting 420 error codes :( Cooling it off again, can you do something to get me out of this trouble? -N On Apr 6, 9:07 pm, nischalshetty nischalshett...@gmail.com wrote: Though I have so many users, each user has an internal limit of 100 unfollows per day which is well within any sort of limits. That is one of the reasons why I never implemented any queuing mechanism, such short number of unfollows can be done instantly. Besides, there were no sudden spikes in traffic so this sudden rate limiting baffles me. And automated unfollows are not allowed so I thought queuing wouldn't be a good idea. I'll try to implement something like that but what's the short term solution? Can you do something on your end to remove the rate limit if any that might have been put on my app? I have always adhered to twitter limits and rules never going out of my way. Please help me with this. -Nischal On Apr 6, 9:00 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: By running on Google App Engine, or any host where you share IP addresses with another service, you're going to be at a disadvantage when it comes to abuse detection -- my advice would be to ensure you have a queue system in place for API actions you take (really any application servicing anywhere near as many users as you do should have this in place), especially actions applied in bulk -- you will have times that you need to queue up your actions until you can resume making requests -- the best way to detect if you can resume making requests is by intermittently trying a single item at the top
[twitter-dev] Re: Getting too many login attempts error though my app uses per user auth apis
Another thing I would like to add is along with these errors I also am getting a lot of 502 and 503 requests. Do they have to do something with this? -N On Apr 7, 5:58 am, nischalshetty nischalshett...@gmail.com wrote: Even as I wrote this and got my servers back up, the 420 errors started all over again :( Please, can you check on your end using my app code or something. I can mail you the app id if you want. The app is justunfollow.com -N On Apr 7, 5:55 am, nischalshetty nischalshett...@gmail.com wrote: There may be others on the IP address you are using abusing the system and making you suffer as a result. Probably but then this had happened twice as I said earlier and both the times none of the api's worked until one of you guys removed the ips from the blacklist. Do you get a HTTP status code 420 just for unfollow requests or is it for all requests? Have you attempted to perform the operation in isolation from your servers (not tied to your application business logic, perhaps using command line tools or Curl, Twurl, etc.)? I'm getting it for Unfollow requests only. It does not throw errors when I try it individually even on my own server. I had a test url set up and it did not throw error on unfollowing around 200 users. That's the time I made it live for everyone but it started giving the errors in a few minutes of going live again. Can you do the following: 1) Issue one of the API calls you're trying to make, taking note of the exact API URL you're executing (tell me which it is) (may as well at this time verify that you're using the proper URL structures, including api.twitter.com as the domain /1/ prepending all resource URLs to indicate the API version) 2) When/if you get the the error response, capture the exact HTTP status code and the raw/exact HTTP body you get in response? (Not as interpreted by any library you're using). I will do this and revert back. I am using the latest version of twitter4j and it uses api.twitter.com as the end point. I had put the servers off for the last 5-6 hours now. I just turned them back up. I'm hoping the same thing does not start again :( -N On Apr 7, 12:44 am, Taylor Singletary taylorsinglet...@twitter.com wrote: There may be others on the IP address you are using abusing the system and making you suffer as a result. Do you get a HTTP status code 420 just for unfollow requests or is it for all requests? Have you attempted to perform the operation in isolation from your servers (not tied to your application business logic, perhaps using command line tools or Curl, Twurl, etc.)? Can you do the following: 1) Issue one of the API calls you're trying to make, taking note of the exact API URL you're executing (tell me which it is) (may as well at this time verify that you're using the proper URL structures, including api.twitter.com as the domain /1/ prepending all resource URLs to indicate the API version) 2) When/if you get the the error response, capture the exact HTTP status code and the raw/exact HTTP body you get in response? (Not as interpreted by any library you're using). @episod http://twitter.com/episod - Taylor Singletary On Wed, Apr 6, 2011 at 12:07 PM, nischalshetty nischalshett...@gmail.comwrote: I cooled down my servers for more than 2 hours now. There were no activities happening through my app. I turned it back on just a few minutes back. The same problem, getting 420 error codes :( Cooling it off again, can you do something to get me out of this trouble? -N On Apr 6, 9:07 pm, nischalshetty nischalshett...@gmail.com wrote: Though I have so many users, each user has an internal limit of 100 unfollows per day which is well within any sort of limits. That is one of the reasons why I never implemented any queuing mechanism, such short number of unfollows can be done instantly. Besides, there were no sudden spikes in traffic so this sudden rate limiting baffles me. And automated unfollows are not allowed so I thought queuing wouldn't be a good idea. I'll try to implement something like that but what's the short term solution? Can you do something on your end to remove the rate limit if any that might have been put on my app? I have always adhered to twitter limits and rules never going out of my way. Please help me with this. -Nischal On Apr 6, 9:00 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: By running on Google App Engine, or any host where you share IP addresses with another service, you're going to be at a disadvantage when it comes to abuse detection -- my advice would be to ensure you have a queue system in place for API actions you take (really any application servicing anywhere near
[twitter-dev] Re: users/lookup returns duplicates, missing records for valid users
Hi, I too am getting duplicate results and some of the valid ids are not beings returned. If it helps, these ids would replicate all the issues faced : 11825, 248874232, 28296091, 251642658, 257793455, 225992183, 85168850, 92509004, 113697273, 99673641, 99253238, 98032551, 91619850, 47528631, 52652119, 14941300, 26403984, 33322905, 32162070, 24612782, 25218999, 20829096, 19491208, 18549369, 15074733, 13757662, 68889828 -N On Mar 2, 2:02 pm, David JULIEN da...@semiocast.com wrote: I have noticed this strange behaviour too (duplicated results and unknown users). For instance, yesterday, when I tried to lookup for user 44537294 (with two different accounts), I received during many hours information about user 243784138, before receiving expected result (around 17/18h UTC). David -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Single Sign On Using Twitter4j
Users(even though they have authenticated your app through twitter previously) would still need to authorize themselves using twitter in order for you to verify them. You won't have a way of knowing whether they are logged in to twitter. The only way for you to verify is the oAuth way. -N On Dec 3, 8:52 pm, Ganesh Sonawane ganesha.s...@gmail.com wrote: Hi All , I have developed Single Sign on using Twitter4j Api JAVA ( OAuth 2.0 framework ) it's working fine. But I have one another use case that I can't implement yet , please read following which i need same. Consider Twitter User has already linked his account with my Sample Sinlge-Sign-On Web Application. ***I have saved UID ,token ,tokensecret in mysql database 1- User is already logged in Twitter from same browser or any other browser. 2 - And if user open website URL ( in which i have implemented single sign on functionality ) he should able to access my complete Website (WebApplication) without asking his credential i.e he need not to go through authentication phase. How I can achieve this please help me. Thanks Regards Ganesh Sonawane. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Twitter followers order
As far as I know, it has always been that way. Followers are ordered based on when you follow them with the most recent follows appearing first. -N On Nov 5, 8:04 am, Senthil Kumar mastersenthilku...@gmail.com wrote: I know that previously there was no particular order in which followers were displayed. But since newTwitter, i find recent followers in the beginning of the list. So, we see followers in the order they started following us? Any help would be appreciated, thanks, Senthil Kumar. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Failed to Auth on Japanese OS
@Gary oAuth takes the current time into consideration, so that really needs to be in sync. -N On Oct 31, 2:56 am, Gary cga...@gmail.com wrote: I checked and all characters are utf-8 - the auth header and the post body. I tried installing an English OS on the same machine so it's not machine specific. I also added charset=utf-8 to the content type header: application/x-www-form-urlencoded; charset=utf-8. Still I get the Failed to validate oauth signature and token. I'm not sure what the system clock would have to do with it. On Oct 29, 1:24 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Are there any other environmental issues, such as the system clock that might be different? Are you absolutely sure that all characters are UTF-8 in both environments, regardless of language? Taylor On Fri, Oct 29, 2010 at 1:04 PM, Gary cga...@gmail.com wrote: I should add that there are no Japanese characters in the message. It's all English. In fact I did try adding Japanese characters using the Engllish OS and that worked fine. Even when I used a Japanese character password, the English OS authenticated correctly. On Oct 29, 1:01 pm, Gary cga...@gmail.com wrote: Hi, I've had great success with the Twitter API until I tried it on a Japanese version of Windows. It fails to ...validate oauth signature and token. I have captured the output using wireshark and the outgoing message is identical to the English version of Windows. This does not happen on all Japanese OS machines, though. Is there a known problem in this area? -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: How many people have authorized my application?
@Januus you could do that on your end as well, twitter doesn't restrict you from keeping a count on the number of users of your app. Nevertheless it would be awesome if twitter did it themselves, but as we can see from the reply above by @taylor they have scaling issues with the count and as far as I can tell, this would be low on their priority (any company would keep this on low priority when they have bigger problems out there to solve) -Nischal On Oct 9, 6:48 am, Jaanus jaa...@gmail.com wrote: Twitter has been advertising better analytics for themselves about users, apps, and developers, as one of the key benefits of migration to OAuth. I believe its completely true, and it would be nice if you reflected a bit of that benefit back to developers in the form of unique userIDs that have got a token for this consumer_key like it used to be on Twitter site. Even if it were with a day's lag or such, it would still be valuable to developers, it does not have to be realtime and with a load impact at all. J On Sep 29, 7:55 am, Taylor Singletary taylorsinglet...@twitter.com wrote: The loading of the information would not scale for many clients, resulting in whales when trying to load your application (lame but true). It's best to track such information by your own means. I'd be happy to look up the value for you if you follow up with me off-list. Thanks, Taylor On Wed, Sep 29, 2010 at 7:51 AM, Duane Roelands duane.roela...@gmail.com wrote: I used to be able to go tohttp://twitter.com/oauth_clientsandsee how many users have authorized my application. Twitter appears to have removed those numbers. Where can I go to find out how many people have authorized my application? Why was this information removed? -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: List of @usernames
a) I would still need to use a large number of api calls just to build the initial list Yeah, you have no choice. Even Twitter just fetches from the recent 500 followers only for autocompleting usernames. You can build your list slowly as background tasks once the user has authenticated you so that the next time the user comes to your site, all the usernames would be available. b) it requires new followers to appear on the first api call. Whilst this happens at the moment, it might not in the future. Where did you get the info from regarding it might not happen in the future? As far as I know, their persistence is such that new ids are returned first, so you don't have to worry about this for a long time. c) the api won't tell me people you have recently unfollowed Yeah, it won't. You can get the delta by retrieving all the friends and followers. d) I'd need to check for updates on a server side for each user on a frequent basis Not really frequent, most of your users won't really be gaining any significant number of followers in a single day. You can run the updates whenever they login. Instead of running a background job (if it doesn't seem feasible for many users), you can just run the updates whenever they login. -Nischal On Oct 1, 3:34 pm, artesea ryancul...@gmail.com wrote: The problem with that method is that a) I would still need to use a large number of api calls just to build the initial list b) it requires new followers to appear on the first api call. Whilst this happens at the moment, it might not in the future. c) the api won't tell me people you have recently unfollowed d) I'd need to check for updates on a server side for each user on a frequent basis if it was just for me, I'd be happy with this method (check once a day, not many changes). but for 000s of users it gets time consuming. On Sep 30, 1:24 pm, nischalshetty nischalshett...@gmail.com wrote: There's no way right now to get usernames in bulk. Get the ids, then query and get the complete info 100 at a time. You can build this for your users over time. Once list of friends for a user has been retrieved, the next time a user comes, you can just get the latest set of friends and add them to the existing records. -Nischal On Sep 30, 4:01 pm, artesea ryancul...@gmail.com wrote: I was hoping on adding some ajax code to my web app to allow auto- completing of @usernames as you start typing eg: [...@jon] �...@jonathan �...@jon_smith �...@jonny I suspect I'll need to cache the names on my server, but was wondering if there was a quick API call to get just the usernames of the people you follow. statuses/friends gets me the username, but I also end up with more data than I need (bandwidth), and have to navigate in blocks of 100s (time). friends/ids looks perfect, limited info, brings back 5000 in one go, however I only get the ids. Is there a (hidden) option to get usernames instead of ids with friends/ ? Else if I have a user who is following 3000 people I will need to cursor through the api 30 times, just to build a cache file, by the time that is complete I'm sure the user will have completed the name. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: List of @usernames
There's no way right now to get usernames in bulk. Get the ids, then query and get the complete info 100 at a time. You can build this for your users over time. Once list of friends for a user has been retrieved, the next time a user comes, you can just get the latest set of friends and add them to the existing records. -Nischal On Sep 30, 4:01 pm, artesea ryancul...@gmail.com wrote: I was hoping on adding some ajax code to my web app to allow auto- completing of @usernames as you start typing eg: [...@jon] �...@jonathan �...@jon_smith �...@jonny I suspect I'll need to cache the names on my server, but was wondering if there was a quick API call to get just the usernames of the people you follow. statuses/friends gets me the username, but I also end up with more data than I need (bandwidth), and have to navigate in blocks of 100s (time). friends/ids looks perfect, limited info, brings back 5000 in one go, however I only get the ids. Is there a (hidden) option to get usernames instead of ids with friends/ ? Else if I have a user who is following 3000 people I will need to cursor through the api 30 times, just to build a cache file, by the time that is complete I'm sure the user will have completed the name. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Getting 500:Something is broken
@Jo thnks! On Sep 29, 11:45 am, Jo Seibert joseib...@gmail.com wrote: Hi there, I discovered the same errors and was told, that these errors are a symptom of overload of the API. In this case you should handle them exactly like 502 or 503 errors. See also the discussion thread:http://groups.google.com/group/twitter-development-talk/browse_thread... And yes: I would appreciate too if the API gives the right kind of errors in these situations. Greetings. Jo Seibert On 29 Sep., 01:32, nischalshetty nischalshett...@gmail.com wrote: For many API calls (retrieving friend Ids, follower Ids) I'm getting 500:Something is broken. Please post to the group so the Twitter team can investigate. as error message. Is the twitter API having problems? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
@John thanks a lot. 2 things : 1. Requests are still timing out though at a lesser rate, I guess this should die down in some time? 2. Can we prevent this from happening? I know apps from GAE end up misusing the API and your algo blocks the IP. But, won't you be able to whitelist the good apps? So that the next time there is an IP block, the calls where a registered app sends requests, you can allow it to go through? -Nischal On Sep 28, 10:49 am, John Adams j...@twitter.com wrote: We talked with GAE and have resolved this issue. -j On Mon, Sep 27, 2010 at 7:06 PM, nischalshetty nischalshett...@gmail.comwrote: Hi John, Just got news from appengine that it is being blocked. http://twitter.com/app_engine/status/25743996553 Can you please have a check? It must be the blocking issue, had one a few months back for Appengine apps. Seems to work fine on my local dev environment. -N On Sep 28, 6:49 am, John Adams j...@twitter.com wrote: We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://www.justunfollow.comisnot able to connect to Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
@John Thanks a lot for having a second look :) I'm still getting timeouts. I understand it's difficult for you guys to determine the rogue apps. But, won't you be able to like put a check where calls that have the consumer key and secret are all allowed? -N On Sep 28, 11:19 am, John Adams j...@twitter.com wrote: The way that Google App Engine handles outbound connections is that many applications share and reuse outbound IPs from a proxy pool. This makes rate limiting much harder and determination of where abuse is sourcing from difficult to determine. The request timing out issue you're experiencing means that there are (possibly) still some IPs out of GAE that are being blocked, or some of your requests are failing. I'll have another look through our system. -j On Mon, Sep 27, 2010 at 11:09 PM, nischalshetty nischalshett...@gmail.comwrote: @John thanks a lot. 2 things : 1. Requests are still timing out though at a lesser rate, I guess this should die down in some time? 2. Can we prevent this from happening? I know apps from GAE end up misusing the API and your algo blocks the IP. But, won't you be able to whitelist the good apps? So that the next time there is an IP block, the calls where a registered app sends requests, you can allow it to go through? -Nischal On Sep 28, 10:49 am, John Adams j...@twitter.com wrote: We talked with GAE and have resolved this issue. -j On Mon, Sep 27, 2010 at 7:06 PM, nischalshetty nischalshett...@gmail.comwrote: Hi John, Just got news from appengine that it is being blocked. http://twitter.com/app_engine/status/25743996553 Can you please have a check? It must be the blocking issue, had one a few months back for Appengine apps. Seems to work fine on my local dev environment. -N On Sep 28, 6:49 am, John Adams j...@twitter.com wrote: We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://www.justunfollow.comisnotable to connect to Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
@John I'm still getting a lot of errors :( My users have been mailing me about the same, please help me with this issue. -Nischal On Sep 28, 12:34 pm, nischalshetty nischalshett...@gmail.com wrote: @John Thanks a lot for having a second look :) I'm still getting timeouts. I understand it's difficult for you guys to determine the rogue apps. But, won't you be able to like put a check where calls that have the consumer key and secret are all allowed? -N On Sep 28, 11:19 am, John Adams j...@twitter.com wrote: The way that Google App Engine handles outbound connections is that many applications share and reuse outbound IPs from a proxy pool. This makes rate limiting much harder and determination of where abuse is sourcing from difficult to determine. The request timing out issue you're experiencing means that there are (possibly) still some IPs out of GAE that are being blocked, or some of your requests are failing. I'll have another look through our system. -j On Mon, Sep 27, 2010 at 11:09 PM, nischalshetty nischalshett...@gmail.comwrote: @John thanks a lot. 2 things : 1. Requests are still timing out though at a lesser rate, I guess this should die down in some time? 2. Can we prevent this from happening? I know apps from GAE end up misusing the API and your algo blocks the IP. But, won't you be able to whitelist the good apps? So that the next time there is an IP block, the calls where a registered app sends requests, you can allow it to go through? -Nischal On Sep 28, 10:49 am, John Adams j...@twitter.com wrote: We talked with GAE and have resolved this issue. -j On Mon, Sep 27, 2010 at 7:06 PM, nischalshetty nischalshett...@gmail.comwrote: Hi John, Just got news from appengine that it is being blocked. http://twitter.com/app_engine/status/25743996553 Can you please have a check? It must be the blocking issue, had one a few months back for Appengine apps. Seems to work fine on my local dev environment. -N On Sep 28, 6:49 am, John Adams j...@twitter.com wrote: We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://www.justunfollow.comisnotableto connect to Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
It's been a long time, I'm completely helpless in this. Please look into it soon and help me out, I have thousands of users who visit the site everyday, been receiving a lot of mails and tweets regarding the errors. -Nischal On Sep 28, 1:41 pm, nischalshetty nischalshett...@gmail.com wrote: @John I'm still getting a lot of errors :( My users have been mailing me about the same, please help me with this issue. -Nischal On Sep 28, 12:34 pm, nischalshetty nischalshett...@gmail.com wrote: @John Thanks a lot for having a second look :) I'm still getting timeouts. I understand it's difficult for you guys to determine the rogue apps. But, won't you be able to like put a check where calls that have the consumer key and secret are all allowed? -N On Sep 28, 11:19 am, John Adams j...@twitter.com wrote: The way that Google App Engine handles outbound connections is that many applications share and reuse outbound IPs from a proxy pool. This makes rate limiting much harder and determination of where abuse is sourcing from difficult to determine. The request timing out issue you're experiencing means that there are (possibly) still some IPs out of GAE that are being blocked, or some of your requests are failing. I'll have another look through our system. -j On Mon, Sep 27, 2010 at 11:09 PM, nischalshetty nischalshett...@gmail.comwrote: @John thanks a lot. 2 things : 1. Requests are still timing out though at a lesser rate, I guess this should die down in some time? 2. Can we prevent this from happening? I know apps from GAE end up misusing the API and your algo blocks the IP. But, won't you be able to whitelist the good apps? So that the next time there is an IP block, the calls where a registered app sends requests, you can allow it to go through? -Nischal On Sep 28, 10:49 am, John Adams j...@twitter.com wrote: We talked with GAE and have resolved this issue. -j On Mon, Sep 27, 2010 at 7:06 PM, nischalshetty nischalshett...@gmail.comwrote: Hi John, Just got news from appengine that it is being blocked. http://twitter.com/app_engine/status/25743996553 Can you please have a check? It must be the blocking issue, had one a few months back for Appengine apps. Seems to work fine on my local dev environment. -N On Sep 28, 6:49 am, John Adams j...@twitter.com wrote: We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://www.justunfollow.comisnotabletoconnect to Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Getting 500:Something is broken
For many API calls (retrieving friend Ids, follower Ids) I'm getting 500:Something is broken. Please post to the group so the Twitter team can investigate. as error message. Is the twitter API having problems? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
@Matt thanks a lot. Not seeing the timeouts any more. 500s are everywhere but I understand from your status blog it's a known thing. Thanks for all the help. Over the Appengine group, we've been discussing about IP blocking for cloud offerings like GAE. Would you be able to help with this? Similar thing happened 2 months ago when Appengine apps were all blocked. It lasted for a long time back then as well. Would you guys not be able to allow apps that send their consumer secret and token with the requests? One rogue app on the GAE causes all other good apps to stop working. GAE is one of the best things that has happened to small time devs like me but it has its own limitations and shared IPs are one of them. But I'm pretty sure you guys at Twitter would be able to find a workaround to help us in this problem. -Nischal On Sep 29, 5:59 am, Matt Harris mhar...@twitter.com wrote: Are you still experiencing problems? We've checked our systems and have checked GAE isn't blocked. Best, @themattharris On Sep 28, 2010, at 9:23, nischalshetty nischalshett...@gmail.com wrote: It's been a long time, I'm completely helpless in this. Please look into it soon and help me out, I have thousands of users who visit the site everyday, been receiving a lot of mails and tweets regarding the errors. -Nischal On Sep 28, 1:41 pm, nischalshetty nischalshett...@gmail.com wrote: @John I'm still getting a lot of errors :( My users have been mailing me about the same, please help me with this issue. -Nischal On Sep 28, 12:34 pm, nischalshetty nischalshett...@gmail.com wrote: @John Thanks a lot for having a second look :) I'm still getting timeouts. I understand it's difficult for you guys to determine the rogue apps. But, won't you be able to like put a check where calls that have the consumer key and secret are all allowed? -N On Sep 28, 11:19 am, John Adams j...@twitter.com wrote: The way that Google App Engine handles outbound connections is that many applications share and reuse outbound IPs from a proxy pool. This makes rate limiting much harder and determination of where abuse is sourcing from difficult to determine. The request timing out issue you're experiencing means that there are (possibly) still some IPs out of GAE that are being blocked, or some of your requests are failing. I'll have another look through our system. -j On Mon, Sep 27, 2010 at 11:09 PM, nischalshetty nischalshett...@gmail.comwrote: @John thanks a lot. 2 things : 1. Requests are still timing out though at a lesser rate, I guess this should die down in some time? 2. Can we prevent this from happening? I know apps from GAE end up misusing the API and your algo blocks the IP. But, won't you be able to whitelist the good apps? So that the next time there is an IP block, the calls where a registered app sends requests, you can allow it to go through? -Nischal On Sep 28, 10:49 am, John Adams j...@twitter.com wrote: We talked with GAE and have resolved this issue. -j On Mon, Sep 27, 2010 at 7:06 PM, nischalshetty nischalshett...@gmail.comwrote: Hi John, Just got news from appengine that it is being blocked. http://twitter.com/app_engine/status/25743996553 Can you please have a check? It must be the blocking issue, had one a few months back for Appengine apps. Seems to work fine on my local dev environment. -N On Sep 28, 6:49 am, John Adams j...@twitter.com wrote: We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://www.justunfollow.comisnotabletoconnectto Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer
[twitter-dev] Not able to connect to twitter through Google Appengine, getting Timeouts
My app http://www.justunfollow.com is not able to connect to Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Not able to connect to twitter through Google Appengine, getting Timeouts
Hi John, Just got news from appengine that it is being blocked. http://twitter.com/app_engine/status/25743996553 Can you please have a check? It must be the blocking issue, had one a few months back for Appengine apps. Seems to work fine on my local dev environment. -N On Sep 28, 6:49 am, John Adams j...@twitter.com wrote: We're not currently blocking google app engine; Could you pass along some source IPs and we'll research? -john On Mon, Sep 27, 2010 at 6:25 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://www.justunfollow.comis not able to connect to Twitter from the Google Appengine. I had faced this problem a few months ago where you guys found out that the appengine IPs were being blocked due to some rogue app. Please help, thousands of my users are getting timeout errors! -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Cursors remain same or do they change?
Say, I need to retrieve friend ids of a user who has 50,000 friends. I do a get, then the subsequent gets are using the cursor returned. Now, are these cursor values the same? I mean, next time, if the users friends have increased to say 53000, can I get all the 50,000 using the old cursors and then use the cursor from the last cursor call to get the remaining 3000 friends? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: Using API to accept a follow request, but it does not clear pending request when tweets are protected.
Sending a friendships/create to follow user doesn't mean you would be accepting follow requests. As far as I can tell there's no way you can accept follow requests through the API, yet! It's on low priority for the twitter team so the chances of accepting/ rejecting follows through the API seem bleak for now! http://code.google.com/p/twitter-api/issues/detail?id=8 -N On Sep 10, 3:23 am, DaveH d...@idreia.com wrote: Here is my problem. 1. My Twitter account is set to Protect My Tweets. It is private. 2. User 1234 send a follow request to my account. 3. My application authenticates with Twitter and using the friendships/ incoming call sees that a request to follow is pending. 4. My application sends a friendships/create to follow User 1234, response is OK (200). 5. My account shows that I am now following User 1234. 5. User 1234 still shows as pending approval. This is not what I expected. I can accept the follow request via my program, but I cannot clear the pending follow request and as such, am unable to grant permission to follow my protected account via the API. Does anyone know what I am missing? Or is this one of those things that Twitter is still working on? My head hearts at this point from reading the docs and trying different things. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
[twitter-dev] Re: share images with twitter
@Aman There are sites like http://twitpic.com , http://filesocial.com , http://posterous.com etc which allow you to upload pics. You can then post the URL of the newly uploaded pics to twitter. -Nischal On Aug 20, 5:28 pm, Aman deep amansys.i...@gmail.com wrote: i am not making any spamming ok mr i am just asking solution of my problem ok ,if i am cant upload directly images to twitter then pl tell me where i have to post the link on twitter and with wich method that one please tell me aman On Thu, Aug 19, 2010 at 11:55 PM, artesea ryancul...@gmail.com wrote: Twitter takes 140 characters and posts them on their site, and allows us dev to do clever stuff with them. However images are not characters. If you want you can post links to images, but not the images themselves. Some twitter clients will recognise links to popular image hosting websites and display a thumbnail, however you can't guarantee that the client your friends are using will either show pictures or know about the site you are using. Can you please now stop spamming every other topic on this list with the same question? Ryan On Aug 18, 8:30 pm, aman amansys.i...@gmail.com wrote: dear twitter team i want to make a web application in asp.net in which i am having one page of gallery with my images and one button for share the images with twitter , i want to share these images in my account in twitter can u help me please any body and am able to post data on ur my twitter acocutn but i dont know the way to upload the images to my twitter account thnx in advance -- Amandeep Singh Software Engineer +919990834436
[twitter-dev] Application source in Direct Messages
I'm totally and unconditionally frustrated with the direct messages sent by various apps. I set out on creating a spam filter for twitter direct messages but then realized this one small thing from twitter's dev team would help everyone a lot more than any of us 3rd party devs doing it. Can we have the application source for Direct Messages as well? It'll help in identifying the source of automated direct messages and app developers can incorporate a way in which users can block messages from rogue apps. I'm really tired of being everyone's #Godfather !!
[twitter-dev] Re: Application source in Direct Messages
I've created a feature request. I request everyone to star it so that this can be done. Life would be so much simpler when users don't receive those automated direct messages! http://code.google.com/p/twitter-api/issues/detail?id=1819 -Nischal On Aug 20, 1:18 am, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: +1e9 -- M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting nischalshetty nischalshett...@gmail.com: I'm totally and unconditionally frustrated with the direct messages sent by various apps. I set out on creating a spam filter for twitter direct messages but then realized this one small thing from twitter's dev team would help everyone a lot more than any of us 3rd party devs doing it. Can we have the application source for Direct Messages as well? It'll help in identifying the source of automated direct messages and app developers can incorporate a way in which users can block messages from rogue apps. I'm really tired of being everyone's #Godfather !!
[twitter-dev] Re: Application source in Direct Messages
@andy thanks a lot. Let's hope twitter devs see this as something that is really needed right now. I've asked so many of my friends and most of them have stopped checking their direct messages altogether due to these spams! -Nischal On Aug 20, 9:31 am, Andy Matsubara andymatsub...@gmail.com wrote: Thank you. I voted it. On Fri, Aug 20, 2010 at 10:55 AM, nischalshetty nischalshett...@gmail.com wrote: I've created a feature request. I request everyone to star it so that this can be done. Life would be so much simpler when users don't receive those automated direct messages! http://code.google.com/p/twitter-api/issues/detail?id=1819 -Nischal On Aug 20, 1:18 am, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: +1e9 -- M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos Quoting nischalshetty nischalshett...@gmail.com: I'm totally and unconditionally frustrated with the direct messages sent by various apps. I set out on creating a spam filter for twitter direct messages but then realized this one small thing from twitter's dev team would help everyone a lot more than any of us 3rd party devs doing it. Can we have the application source for Direct Messages as well? It'll help in identifying the source of automated direct messages and app developers can incorporate a way in which users can block messages from rogue apps. I'm really tired of being everyone's #Godfather !!
[twitter-dev] Re: Introducing the Tweet Button
Awesome! Looks good and so many customizations while still being simple and easy to configure makes it a winner! -Nischal On Aug 12, 8:28 pm, themattharris thematthar...@twitter.com wrote: Hey everyone, Today we’re launching the Tweet Button to make it easy for your users to share your website with their followers. When they click on the Tweet Button, a Tweet box will appear pre-populated with a message and link chosen by you. Once they have sent a Tweet they can choose to follow accounts recommended by you. All of this happens on your website, so the user never has to leave. You have complete control over the suggested text of the Tweet Button, who the Tweet should be attributed to and recommendations of who to follow. All of this is possible through a line of javascript and a few URL parameters or data attributes of a link. To add this to your own site grab it fromhttp://twitter.com/tweetbutton, or create your own using our developer documentation,http://dev.twitter.com/pages/tweet_button Read more about the Tweet Button on our blog,http://blog.twitter.com/2010/08/pushing-our-tweet-button.html Best Matt -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris
[twitter-dev] Norton detects this js on my site, I'm not able to find it!
I got feedback from a few users saying Norton was identifying my site as unsafe. The script that was being displayed was https://s3.amazonaws.com/twitter_production/a/1281028705/javascripts/twitter-https.js I haven't included anything, I'm not able to find this link on my site, any idea what this can be? My site is http://www.justunfollow.com Here's the Norton report - http://safeweb.norton.com/report/show?name=justunfollow.com
[twitter-dev] Re: Norton detects this js on my site, I'm not able to find it!
Thanks a lot Tom, kinda relieved! I too wasn't able to find that script, but a couple of users pointed to the same thing. Since the link is to a file named twitter-https.js , figured it would be good to ask about it here :) -Nischal On Aug 10, 9:57 pm, Tom van der Woerdt i...@tvdw.eu wrote: On 8/10/10 6:51 PM, nischalshetty wrote: I got feedback from a few users saying Norton was identifying my site as unsafe. The script that was being displayed was https://s3.amazonaws.com/twitter_production/a/1281028705/javascripts/... I haven't included anything, I'm not able to find this link on my site, any idea what this can be? My site ishttp://www.justunfollow.com Here's the Norton report -http://safeweb.norton.com/report/show?name=justunfollow.com I just checked about 5 pages of your site and I do not see it. I checked with a javascript debugger so I also checked deferred loads. I also wonder why Norton flags that file as unsafe... Looks perfectly safe to me. Tom
[twitter-dev] Not able to connect to twitter API from Google Appengine
My app http://www.justunfollow.com is just not able to connect to twitter from Google Appengine. It's most probably an app engine issue (none of the app engine apps seem to be able to connect to twitter), but nevertheless I'm writing here to see if it so happened that twitter has blocked access to app engine. The error says : Could not fecth URL for http calls made to twitter from google Appengine -Nischal
[twitter-dev] Re: Not able to connect to twitter API from Google Appengine
@Taylor Ah! You're my hero! I've been frantically trying to get in touch with anyone and everyone over twitter and google app engine. The App engine folks are yet to read the long thread I've started in their forum. I hope if the issue is on your end you find a fix soon. It's been well over 15-20 hours since my app has been unusable, it hurts! -Nischal On Jul 23, 7:06 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi folks on Google App Engine experiencing difficulties, We're looking into it! Taylor On Fri, Jul 23, 2010 at 3:13 AM, Livid v2ex.li...@me.com wrote: I'm getting the same error for my community (with a built-in Twitter OAuth client) running on GAE:http://v2ex.appspot.com Traceback (most recent call last): File /base/python_runtime/python_lib/versions/1/google/appengine/ ext/webapp/__init__.py, line 511, in __call__ handler.get(*groups) File /base/data/home/apps/v2ex/1.343564127440067233/t.py, line 157, in get statuses = twitter.GetHomeTimeline(count = 100) File /base/data/home/apps/v2ex/1.343564127440067233/twitter/ twitter.py, line 1451, in GetHomeTimeline json = self._FetchUrl(url, parameters=parameters) File /base/data/home/apps/v2ex/1.343564127440067233/twitter/ oauthtwitter.py, line 101, in _FetchUrl url_data = opener.open(url).read() File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 381, in open response = self._open(req, data) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 399, in _open '_open', req) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 360, in _call_chain result = func(*args) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 1115, in https_open return self.do_open(httplib.HTTPSConnection, req) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 1080, in do_open r = h.getresponse() File /base/python_runtime/python_dist/lib/python2.5/httplib.py, line 197, in getresponse self._allow_truncated, self._follow_redirects) File /base/python_runtime/python_lib/versions/1/google/appengine/ api/urlfetch.py, line 241, in fetch return rpc.get_result() File /base/python_runtime/python_lib/versions/1/google/appengine/ api/apiproxy_stub_map.py, line 501, in get_result return self.__get_result_hook(self) File /base/python_runtime/python_lib/versions/1/google/appengine/ api/urlfetch.py, line 325, in _get_fetch_result raise DownloadError(str(err)) DownloadError: ApplicationError: 2 It was fine several days ago. On Jul 23, 2:15 pm, nischalshetty nischalshett...@gmail.com wrote: My apphttp://www.justunfollow.comisjust not able to connect to twitter from Google Appengine. It's most probably an app engine issue (none of the app engine apps seem to be able to connect to twitter), but nevertheless I'm writing here to see if it so happened that twitter has blocked access to app engine. The error says : Could not fecth URL for http calls made to twitter from google Appengine -Nischal
[twitter-dev] Re: Not able to connect to twitter API from Google Appengine
@Taylor The problem is even with the simple search request. So basically its for all API calls to twitter. -Nischal On Jul 23, 8:56 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hey all, We're still looking into this. To help us eliminate some possibile issues, can someone who's working behind the Google App Engine IP addresses attempt to connect to bothhttp://api.twitter.com/oauth/request_tokenandhttps://api.twitter.com/oauth/request_tokenand let us know if you're seeing a difference between the two? (I'm trying to rule out that the SSL wildcard certificate is to blame or not). Thanks, Taylor On Fri, Jul 23, 2010 at 7:45 AM, nischalshetty nischalshett...@gmail.com wrote: @Taylor Ah! You're my hero! I've been frantically trying to get in touch with anyone and everyone over twitter and google app engine. The App engine folks are yet to read the long thread I've started in their forum. I hope if the issue is on your end you find a fix soon. It's been well over 15-20 hours since my app has been unusable, it hurts! -Nischal On Jul 23, 7:06 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi folks on Google App Engine experiencing difficulties, We're looking into it! Taylor On Fri, Jul 23, 2010 at 3:13 AM, Livid v2ex.li...@me.com wrote: I'm getting the same error for my community (with a built-in Twitter OAuth client) running on GAE:http://v2ex.appspot.com Traceback (most recent call last): File /base/python_runtime/python_lib/versions/1/google/appengine/ ext/webapp/__init__.py, line 511, in __call__ handler.get(*groups) File /base/data/home/apps/v2ex/1.343564127440067233/t.py, line 157, in get statuses = twitter.GetHomeTimeline(count = 100) File /base/data/home/apps/v2ex/1.343564127440067233/twitter/ twitter.py, line 1451, in GetHomeTimeline json = self._FetchUrl(url, parameters=parameters) File /base/data/home/apps/v2ex/1.343564127440067233/twitter/ oauthtwitter.py, line 101, in _FetchUrl url_data = opener.open(url).read() File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 381, in open response = self._open(req, data) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 399, in _open '_open', req) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 360, in _call_chain result = func(*args) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 1115, in https_open return self.do_open(httplib.HTTPSConnection, req) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 1080, in do_open r = h.getresponse() File /base/python_runtime/python_dist/lib/python2.5/httplib.py, line 197, in getresponse self._allow_truncated, self._follow_redirects) File /base/python_runtime/python_lib/versions/1/google/appengine/ api/urlfetch.py, line 241, in fetch return rpc.get_result() File /base/python_runtime/python_lib/versions/1/google/appengine/ api/apiproxy_stub_map.py, line 501, in get_result return self.__get_result_hook(self) File /base/python_runtime/python_lib/versions/1/google/appengine/ api/urlfetch.py, line 325, in _get_fetch_result raise DownloadError(str(err)) DownloadError: ApplicationError: 2 It was fine several days ago. On Jul 23, 2:15 pm, nischalshetty nischalshett...@gmail.com wrote: My apphttp://www.justunfollow.comisjustnot able to connect to twitter from Google Appengine. It's most probably an app engine issue (none of the app engine apps seem to be able to connect to twitter), but nevertheless I'm writing here to see if it so happened that twitter has blocked access to app engine. The error says : Could not fecth URL for http calls made to twitter from google Appengine -Nischal
[twitter-dev] Re: Not able to connect to twitter API from Google Appengine
@Taylor Just checked. I can make calls to google.com through the appengine. So I guess its only twitter calls that are failing which means the issue is on twitter's side. I guess the appengine IPs are being blacklisted? or blocked by twitter? -Nischal On Jul 23, 9:32 pm, nischalshetty nischalshett...@gmail.com wrote: @Taylor The problem is even with the simple search request. So basically its for all API calls to twitter. -Nischal On Jul 23, 8:56 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hey all, We're still looking into this. To help us eliminate some possibile issues, can someone who's working behind the Google App Engine IP addresses attempt to connect to bothhttp://api.twitter.com/oauth/request_tokenandhttps://api.twitter.com/...let us know if you're seeing a difference between the two? (I'm trying to rule out that the SSL wildcard certificate is to blame or not). Thanks, Taylor On Fri, Jul 23, 2010 at 7:45 AM, nischalshetty nischalshett...@gmail.com wrote: @Taylor Ah! You're my hero! I've been frantically trying to get in touch with anyone and everyone over twitter and google app engine. The App engine folks are yet to read the long thread I've started in their forum. I hope if the issue is on your end you find a fix soon. It's been well over 15-20 hours since my app has been unusable, it hurts! -Nischal On Jul 23, 7:06 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi folks on Google App Engine experiencing difficulties, We're looking into it! Taylor On Fri, Jul 23, 2010 at 3:13 AM, Livid v2ex.li...@me.com wrote: I'm getting the same error for my community (with a built-in Twitter OAuth client) running on GAE:http://v2ex.appspot.com Traceback (most recent call last): File /base/python_runtime/python_lib/versions/1/google/appengine/ ext/webapp/__init__.py, line 511, in __call__ handler.get(*groups) File /base/data/home/apps/v2ex/1.343564127440067233/t.py, line 157, in get statuses = twitter.GetHomeTimeline(count = 100) File /base/data/home/apps/v2ex/1.343564127440067233/twitter/ twitter.py, line 1451, in GetHomeTimeline json = self._FetchUrl(url, parameters=parameters) File /base/data/home/apps/v2ex/1.343564127440067233/twitter/ oauthtwitter.py, line 101, in _FetchUrl url_data = opener.open(url).read() File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 381, in open response = self._open(req, data) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 399, in _open '_open', req) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 360, in _call_chain result = func(*args) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 1115, in https_open return self.do_open(httplib.HTTPSConnection, req) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 1080, in do_open r = h.getresponse() File /base/python_runtime/python_dist/lib/python2.5/httplib.py, line 197, in getresponse self._allow_truncated, self._follow_redirects) File /base/python_runtime/python_lib/versions/1/google/appengine/ api/urlfetch.py, line 241, in fetch return rpc.get_result() File /base/python_runtime/python_lib/versions/1/google/appengine/ api/apiproxy_stub_map.py, line 501, in get_result return self.__get_result_hook(self) File /base/python_runtime/python_lib/versions/1/google/appengine/ api/urlfetch.py, line 325, in _get_fetch_result raise DownloadError(str(err)) DownloadError: ApplicationError: 2 It was fine several days ago. On Jul 23, 2:15 pm, nischalshetty nischalshett...@gmail.com wrote: My apphttp://www.justunfollow.comisjustnotable to connect to twitter from Google Appengine. It's most probably an app engine issue (none of the app engine apps seem to be able to connect to twitter), but nevertheless I'm writing here to see if it so happened that twitter has blocked access to app engine. The error says : Could not fecth URL for http calls made to twitter from google Appengine -Nischal
[twitter-dev] Re: Not able to connect to twitter API from Google Appengine
Oh my GOD! I can see it working! Yippe Thank you so much. A post or update on what caused the issue would be welcome! -Nischal On Jul 23, 9:51 pm, Greg Jones psycle@gmail.com wrote: Hi Taylor, It doesn't connect to either http or https. Happy to help testing anything else...app's not live yet, but was a bit of a scare this morning! cheers, Greg On Jul 23, 5:32 pm, nischalshetty nischalshett...@gmail.com wrote: @Taylor The problem is even with the simple search request. So basically its for all API calls to twitter. -Nischal On Jul 23, 8:56 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hey all, We're still looking into this. To help us eliminate some possibile issues, can someone who's working behind the Google App Engine IP addresses attempt to connect to bothhttp://api.twitter.com/oauth/request_tokenandhttps://api.twitter.com/...us know if you're seeing a difference between the two? (I'm trying to rule out that the SSL wildcard certificate is to blame or not). Thanks, Taylor On Fri, Jul 23, 2010 at 7:45 AM, nischalshetty nischalshett...@gmail.com wrote: @Taylor Ah! You're my hero! I've been frantically trying to get in touch with anyone and everyone over twitter and google app engine. The App engine folks are yet to read the long thread I've started in their forum. I hope if the issue is on your end you find a fix soon. It's been well over 15-20 hours since my app has been unusable, it hurts! -Nischal On Jul 23, 7:06 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi folks on Google App Engine experiencing difficulties, We're looking into it! Taylor On Fri, Jul 23, 2010 at 3:13 AM, Livid v2ex.li...@me.com wrote: I'm getting the same error for my community (with a built-in Twitter OAuth client) running on GAE:http://v2ex.appspot.com Traceback (most recent call last): File /base/python_runtime/python_lib/versions/1/google/appengine/ ext/webapp/__init__.py, line 511, in __call__ handler.get(*groups) File /base/data/home/apps/v2ex/1.343564127440067233/t.py, line 157, in get statuses = twitter.GetHomeTimeline(count = 100) File /base/data/home/apps/v2ex/1.343564127440067233/twitter/ twitter.py, line 1451, in GetHomeTimeline json = self._FetchUrl(url, parameters=parameters) File /base/data/home/apps/v2ex/1.343564127440067233/twitter/ oauthtwitter.py, line 101, in _FetchUrl url_data = opener.open(url).read() File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 381, in open response = self._open(req, data) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 399, in _open '_open', req) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 360, in _call_chain result = func(*args) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 1115, in https_open return self.do_open(httplib.HTTPSConnection, req) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 1080, in do_open r = h.getresponse() File /base/python_runtime/python_dist/lib/python2.5/httplib.py, line 197, in getresponse self._allow_truncated, self._follow_redirects) File /base/python_runtime/python_lib/versions/1/google/appengine/ api/urlfetch.py, line 241, in fetch return rpc.get_result() File /base/python_runtime/python_lib/versions/1/google/appengine/ api/apiproxy_stub_map.py, line 501, in get_result return self.__get_result_hook(self) File /base/python_runtime/python_lib/versions/1/google/appengine/ api/urlfetch.py, line 325, in _get_fetch_result raise DownloadError(str(err)) DownloadError: ApplicationError: 2 It was fine several days ago. On Jul 23, 2:15 pm, nischalshetty nischalshett...@gmail.com wrote: My apphttp://www.justunfollow.comisjustnotableto connect to twitter from Google Appengine. It's most probably an app engine issue (none of the app engine apps seem to be able to connect to twitter), but nevertheless I'm writing here to see if it so happened that twitter has blocked access to app engine. The error says : Could not fecth URL for http calls made to twitter from google Appengine -Nischal
[twitter-dev] Re: Not able to connect to twitter API from Google Appengine
Alrite, I can see intermittent errors. So all's not well yet... -Nischal On Jul 23, 11:35 pm, nischalshetty nischalshett...@gmail.com wrote: Oh my GOD! I can see it working! Yippe Thank you so much. A post or update on what caused the issue would be welcome! -Nischal On Jul 23, 9:51 pm, Greg Jones psycle@gmail.com wrote: Hi Taylor, It doesn't connect to either http or https. Happy to help testing anything else...app's not live yet, but was a bit of a scare this morning! cheers, Greg On Jul 23, 5:32 pm, nischalshetty nischalshett...@gmail.com wrote: @Taylor The problem is even with the simple search request. So basically its for all API calls to twitter. -Nischal On Jul 23, 8:56 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hey all, We're still looking into this. To help us eliminate some possibile issues, can someone who's working behind the Google App Engine IP addresses attempt to connect to bothhttp://api.twitter.com/oauth/request_tokenandhttps://api.twitter.com/...know if you're seeing a difference between the two? (I'm trying to rule out that the SSL wildcard certificate is to blame or not). Thanks, Taylor On Fri, Jul 23, 2010 at 7:45 AM, nischalshetty nischalshett...@gmail.com wrote: @Taylor Ah! You're my hero! I've been frantically trying to get in touch with anyone and everyone over twitter and google app engine. The App engine folks are yet to read the long thread I've started in their forum. I hope if the issue is on your end you find a fix soon. It's been well over 15-20 hours since my app has been unusable, it hurts! -Nischal On Jul 23, 7:06 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi folks on Google App Engine experiencing difficulties, We're looking into it! Taylor On Fri, Jul 23, 2010 at 3:13 AM, Livid v2ex.li...@me.com wrote: I'm getting the same error for my community (with a built-in Twitter OAuth client) running on GAE:http://v2ex.appspot.com Traceback (most recent call last): File /base/python_runtime/python_lib/versions/1/google/appengine/ ext/webapp/__init__.py, line 511, in __call__ handler.get(*groups) File /base/data/home/apps/v2ex/1.343564127440067233/t.py, line 157, in get statuses = twitter.GetHomeTimeline(count = 100) File /base/data/home/apps/v2ex/1.343564127440067233/twitter/ twitter.py, line 1451, in GetHomeTimeline json = self._FetchUrl(url, parameters=parameters) File /base/data/home/apps/v2ex/1.343564127440067233/twitter/ oauthtwitter.py, line 101, in _FetchUrl url_data = opener.open(url).read() File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 381, in open response = self._open(req, data) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 399, in _open '_open', req) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 360, in _call_chain result = func(*args) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 1115, in https_open return self.do_open(httplib.HTTPSConnection, req) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 1080, in do_open r = h.getresponse() File /base/python_runtime/python_dist/lib/python2.5/httplib.py, line 197, in getresponse self._allow_truncated, self._follow_redirects) File /base/python_runtime/python_lib/versions/1/google/appengine/ api/urlfetch.py, line 241, in fetch return rpc.get_result() File /base/python_runtime/python_lib/versions/1/google/appengine/ api/apiproxy_stub_map.py, line 501, in get_result return self.__get_result_hook(self) File /base/python_runtime/python_lib/versions/1/google/appengine/ api/urlfetch.py, line 325, in _get_fetch_result raise DownloadError(str(err)) DownloadError: ApplicationError: 2 It was fine several days ago. On Jul 23, 2:15 pm, nischalshetty nischalshett...@gmail.com wrote: My apphttp://www.justunfollow.comisjustnotabletoconnect to twitter from Google Appengine. It's most probably an app engine issue (none of the app engine apps seem to be able to connect to twitter), but nevertheless I'm writing here to see if it so happened that twitter has blocked access to app engine. The error says : Could not fecth URL for http calls made to twitter from google Appengine -Nischal
[twitter-dev] Re: Not able to connect to twitter API from Google Appengine
@John It's hosted on the Google Appengine. I guess you guys are already on it to fix the issue. -Nischal On Jul 23, 11:55 pm, John Adams j...@twitter.com wrote: Please post or forward your app's IP range so we can investigate. Thanks. -j On Fri, Jul 23, 2010 at 11:50 AM, nischalshetty nischalshett...@gmail.comwrote: Alrite, I can see intermittent errors. So all's not well yet... -Nischal On Jul 23, 11:35 pm, nischalshetty nischalshett...@gmail.com wrote: Oh my GOD! I can see it working! Yippe Thank you so much. A post or update on what caused the issue would be welcome! -Nischal On Jul 23, 9:51 pm, Greg Jones psycle@gmail.com wrote: Hi Taylor, It doesn't connect to either http or https. Happy to help testing anything else...app's not live yet, but was a bit of a scare this morning! cheers, Greg On Jul 23, 5:32 pm, nischalshetty nischalshett...@gmail.com wrote: @Taylor The problem is even with the simple search request. So basically its for all API calls to twitter. -Nischal On Jul 23, 8:56 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hey all, We're still looking into this. To help us eliminate some possibile issues, can someone who's working behind the Google App Engine IP addresses attempt to connect to bothhttp:// api.twitter.com/oauth/request_tokenandhttps://api.twitter.com/...knowif you're seeing a difference between the two? (I'm trying to rule out that the SSL wildcard certificate is to blame or not). Thanks, Taylor On Fri, Jul 23, 2010 at 7:45 AM, nischalshetty nischalshett...@gmail.com wrote: @Taylor Ah! You're my hero! I've been frantically trying to get in touch with anyone and everyone over twitter and google app engine. The App engine folks are yet to read the long thread I've started in their forum. I hope if the issue is on your end you find a fix soon. It's been well over 15-20 hours since my app has been unusable, it hurts! -Nischal On Jul 23, 7:06 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi folks on Google App Engine experiencing difficulties, We're looking into it! Taylor On Fri, Jul 23, 2010 at 3:13 AM, Livid v2ex.li...@me.com wrote: I'm getting the same error for my community (with a built-in Twitter OAuth client) running on GAE:http://v2ex.appspot.com Traceback (most recent call last): File /base/python_runtime/python_lib/versions/1/google/appengine/ ext/webapp/__init__.py, line 511, in __call__ handler.get(*groups) File /base/data/home/apps/v2ex/1.343564127440067233/t.py, line 157, in get statuses = twitter.GetHomeTimeline(count = 100) File /base/data/home/apps/v2ex/1.343564127440067233/twitter/ twitter.py, line 1451, in GetHomeTimeline json = self._FetchUrl(url, parameters=parameters) File /base/data/home/apps/v2ex/1.343564127440067233/twitter/ oauthtwitter.py, line 101, in _FetchUrl url_data = opener.open(url).read() File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 381, in open response = self._open(req, data) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 399, in _open '_open', req) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 360, in _call_chain result = func(*args) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 1115, in https_open return self.do_open(httplib.HTTPSConnection, req) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 1080, in do_open r = h.getresponse() File /base/python_runtime/python_dist/lib/python2.5/httplib.py, line 197, in getresponse self._allow_truncated, self._follow_redirects) File /base/python_runtime/python_lib/versions/1/google/appengine/ api/urlfetch.py, line 241, in fetch return rpc.get_result() File /base/python_runtime/python_lib/versions/1/google/appengine/ api/apiproxy_stub_map.py, line 501, in get_result return self.__get_result_hook(self) File /base/python_runtime/python_lib/versions/1/google/appengine/ api/urlfetch.py, line 325, in _get_fetch_result raise DownloadError(str(err)) DownloadError: ApplicationError: 2 It was fine several days ago. On Jul 23, 2:15 pm, nischalshetty nischalshett...@gmail.com wrote: My apphttp://www.justunfollow.comisjustnotabletoconnectto twitter from Google Appengine. It's most probably an app engine issue (none of the app engine apps
[twitter-dev] Re: Not able to connect to twitter API from Google Appengine
I'm still facing issues. Please help me - http://www.justunfollow.com I have no idea about the IP addresses though. -Nischal On Jul 24, 12:26 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Everyone, Here are the details on the issues with Google App Engine. Twitter blocked a portion of the GAE network because an unknown user set up a large proxy farm, forwarding large amounts of traffic to twitter.com. This was probably an attempt to avoid our rate limits, which is against the Twitter terms of service, among other privacy and security issues. We recognize that those in shared hosting environments like Google App Engine are often held hostage by the actions of their peers and will continue to investigate ways that we can deal with issues like this without necessarily cutting off all traffic from a shared hosting services, but those operating under such circumstances should be aware that this kind of blacklisting will occur from time to time. If you continue to experience issues with your Google App Engine application, please reply to this thread with a link to your application, and, if possible, the IP address from which your remote requests are originating. Thanks, Taylor On Fri, Jul 23, 2010 at 12:08 PM, nischalshettynischalshett...@gmail.com wrote: @John It's hosted on the Google Appengine. I guess you guys are already on it to fix the issue. -Nischal On Jul 23, 11:55 pm, John Adams j...@twitter.com wrote: Please post or forward your app's IP range so we can investigate. Thanks. -j On Fri, Jul 23, 2010 at 11:50 AM, nischalshetty nischalshett...@gmail.comwrote: Alrite, I can see intermittent errors. So all's not well yet... -Nischal On Jul 23, 11:35 pm, nischalshetty nischalshett...@gmail.com wrote: Oh my GOD! I can see it working! Yippe Thank you so much. A post or update on what caused the issue would be welcome! -Nischal On Jul 23, 9:51 pm, Greg Jones psycle@gmail.com wrote: Hi Taylor, It doesn't connect to either http or https. Happy to help testing anything else...app's not live yet, but was a bit of a scare this morning! cheers, Greg On Jul 23, 5:32 pm, nischalshetty nischalshett...@gmail.com wrote: @Taylor The problem is even with the simple search request. So basically its for all API calls to twitter. -Nischal On Jul 23, 8:56 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hey all, We're still looking into this. To help us eliminate some possibile issues, can someone who's working behind the Google App Engine IP addresses attempt to connect to bothhttp:// api.twitter.com/oauth/request_tokenandhttps://api.twitter.com/...knowif you're seeing a difference between the two? (I'm trying to rule out that the SSL wildcard certificate is to blame or not). Thanks, Taylor On Fri, Jul 23, 2010 at 7:45 AM, nischalshetty nischalshett...@gmail.com wrote: @Taylor Ah! You're my hero! I've been frantically trying to get in touch with anyone and everyone over twitter and google app engine. The App engine folks are yet to read the long thread I've started in their forum. I hope if the issue is on your end you find a fix soon. It's been well over 15-20 hours since my app has been unusable, it hurts! -Nischal On Jul 23, 7:06 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi folks on Google App Engine experiencing difficulties, We're looking into it! Taylor On Fri, Jul 23, 2010 at 3:13 AM, Livid v2ex.li...@me.com wrote: I'm getting the same error for my community (with a built-in Twitter OAuth client) running on GAE:http://v2ex.appspot.com Traceback (most recent call last): File /base/python_runtime/python_lib/versions/1/google/appengine/ ext/webapp/__init__.py, line 511, in __call__ handler.get(*groups) File /base/data/home/apps/v2ex/1.343564127440067233/t.py, line 157, in get statuses = twitter.GetHomeTimeline(count = 100) File /base/data/home/apps/v2ex/1.343564127440067233/twitter/ twitter.py, line 1451, in GetHomeTimeline json = self._FetchUrl(url, parameters=parameters) File /base/data/home/apps/v2ex/1.343564127440067233/twitter/ oauthtwitter.py, line 101, in _FetchUrl url_data = opener.open(url).read() File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 381, in open response = self._open(req, data) File /base/python_runtime/python_dist/lib/python2.5/urllib2.py, line 399, in _open '_open', req
[twitter-dev] Re: Not able to connect to twitter API from Google Appengine
@John Thank you very much for lifting the ban. It's working now. Our apps depend completely on Twitter. I have been working and putting in a lot of time and effort (and money on app engine for the resources) to manage my app http://justunfollow.com My app gets a good number of users and I have been thinking of making some money off it. But, if something like this happens, all my efforts would take a beating! Can't you guys be able to determine if the app making the request is legit or not. I mean, we all use our consumer keys, at least the apps using their consumer key must be allowed to make requests. IP should come into play only when the consumer key is missing. Can this be done? -Nischal On Jul 24, 3:12 am, John Adams j...@twitter.com wrote: About thirty minutes ago we lifted all of the blocks on Google App engine IPs; You should no longer have issues connecting from GAE to us. -j On Fri, Jul 23, 2010 at 3:06 PM, Marco Gomes mvtgo...@gmail.com wrote: I am with same problema, DownloadError: ApplicationError: 2 On both my GAE apps: http://apoiomaisfeliz.appspot.com/ http://apoio.minhamarina.org.br/ Can Twitter API block the proxy farm without stopping our permitted apps? On Jul 23, 4:26 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Everyone, Here are the details on the issues with Google App Engine. Twitter blocked a portion of the GAE network because an unknown user set up a large proxy farm, forwarding large amounts of traffic to twitter.com. This was probably an attempt to avoid our rate limits, which is against the Twitter terms of service, among other privacy and security issues. We recognize that those in shared hosting environments like Google App Engine are often held hostage by the actions of their peers and will continue to investigate ways that we can deal with issues like this without necessarily cutting off all traffic from a shared hosting services, but those operating under such circumstances should be aware that this kind of blacklisting will occur from time to time. If you continue to experience issues with your Google App Engine application, please reply to this thread with a link to your application, and, if possible, the IP address from which your remote requests are originating. Thanks, Taylor On Fri, Jul 23, 2010 at 12:08 PM, nischalshetty nischalshett...@gmail.com wrote: @John It's hosted on the Google Appengine. I guess you guys are already on it to fix the issue. -Nischal On Jul 23, 11:55 pm, John Adams j...@twitter.com wrote: Please post or forward your app's IP range so we can investigate. Thanks. -j On Fri, Jul 23, 2010 at 11:50 AM, nischalshetty nischalshett...@gmail.comwrote: Alrite, I can see intermittent errors. So all's not well yet... -Nischal On Jul 23, 11:35 pm, nischalshetty nischalshett...@gmail.com wrote: Oh my GOD! I can see it working! Yippe Thank you so much. A post or update on what caused the issue would be welcome! -Nischal On Jul 23, 9:51 pm, Greg Jones psycle@gmail.com wrote: Hi Taylor, It doesn't connect to either http or https. Happy to help testing anything else...app's not live yet, but was a bit of a scare this morning! cheers, Greg On Jul 23, 5:32 pm, nischalshetty nischalshett...@gmail.com wrote: @Taylor The problem is even with the simple search request. So basically its for all API calls to twitter. -Nischal On Jul 23, 8:56 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hey all, We're still looking into this. To help us eliminate some possibile issues, can someone who's working behind the Google App Engine IP addresses attempt to connect to bothhttp:// api.twitter.com/oauth/request_tokenandhttps://api.twitter.com/...knowif you're seeing a difference between the two? (I'm trying to rule out that the SSL wildcard certificate is to blame or not). Thanks, Taylor On Fri, Jul 23, 2010 at 7:45 AM, nischalshetty nischalshett...@gmail.com wrote: @Taylor Ah! You're my hero! I've been frantically trying to get in touch with anyone and everyone over twitter and google app engine. The App engine folks are yet to read the long thread I've started in their forum. I hope if the issue is on your end you find a fix soon. It's been well over 15-20 hours since my app has been unusable, it hurts! -Nischal On Jul 23, 7:06 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi folks on Google App Engine experiencing difficulties, We're looking
[twitter-dev] Re: Bug: friends/ids returning invalid user IDs
There's nothing to worry about. Twitter periodically suspends users for spam and other rogue activities. Such suspended users might still be part of friends/ids but their profile information will not be returned. -Nischal On Jul 22, 10:56 pm, soung3 sou...@gmail.com wrote: I've encountered an issue with the friends/ids where the IDs returned can contain IDs of non-existent users. One example of this can be found when getting the friends of the user id = 16067667 (http:// api.twitter.com/1/friends/ids.xml?id=16067667). Within the IDs returned, there is a value = 28745723, which can not be found when using users/show (http://api.twitter.com/1/users/show.xml? id=28745723). Has anyone else encountered the same bug when using the friends/ids or followers/ids endpoints?
[twitter-dev] Re: Friend and Follower count - since timestamp
Hi Matt, Sure, will do that right away :) -Nischal On Jul 7, 11:13 am, Matt Harris thematthar...@twitter.com wrote: Hey Nischal, So this doesn't get lost in the email archive would you be able to create this as an enhancement request in our issue tracker:http://code.google.com/p/twitter-api/issues/list Thanks, Matt On Tue, Jul 6, 2010 at 10:00 PM, nischalshetty nischalshett...@gmail.comwrote: Thanks. That would help me in listing out new followers. But if any of a users old friends stopped following them, I wouldn't get it :( Anyways, hoping to see a 'since' param with new and deleted ids sent. I know you guys are pretty tied up with other important stuff, but hope to see this someday :) -Nischal On Jul 6, 7:04 pm, Raffi Krikorian ra...@twitter.com wrote: unfortunately, we don't yet support that functionality. the list is sorted with the newest items being first - you could grab the first page, and then go backwards until you start to see data that you've seen before. On Mon, Jul 5, 2010 at 10:34 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://justunfollow.comextensivelyuses the friends/ids and followers/ids API. Since twitter users have a lot of followers and friends and this API is paginated, I find it repetitive to use it. A since param that sends me all new friend and follower ids of a user along with the deleted ids (when someone stops being a friend or follower) would help a lot. I checked the documentation but found no mention of this. Please help! -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris
[twitter-dev] Re: Friend and Follower count - since timestamp
Raised an issue: http://code.google.com/p/twitter-api/issues/detail?id=1732 Hope one of you finds time to work on this, would be a big help for me as well whole lot of other apps that deal with a users friend and followers. -Nischal On Jul 7, 1:37 pm, nischalshetty nischalshett...@gmail.com wrote: Hi Matt, Sure, will do that right away :) -Nischal On Jul 7, 11:13 am, Matt Harris thematthar...@twitter.com wrote: Hey Nischal, So this doesn't get lost in the email archive would you be able to create this as an enhancement request in our issue tracker:http://code.google.com/p/twitter-api/issues/list Thanks, Matt On Tue, Jul 6, 2010 at 10:00 PM, nischalshetty nischalshett...@gmail.comwrote: Thanks. That would help me in listing out new followers. But if any of a users old friends stopped following them, I wouldn't get it :( Anyways, hoping to see a 'since' param with new and deleted ids sent. I know you guys are pretty tied up with other important stuff, but hope to see this someday :) -Nischal On Jul 6, 7:04 pm, Raffi Krikorian ra...@twitter.com wrote: unfortunately, we don't yet support that functionality. the list is sorted with the newest items being first - you could grab the first page, and then go backwards until you start to see data that you've seen before. On Mon, Jul 5, 2010 at 10:34 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://justunfollow.comextensivelyusesthe friends/ids and followers/ids API. Since twitter users have a lot of followers and friends and this API is paginated, I find it repetitive to use it. A since param that sends me all new friend and follower ids of a user along with the deleted ids (when someone stops being a friend or follower) would help a lot. I checked the documentation but found no mention of this. Please help! -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris
[twitter-dev] Re: Friend and Follower count - since timestamp
Thanks. That would help me in listing out new followers. But if any of a users old friends stopped following them, I wouldn't get it :( Anyways, hoping to see a 'since' param with new and deleted ids sent. I know you guys are pretty tied up with other important stuff, but hope to see this someday :) -Nischal On Jul 6, 7:04 pm, Raffi Krikorian ra...@twitter.com wrote: unfortunately, we don't yet support that functionality. the list is sorted with the newest items being first - you could grab the first page, and then go backwards until you start to see data that you've seen before. On Mon, Jul 5, 2010 at 10:34 PM, nischalshetty nischalshett...@gmail.comwrote: My apphttp://justunfollow.comextensively uses the friends/ids and followers/ids API. Since twitter users have a lot of followers and friends and this API is paginated, I find it repetitive to use it. A since param that sends me all new friend and follower ids of a user along with the deleted ids (when someone stops being a friend or follower) would help a lot. I checked the documentation but found no mention of this. Please help! -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Friend and Follower count - since timestamp
My app http://justunfollow.com extensively uses the friends/ids and followers/ids API. Since twitter users have a lot of followers and friends and this API is paginated, I find it repetitive to use it. A since param that sends me all new friend and follower ids of a user along with the deleted ids (when someone stops being a friend or follower) would help a lot. I checked the documentation but found no mention of this. Please help!
[twitter-dev] Re: What tools do you use?
I created http://JustUnfollow.com It's built on Java and hosted on the Google App Engine. Twitter4j is the twitter API for java that I make use of ( http://twitter4j.org ) -Nischal On Jun 11, 1:06 am, @IDisposable idisposa...@gmail.com wrote: Using: ASP.Net 3.5 with MVC 2.0 http://asp.net/mvc C# Microsoft SQL Server 2008 Twitter LinqToTwitterhttp://linqtotwitter.codeplex.com(thanks @JoeMayo) dotNetOAuth for oAuthhttp://code.google.com/p/dotnetoauth/(thanks @AArnott) Newtonsoft JSON.Net for JSONhttp://james.newtonking.com/projects/json-net.aspx ( Framework xUnit unit-text platformhttp://xunit.codeplex.com/(thanks @bradwilson) nInject dependency injectionhttp://ninject.org(thanks @nhokari) Log4Net for logginghttp://logging.apache.org/log4net/ MOQ for mockinghttp://code.google.com/p/moq/(thanks @kzu) Automapper for DTO to VM mappinghttp://automapper.codeplex.com/ (thanks @ehexter) UI jQuery for WebUI magichttp://jquery.com/ Link Scraping / MetaData HTML Agility Pack for metadatahttp://htmlagilitypack.codeplex.com/' Flickr REST API for photohttp://www.flickr.com/services/api/ OEmbed REST API for embeddinghttp://oembed.com/ TweetPhoto REST API for photohttp://tweetphotoapi.com/ TwitPic REST API for photohttp://twitpic.com/api.do YFrog REST API for photo/videohttp://code.google.com/p/imageshackapi/ Vimeo REST API for videohttp://www.vimeo.com/api Google DATA API for YouTube metadatahttp://code.google.com/apis/gdata/ (inhouse tons of special logic for frame-busting, etc) Link Canonicalization Bit.Ly REST APIhttp://code.google.com/p/bitly-api/wiki/ApiDocumentation Digg REST APIhttp://apidoc.digg.com/ IS.GD REST APIhttp://is.gd/api_info.php Owl.Ly REST APIhttp://ow.ly/url/shorten-url(apply at bottom) Snurl/SnipUrl REST APIhttp://snipurl.com/site/help?go=api Twurl .NL/.CC Tweetburner REST APIhttp://tweetburner.com/api StumbleUpon SU.PR REST [good luck, sorry] Untiny.Me REST API for [all others]http://untiny.me/api/(thanks @alzaid @untiny) Marc Brooks Hack Prime @Infuzhttp://infuz.comhttp://stltweets.comhttp://buzzradius.comhttp://musingmarc.blogspot.com
[twitter-dev] Re: users.lookup() pulls by friendship date
So it's the same one that I was talking about. They haven't specified any sorting rules in the doc, are you sure about it? Before all that, I hope you know that the lookup API can be used to retrieve info about ANY twitter user. So it does not matter if that user is your friend. How will the sorting be applied then? -Nischal On May 27, 5:18 am, cballou ball...@gmail.com wrote: The link is: http://dev.twitter.com/doc/get/users/lookup It actually returns the full dataset for up to 100 users. The returned data is sorted by your newest friendship in descending order. This functionality is quite minimal and could definitely be expanded upon like I suggested above. I was just wondering if there were any possibly hidden parameters I could pass in to change the count, cursor position, etc. On May 26, 1:22 am, nischalshetty nischalshett...@gmail.com wrote: Are you talking about this -http://api.twitter.com/version/users/lookup.format The above API returns whatever ids you have passed. Am I missing something? -Nischal On May 26, 4:38 am, cballou ball...@gmail.com wrote: Nobody? On May 25, 12:14 pm, cballou ball...@gmail.com wrote: I really don't like the fact that calling users.lookup() returns the last 100 users I have friended. Is there a way to retrieve users in a more random fashion or with some kind of ordering (ascending/descending)? I'm looking for more optional parameters. Suppose, for instance, that I have 500 friends. I would not want to pull my last 100 friends when making this API call. I might want to, however, pull a random sampling of 100 of those friends. I may also want to pull a particular number of friends (i.e. imposing a limit on the request). I would propose that there be additional filtering parameters for this request: sort: asc/desc/random (default desc) limit: 1-100 (default 100) Can anybody clarify and expand upon this for me?
[twitter-dev] Re: users.lookup() pulls by friendship date
Are you talking about this - http://api.twitter.com/version/users/lookup.format The above API returns whatever ids you have passed. Am I missing something? -Nischal On May 26, 4:38 am, cballou ball...@gmail.com wrote: Nobody? On May 25, 12:14 pm, cballou ball...@gmail.com wrote: I really don't like the fact that calling users.lookup() returns the last 100 users I have friended. Is there a way to retrieve users in a more random fashion or with some kind of ordering (ascending/descending)? I'm looking for more optional parameters. Suppose, for instance, that I have 500 friends. I would not want to pull my last 100 friends when making this API call. I might want to, however, pull a random sampling of 100 of those friends. I may also want to pull a particular number of friends (i.e. imposing a limit on the request). I would propose that there be additional filtering parameters for this request: sort: asc/desc/random (default desc) limit: 1-100 (default 100) Can anybody clarify and expand upon this for me?
[twitter-dev] Re: users.lookup() pulls by friendship date
Are you talking about this - http://api.twitter.com/version/users/lookup.format The above API returns whatever ids you have passed. Am I missing something? -Nischal On May 26, 4:38 am, cballou ball...@gmail.com wrote: Nobody? On May 25, 12:14 pm, cballou ball...@gmail.com wrote: I really don't like the fact that calling users.lookup() returns the last 100 users I have friended. Is there a way to retrieve users in a more random fashion or with some kind of ordering (ascending/descending)? I'm looking for more optional parameters. Suppose, for instance, that I have 500 friends. I would not want to pull my last 100 friends when making this API call. I might want to, however, pull a random sampling of 100 of those friends. I may also want to pull a particular number of friends (i.e. imposing a limit on the request). I would propose that there be additional filtering parameters for this request: sort: asc/desc/random (default desc) limit: 1-100 (default 100) Can anybody clarify and expand upon this for me?
[twitter-dev] Re: alert() in anywhere.js
One of us is crazy here. If I'm not wrong console.log belongs to firebug. Which means you will get a javascript error on ALL browsers which do not have firebug installed and running. -Nischal On May 19, 11:41 pm, Dan Webb d...@twitter.com wrote: On Wed, May 19, 2010 at 11:27 AM, Steve C st...@twitpic.com wrote: We just rolled out @anywhere yesterday and some of our users are experiencing similar issues. http://twitpic.com/1p00d6 We rolled out a fix at the weekend that we fixed all the browsers that we test under but there are obviously still some browsers getting the issue. I think we'll use console.info to display these message instead of an alert. We wanted to let developers know that they needed a clientID in the most noticable way but to avoid unintended annoyance of users we'll move to console.log. Thanks, -- Dan Webb Front-end Engineer, Platform d...@twitter.com / @danwrong +1 415 425 5631
[twitter-dev] Re: alert() in anywhere.js
Phew... I would have agreed if u guys had said I was crazy too... I follow these threads to understand and learn new stuff... :) -Nischal On May 20, 12:07 am, Steve C st...@twitpic.com wrote: I am assuming they will create a dummy function that will be used console.log is undefined- otherwise, you are very right. On May 19, 3:03 pm, nischalshetty nischalshett...@gmail.com wrote: One of us is crazy here. If I'm not wrong console.log belongs to firebug. Which means you will get a javascript error on ALL browsers which do not have firebug installed and running. -Nischal On May 19, 11:41 pm, Dan Webb d...@twitter.com wrote: On Wed, May 19, 2010 at 11:27 AM, Steve C st...@twitpic.com wrote: We just rolled out @anywhere yesterday and some of our users are experiencing similar issues. http://twitpic.com/1p00d6 We rolled out a fix at the weekend that we fixed all the browsers that we test under but there are obviously still some browsers getting the issue. I think we'll use console.info to display these message instead of an alert. We wanted to let developers know that they needed a clientID in the most noticable way but to avoid unintended annoyance of users we'll move to console.log. Thanks, -- Dan Webb Front-end Engineer, Platform d...@twitter.com / @danwrong +1 415 425 5631
[twitter-dev] Re: alert() in anywhere.js
Isn't console.log() specific to firebug? #JustSaying :) On May 16, 4:43 am, Larry la...@topsy.com wrote: Firefox 3.X is a supported browser for @anywhere and my example is properly configured, yet it triggered when it wasn't supposed to. This highlights my point of why alert() not a good choice for notification of incorrect installations. Instead maybe it should use throw(). That would be more useful to a developer and not intrusive to a user. Larry On May 15, 3:26 pm, Abraham Williams 4bra...@gmail.com wrote: I agree that @Anywhere should degrade gracefully when configured properly on unsupported platforms and not prompt incorrect alert()s. But I do think alert()s are probably the best way to notify developers of incorrect installations. Abraham On Sat, May 15, 2010 at 11:55, Larry la...@topsy.com wrote: I can reliably reproduce this with Firefox 3.0.8 at the following url: http://cornsyrup.org/~larry/anywhere/index.html Error console is reporting S.get is not a function Larry On May 15, 11:31 am, Larry la...@topsy.com wrote: Our site has been running @anywhere for over a week now without error. Yesterday my coworker was getting the alert(). He is running an older version of Firefox (3.0.8) on Ubuntu, so there might be another cause other than missing clientID or version? I still believe alert() is intrusive, especially for this case where it works fine except for this edge case. Instead of users complaining about broken hovercards, they are complaining about alert dialogs. Larry On May 14, 8:38 pm, Abraham Williams 4bra...@gmail.com wrote: Both of which are issues that will pretty much stop @Anywhere from working and need to be noticed as soon as possible at installation. Hiding them in console.log will make it more likely that @Anywhere will be installe improperly and the admins will only find out when users complain. Abraham On Fri, May 14, 2010 at 15:57, Larry la...@topsy.com wrote: I just came across a coworker's browser that triggered an alert() call from anywhere.js. While okay for development, the use of alert() is not friendly for production websites. Could these be converted console.log() or some other benign mechanism? Grepping through anywhere.js I found two instances of alert(): alert(To set up @anywhere, please provide a client ID); alert(No version matching +Z); Cheers Larry -- Abraham Williams | Developer for hire |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. -- Abraham Williams | Developer for hire |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] The most shameful bug a site can have! Fix it quickly before it causes havoc dear Twitter
Hi, TechCrunch Europe reported the bug. I hope you fix it asap. It seems to work! I'm extremely sorry, did not mean to exploit it, was just trying to ascertain if it was true. Once you are done fixing the bug, you will have the arduous task of reversing all the follows that took place by exploiting this bug. If you have an easy way to do that, well and fine. One thing I noticed, when you make someone follow you using the exploited bug, the new follower notification email is never sent. This might be of some help to you in identifying all those who exploited the bug and reverse it.
[twitter-dev] Re: The most shameful bug a site can have! Fix it quickly before it causes havoc dear Twitter
All the best to your team. Hope things turn out well for everyone :) -Nischal On May 10, 9:42 pm, Mark McBride mmcbr...@twitter.com wrote: We're aware and currently working on a fix. ---Mark http://twitter.com/mccv On Mon, May 10, 2010 at 9:37 AM, nischalshetty nischalshett...@gmail.com wrote: Hi, TechCrunch Europe reported the bug. I hope you fix it asap. It seems to work! I'm extremely sorry, did not mean to exploit it, was just trying to ascertain if it was true. Once you are done fixing the bug, you will have the arduous task of reversing all the follows that took place by exploiting this bug. If you have an easy way to do that, well and fine. One thing I noticed, when you make someone follow you using the exploited bug, the new follower notification email is never sent. This might be of some help to you in identifying all those who exploited the bug and reverse it.
[twitter-dev] Re: Search API or Streaming API?
Woops, my bad. I meant a meta search that would make use of all third party APIs to display the results. But I got your explanation. So if I intend to process the tweets and make sense of it, the Streaming API is what I would need to take a look at. But if I intend to get the search results and just display them on my site, then I guess the search API is what I should use! Pretty much clears everything, so cool! Thanks a lot! -Nischal On May 4, 3:27 am, John Kalucki j...@twitter.com wrote: If you are going to build a search engine, you'll need all of the Tweets to search over them. For this, you'll want to take the Firehose of all public statuses. http://apiwiki.twitter.com/Streaming-API-Documentation You'll need a commercial data license to do this. Email api to get started. GAE currently does not allow standing connections to the Streaming API. Also, you'll need considerably more resources than GAE to build a search engine. You'll need dozens of cores and hundreds of spindles just to get started. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sun, May 2, 2010 at 5:28 AM, nischalshetty nischalshett...@gmail.com wrote: I plan to build a search engine which would utilize the search APIs. Should I be using the Twitter Search API or the Streaming API to do the same? What is the difference between the two and would the Streaming API work on the Google App Engine?
[twitter-dev] Re: Search API or Streaming API?
Oh.. alright.. I thought GAE had multiple IP addresses... hmmm... then might have to look into Amazon Thanks a lot for the info :) -Nischal On May 4, 6:29 pm, John Kalucki j...@twitter.com wrote: Note that from GAE, your search rate will be throttled significantly, as you are sharing the Search API with every other GAE project on a single IP. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, May 4, 2010 at 12:34 AM, nischalshetty nischalshett...@gmail.com wrote: Woops, my bad. I meant a meta search that would make use of all third party APIs to display the results. But I got your explanation. So if I intend to process the tweets and make sense of it, the Streaming API is what I would need to take a look at. But if I intend to get the search results and just display them on my site, then I guess the search API is what I should use! Pretty much clears everything, so cool! Thanks a lot! -Nischal On May 4, 3:27 am, John Kalucki j...@twitter.com wrote: If you are going to build a search engine, you'll need all of the Tweets to search over them. For this, you'll want to take the Firehose of all public statuses. http://apiwiki.twitter.com/Streaming-API-Documentation You'll need a commercial data license to do this. Email api to get started. GAE currently does not allow standing connections to the Streaming API. Also, you'll need considerably more resources than GAE to build a search engine. You'll need dozens of cores and hundreds of spindles just to get started. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sun, May 2, 2010 at 5:28 AM, nischalshetty nischalshett...@gmail.com wrote: I plan to build a search engine which would utilize the search APIs. Should I be using the Twitter Search API or the Streaming API to do the same? What is the difference between the two and would the Streaming API work on the Google App Engine?
[twitter-dev] Search API or Streaming API?
I plan to build a search engine which would utilize the search APIs. Should I be using the Twitter Search API or the Streaming API to do the same? What is the difference between the two and would the Streaming API work on the Google App Engine?
[twitter-dev] Re: Issue on Follow feature
You can use http://twitter4j.org for your app. It's an open source API for Java. Has an awesome community around it as well and the developer Yusuke is smart and helpful! On Apr 12, 9:29 pm, Ernandes Jr. ernan...@gmail.com wrote: Hi all, I have been struggling to get Follow feature working on a Java API that I am working on. For every request I am getting the error bellow: hash request/1/notifications/follow/ernandesmjr.xml/request errorThere was a problem following the specified user./error /hash According to the feature's spec, I just need a simple post request to a given user, e.g.,http://api.twitter.com/1/notifications/follow/ernandesmjr.xml. To perform a quick and straighforward test, I created this HTML file: html head titleFollow Usertitle /head body form action=http://api.twitter.com/1/notifications/follow/ernandesmjr.xml; method=post input type=submit/ /form /body /html Either way, I get the same error as I get with Java. Any idea? Am I missing something? Thanks in advance. Regards, -- Ernandes Jr. - ALL programs are poems. However, NOT all programmers are poets. -- To unsubscribe, reply using remove me as the subject.
[twitter-dev] Re: Twitter4J now supports xAuth!
Hi John, Twitter4j has a very active community. Yusuke, the creator of Twitter4j is always available for help and he is an awesome programmer. You can visit http://twitter4j.org for info, examples, source code and jars needed for your development. -Nischal On Mar 12, 12:05 am, John Meyer john.l.me...@gmail.com wrote: 1. Does Twitter4J have a mailing list 2. Are there any tutorials on using Twitter4J, or any library for that matter, while using Netbeans? John Meyer Freelance Consultanthttp://www.pueblonative.com/blog If something goes wrong at the plant, blame the guy who can’t speak English. */Homer Simpson/* --- @ WiseStamp Signature http://my.wisestamp.com/link?u=42bgx5rfnpr43zfjsite=www.wisestamp.co Get it now http://my.wisestamp.com/link?u=42bgx5rfnpr43zfjsite=www.wisestamp.co... On 3/11/2010 11:46 AM, Yusuke Yamamoto wrote: Hi all, I'm glad to announce that now Twitter4J supports xAuth. http://twitter4j.org/jira/browse/TFJ-303 This release also includes a significant performance improvement. http://twitter4j.org/jira/browse/TFJ-319 You can download the latest stable build at: http://twitter4j.org/en/index.html#download http://twitter4j.org/maven2/org/twitter4j/twitter4j-core/2.1.1-SNAPSHOT/ Usage: 1. specify consumer key/secret combination with either twitter4j.properties or system properties Using twitter4j.properties: - oauth.consumerKey=[your app's consumer key] oauth.consumerSecret=[you app's consumer secret] - # twitter4j.properties should be located under either the default directory, the root of your classpath, or the WEB-INF/ directory Using system properties: -Dtwitter4j.oauth.consumerKey=[your app's consumer key] -Dtwitter4j.oauth.consumerSecret=[you app's consumer secret] 2. your code will go like this //get a Basic authenticated instance Twitter twitter = new TwitterFactory().getInstance(screenName, password); //and then you can get an AccessToken without user interaction AccessToken token = twitter.getOAuthAccessToken(); // production apps may want to persist the access token here twitter.updateStatus(new Date() + : xAuth test.); Thanks,
[twitter-dev] Re: web application launch...Tweetmasher
Nice site. I can profile it on http://twi5.com , need few more details such as your twitter handle -Nischal On Mar 8, 12:09 am, eco_bach bac...@gmail.com wrote: http://tweetmasher.com/ At the moment mostly 3d window dressing on the Twitter search api...but slowly adding new features.
