[twitter-dev] Re: weird things with statuses/user_timeline
Indeed, the response is a failwhale, which in my loop creates a return of 0 tweets, and than abandons the loop. Like you said I can put in one or two retries before breaking the loop. It is still funny though that the error happens everytime further down the loop, and stops happening once all tweets have been returned. On Apr 11, 1:20 am, Arnaud Meunier arn...@twitter.com wrote: My guess is you probably just received an HTTP 502 (FailWhale) at some point, this breaking your loop. What was the last HTTP response you received (including headers)? If it's a 502 error, just handle it in your loop (i.e. retrying after 10 seconds), and eventually reduce the count if that happens too frequently. Arnaud / @rno http://twitter.com/rno On Sun, Apr 10, 2011 at 11:32 AM, Randomness randomness.bl...@gmail.comwrote: I a trying to capture the last 3200 tweets from an authenticated user with the statuses/user_timeline method. I use count = 200 and have a function with calls the function 16 times with page being 1 to 16, so it looks like this: http://api.twitter.com/1/statuses/user_timeline.xml?user_id=.$user_id. 'count=200page='.$page.'include_rts=true'; The strange thing is that the first time for an account I only get a limited return of tweets like 800 or 1000. Then every subsequent try I get some more pages returned, until eventually I get all tweets sent by the user, or the maximum of 3200. Does anyone understand this or would this be a temporary glitch from the API ? -- 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- Hide quoted text - - Show quoted text - -- 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: weird things with statuses/user_timeline
I've seen this happen quite regularly when you have count of 200 and either rts or entities enabled. I submitted a bug report and was simply told to lower my count because the system often takes too long to process rts and entities the first time they are requested. On Apr 11, 8:35 am, Randomness randomness.bl...@gmail.com wrote: Indeed, the response is a failwhale, which in my loop creates a return of 0 tweets, and than abandons the loop. Like you said I can put in one or two retries before breaking the loop. It is still funny though that the error happens everytime further down the loop, and stops happening once all tweets have been returned. On Apr 11, 1:20 am, Arnaud Meunier arn...@twitter.com wrote: My guess is you probably just received an HTTP 502 (FailWhale) at some point, this breaking your loop. What was the last HTTP response you received (including headers)? If it's a 502 error, just handle it in your loop (i.e. retrying after 10 seconds), and eventually reduce the count if that happens too frequently. Arnaud / @rno http://twitter.com/rno On Sun, Apr 10, 2011 at 11:32 AM, Randomness randomness.bl...@gmail.comwrote: I a trying to capture the last 3200 tweets from an authenticated user with the statuses/user_timeline method. I use count = 200 and have a function with calls the function 16 times with page being 1 to 16, so it looks like this: http://api.twitter.com/1/statuses/user_timeline.xml?user_id=.$user_id. 'count=200page='.$page.'include_rts=true'; The strange thing is that the first time for an account I only get a limited return of tweets like 800 or 1000. Then every subsequent try I get some more pages returned, until eventually I get all tweets sent by the user, or the maximum of 3200. Does anyone understand this or would this be a temporary glitch from the API ? -- 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-Hide quoted text - - Show quoted text - -- 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] signature
which parameter need to generate oauth_signature? i have below data and its a desktop app. API key Consumer key Consumer secret timestamp nonce Regards, Shyam -- 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] get email address from API
I'm using twitter API to fetch user information and getting all information accept email address...i have searched in many places but not getting proper response...can anyone tell me how can i do this? or need any specific permission from twitter -- 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] Retweet_count set to 0.
Hi. When loading user_timeline for any user, all retweet_count fields are set to 0 since April 4th. Is it a bug or is it normal ? Thanks. -- 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] statuses/user_timeline: translate the date
Hi, I am new to twitter development and after looking for a while, I didn't figure out how to translate the date of my tweet. My application pushes on my website my last tweet and when I published it: 6 days ago. I would like to translate it in French. Is it possible ? If not, how could I do ? Thx you in advance for your help. Maxence -- 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
Re: [twitter-dev] get email address from API
Akhil, There is no way to do this via the Twitter API, if you need the user's email address you have to ask them for it. On 11 Apr 2011, at 08:15, Akhil wrote: I'm using twitter API to fetch user information and getting all information accept email address...i have searched in many places but not getting proper response...can anyone tell me how can i do this? or need any specific permission from twitter -- 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
Re: [twitter-dev] Retweet_count set to 0.
Hi there, We're looking into this issue and hope to have it resolved soon. @episod http://twitter.com/episod - Taylor Singletary On Mon, Apr 11, 2011 at 2:06 AM, JDNebusiness asteinm...@commentcamarche.net wrote: Hi. When loading user_timeline for any user, all retweet_count fields are set to 0 since April 4th. Is it a bug or is it normal ? Thanks. -- 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] Twitter Search API - Questions Regarding Scaling Out
I tried speaking with Ryan Sarver directly, but he's forwarding me here to the community advocates to answer. I believe this answer will need to come top down from Twitter, as it's your rate limiting that I'm most worried about. I have a technical question for all of you in regards to the Search API as I want to maintain full compliancy. Currently, the old Search API implementation (albeit slower) provides a fuller result set and allows for more flexibility in the types and combinations of searches allowed. The manner I have developed my application would allow for a number of daemonized worker instances running on different IP addresses to make calls to the search API on behalf of the stored OAuth credentials to avoid rate limiting issues. I had a conversation with the Pluggio developer in which he stated Twitter had threatened to shutdown his application if he didn't switch to a different implementation of the Search API. The problem indicated was that he was performing searches for multiple Twitter accounts, which is exactly my use case. Site streams does not make as much sense for my application given the search queries I wish to perform and the necessity for logical AND operations on geo-location. Do you foresee any problems with my current method of using different IP addresses to stay under the rate limit? I'm trying to stay in full compliance with Twitter's TOS and would love to find the most applicable and API friendly solution. I know headway is being made with Twitter's new search implementation so I would like to stay ahead of the curve and not get myself stuck in a box. I still need a method for polling for new search results (say, every 30 minutes, dependent upon the pricing plan) for non-logged in users. Below is a scaled down representation of how I'm currently handling searches to help you decide the best plan of action: 1) Searches are performed on a rolling queue basis, say one search every thirty minutes. There can be a finite number of searches per Twitter user (say 5 searches per Twitter account). There can be any number of Twitter accounts. 2) Search results are stored locally for retrieval by a javascript AJAX long-poller every minute to check for frequent changes. 3) When a user visits the search results page and filters results, no API calls to Twitter are made, only a local query is required Due to this process, the queue is constantly searching for the next searches and mentions to perform. I foresee rate limiting concerns cropping up with searches being performed for any number of users. Can you steer me in the right direction to avoid shutdown notices or access revocation? Regards, Corey @cballou -- 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: Does twitter stream API support proxy server?
Hi Zhe, On Feb 18, 10:25 pm, Zhe Chen chenzhe@gmail.com wrote: Does twitter stream API support proxy server? If so, what kind of proxy server it supports? this is independent of the API itself and needs to be supported by the library of your choice. Most of them do support proxies. Cheers Simon -- 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: Retweet_count set to 0.
I had created issue #2141 for this retweet_count set to 0 bug: http://code.google.com/p/twitter-api/issues/detail?id=2141 Without this working, a big piece of my app is broken. Thanks. On Apr 11, 7:21 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi there, We're looking into this issue and hope to have it resolved soon. @episod http://twitter.com/episod - Taylor Singletary On Mon, Apr 11, 2011 at 2:06 AM, JDNebusiness asteinm...@commentcamarche.net wrote: Hi. When loading user_timeline for any user, all retweet_count fields are set to 0 since April 4th. Is it a bug or is it normal ? Thanks. -- 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- Hide quoted text - - Show quoted text - -- 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
Re: [twitter-dev] Twitter Search API - Questions Regarding Scaling Out
I don't see an answer here, but I'll tell you how *I* would go about implementing this: 1. Switch to the Streaming API. Using Search in an application puts a strain on Twitter's servers and makes it difficult to Twitter to manage capacity. That's why it's rate-limited and why the rate limits aren't publicly disclosed. 2. If your application is a desktop application, use User Streams. If it is a server, use User Streams on a desktop or the low-frequency free access to Streaming on a server to prototype and develop. Your target for a server will be Site Streams, but that's in closed beta at the moment IIRC. 3. *Concurrently with development*, your business development / sales / marketing / planning people, or yourself, if it's a one-person shop, should be negotiating with Twitter for access to Site Streams, I'm assuming an agile development methodology - customer-in-the-loop - and one of the parties that needs to be in the loop is Twitter for Site Streams. You simply *can't* build an at-scale Twitter application without direct business discussions with Twitter! On Mon, Apr 11, 2011 at 8:14 AM, Corey Ballou ball...@gmail.com wrote: I tried speaking with Ryan Sarver directly, but he's forwarding me here to the community advocates to answer. I believe this answer will need to come top down from Twitter, as it's your rate limiting that I'm most worried about. I have a technical question for all of you in regards to the Search API as I want to maintain full compliancy. Currently, the old Search API implementation (albeit slower) provides a fuller result set and allows for more flexibility in the types and combinations of searches allowed. The manner I have developed my application would allow for a number of daemonized worker instances running on different IP addresses to make calls to the search API on behalf of the stored OAuth credentials to avoid rate limiting issues. I had a conversation with the Pluggio developer in which he stated Twitter had threatened to shutdown his application if he didn't switch to a different implementation of the Search API. The problem indicated was that he was performing searches for multiple Twitter accounts, which is exactly my use case. Site streams does not make as much sense for my application given the search queries I wish to perform and the necessity for logical AND operations on geo-location. Do you foresee any problems with my current method of using different IP addresses to stay under the rate limit? I'm trying to stay in full compliance with Twitter's TOS and would love to find the most applicable and API friendly solution. I know headway is being made with Twitter's new search implementation so I would like to stay ahead of the curve and not get myself stuck in a box. I still need a method for polling for new search results (say, every 30 minutes, dependent upon the pricing plan) for non-logged in users. Below is a scaled down representation of how I'm currently handling searches to help you decide the best plan of action: 1) Searches are performed on a rolling queue basis, say one search every thirty minutes. There can be a finite number of searches per Twitter user (say 5 searches per Twitter account). There can be any number of Twitter accounts. 2) Search results are stored locally for retrieval by a javascript AJAX long-poller every minute to check for frequent changes. 3) When a user visits the search results page and filters results, no API calls to Twitter are made, only a local query is required Due to this process, the queue is constantly searching for the next searches and mentions to perform. I foresee rate limiting concerns cropping up with searches being performed for any number of users. Can you steer me in the right direction to avoid shutdown notices or access revocation? Regards, Corey @cballou -- 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 -- http://twitter.com/znmeb http://borasky-research.net A mathematician is a device for turning coffee into theorems. -- Paul Erdős -- 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: Tweet Button vs ?Status=
Nice! I didn't realize the intent page had the related and via parameters! Great compromise between the aforementioned 2 options. Thanks guys! -- 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] Winterwell JTwitter API with Apache proxy cause Connection refuse
Hello All, Does Twitter not allow connections through forward proxies like Apache proxy? My apache proxy does a hard redirect to any try to connect to Twitter.com. I am using Winterwell JTwitter API to tweet. When I try to use wget with the forward proxy this is the stack trace --2011-04-11 12:52:09-- http://dvltps015.X.com:7080/twitter Resolving dvltps015.X.com... 10.5.1.82 Connecting to dvltps015.X.com|10.5.1.82|:7080... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: http://twitter.com/ [following] --2011-04-11 12:52:09-- http://twitter.com/ Resolving twitter.com... 199.59.148.10, 199.59.148.82, 199.59.148.83 Connecting to twitter.com|199.59.148.10|:80... failed: Connection refused. Connecting to twitter.com|199.59.148.82|:80... failed: Connection refused. Connecting to twitter.com|199.59.148.83|:80... failed: Connection refused. Architecture, we are using Java6 to run the application on JBoss4.3 on RHEL5. The application server has Apache proxy acting as forward proxy helping it to connect to internet. Problem, when I am trying to tweet using my Java application I get this error message. Create clientwinterwell.jtwitter.OAuthSignpostClient[name=null, password=null] Set providerwinterwell.jtwitter.OAuthSignpostClient[name=null, password=null] Created Twitterwinterwell.jtwitter.Twitter@32c41a Exception in thread main winterwell.jtwitter.TwitterException: java.net.ConnectException: Connection refused at winterwell.jtwitter.OAuthSignpostClient.post(OAuthSignpostClient.java: 134) at winterwell.jtwitter.Twitter.updateStatus(Twitter.java:3062) at winterwell.jtwitter.Twitter.updateStatus(Twitter.java:3003) at winterwell.jtwitter.Twitter.setStatus(Twitter.java:2762) at DtiwanTestURLConnect.main(DtiwanTestURLConnect.java:45) Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java: 333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.Socket.connect(Socket.java:520) at java.net.Socket.connect(Socket.java:470) at sun.net.NetworkClient.doConnect(NetworkClient.java:157) at sun.net.www.http.HttpClient.openServer(HttpClient.java:388) at sun.net.www.http.HttpClient.openServer(HttpClient.java:523) at sun.net.www.http.HttpClient.init(HttpClient.java:231) at sun.net.www.http.HttpClient.New(HttpClient.java:304) at sun.net.www.http.HttpClient.New(HttpClient.java:321) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java: 813) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java: 765) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java: 690) at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java: 857) at winterwell.jtwitter.OAuthSignpostClient.post(OAuthSignpostClient.java: 125) ... 4 more Thanks in advance, Deepam -- 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
Re: [twitter-dev] Tweet Button Display Issue
Hey Sam, Can you share the HTML you are using to markup the Tweet Button so we can see what the issue could be. Thanks, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Mon, Apr 11, 2011 at 3:37 AM, Sam Hughes samvhug...@googlemail.comwrote: Hey guys, I am trying to customize some tweet buttons so that when clicked on the pop-up opens and the tweet text is something I have wrote. I know that the tweet button has this functionality, but when I try to embed the code onto any site the text reverts so that it tweets the page title that the Tweet button sits on. Anyone know why this isn't working? or know any good work arounds? Cheers, Sam -- 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] Confused about rate limits
Hey guys, maybe this question has been asked before, but I just joined the group. I just ran into a little problem that threw me off. I'm developing a website that uses the REST API extensively. The documentation says that anonymous requests get limited to 150 requests/ hour/IP and authenticated requests get limited to 350 requests/hour/ user. I did the anonymous request to account/rate_limit_status and I got 150; and then I authenticated, verified the credentials and queried account/rate_limit_status again. Got the same result. Why is that? When you are authenticated, aren't you supposed to get 350 back from account/rate_limit_status? Thanks in advance. Alin -- 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 Search API - Questions Regarding Scaling Out
Thanks for the reply, I appreciate it. I have concerns regarding the streaming APIs, which mainly concern the following: * usage of logical OR when using locations * firehose limitations * the user’s location field is not used to filter tweets * increased application complexity for parsing the resulting stream of data back out into individual searches I know that the Search API is not Twitter's preferred choice, but it's currently returning the best applicable results for my application. It's also worth noting that the API recently received a drastic improvement to speed which should theoretically relax the strain on the API: http://engineering.twitter.com/2011/04/twitter-search-is-now-3x-faster_1656.html I guess I'm mainly interested in knowing whether @twitterapi will allow me to use the Search API in the manner I indicated above? Essentially I would be willing to guarantee the application worker nodes handles 420 rate limiting errors accordingly while still supporting multiple twitter accounts and searches. On Apr 11, 1:05 pm, M. Edward (Ed) Borasky zn...@borasky- research.net wrote: I don't see an answer here, but I'll tell you how *I* would go about implementing this: 1. Switch to the Streaming API. Using Search in an application puts a strain on Twitter's servers and makes it difficult to Twitter to manage capacity. That's why it's rate-limited and why the rate limits aren't publicly disclosed. 2. If your application is a desktop application, use User Streams. If it is a server, use User Streams on a desktop or the low-frequency free access to Streaming on a server to prototype and develop. Your target for a server will be Site Streams, but that's in closed beta at the moment IIRC. 3. *Concurrently with development*, your business development / sales / marketing / planning people, or yourself, if it's a one-person shop, should be negotiating with Twitter for access to Site Streams, I'm assuming an agile development methodology - customer-in-the-loop - and one of the parties that needs to be in the loop is Twitter for Site Streams. You simply *can't* build an at-scale Twitter application without direct business discussions with Twitter! On Mon, Apr 11, 2011 at 8:14 AM, Corey Ballou ball...@gmail.com wrote: I tried speaking with Ryan Sarver directly, but he's forwarding me here to the community advocates to answer. I believe this answer will need to come top down from Twitter, as it's your rate limiting that I'm most worried about. I have a technical question for all of you in regards to the Search API as I want to maintain full compliancy. Currently, the old Search API implementation (albeit slower) provides a fuller result set and allows for more flexibility in the types and combinations of searches allowed. The manner I have developed my application would allow for a number of daemonized worker instances running on different IP addresses to make calls to the search API on behalf of the stored OAuth credentials to avoid rate limiting issues. I had a conversation with the Pluggio developer in which he stated Twitter had threatened to shutdown his application if he didn't switch to a different implementation of the Search API. The problem indicated was that he was performing searches for multiple Twitter accounts, which is exactly my use case. Site streams does not make as much sense for my application given the search queries I wish to perform and the necessity for logical AND operations on geo-location. Do you foresee any problems with my current method of using different IP addresses to stay under the rate limit? I'm trying to stay in full compliance with Twitter's TOS and would love to find the most applicable and API friendly solution. I know headway is being made with Twitter's new search implementation so I would like to stay ahead of the curve and not get myself stuck in a box. I still need a method for polling for new search results (say, every 30 minutes, dependent upon the pricing plan) for non-logged in users. Below is a scaled down representation of how I'm currently handling searches to help you decide the best plan of action: 1) Searches are performed on a rolling queue basis, say one search every thirty minutes. There can be a finite number of searches per Twitter user (say 5 searches per Twitter account). There can be any number of Twitter accounts. 2) Search results are stored locally for retrieval by a javascript AJAX long-poller every minute to check for frequent changes. 3) When a user visits the search results page and filters results, no API calls to Twitter are made, only a local query is required Due to this process, the queue is constantly searching for the next searches and mentions to perform. I foresee rate limiting concerns cropping up with searches being performed for any number of users. Can you steer me in the right direction to avoid shutdown
[twitter-dev] Re: The thinking behind not drawing attention to Unfollows?
I just wanted to make clear that I was in no way questioning the rule. I was just curious about the reasoning behind it, from Twitter's POV. I, of course, came to the same logical conclusion that you did, Nick. That it was simply to maintain a positive atmosphere and avoid contention. Thanks for your thoughtful replies. - John On Apr 9, 8:51 pm, nickmilon nickmi...@gmail.com wrote: The intentions behind the rule is good, but what about the following list of applications (and many more) that do not respect the TOS ? http://mashable.com/2010/08/09/track-twitter-unfollowers/ happy coding :-) Nick On Apr 9, 5:05 am, Nicholas Chase nch...@earthlink.net wrote: From a user perspective, I think it's good to know that you can unfollow someone without them noticing, so you don't hurt their feelings. The last thing that Twitter wants is to be linked to hard feelings between people. But that's just my opinion. YMMV, but I wouldn't be surprised if that were the reason. Nick On 4/8/2011 9:57 PM, Whonew wrote: Could someone from the Twitter staff go into some detail about why the Terms of Service stress not drawing attention to user's Unfollows? I have no particular interest in doing so; but I have been struggling to figure out why as I'm certain that many users would like to know without jumping through hoops. Thanks a lot! -- 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] PHP and phpBB3 Integration
I run a for fun website, and found a nice widget for Twitter integration. What I was hoping to do, is find a widget, than perform an SQL SELECT QUERY from a TABLE storing user information, For say a field called Twitter_ID. Take the value if Twitter_ID, and have that value inserted into a script that parses the twitter feed for that value, and displays it in that javascript widget. It would give user based content sites, a customer twitter widget per user.via the SQL SELECT. -- 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] Domain search fails with www prefix
Hi all, I dev for an application where we do timely domain-based searches for all recent tweets involving that domain. Part of the queueing process is automated, and has been working brilliantly, until i discovered an odd quirk just this morning. Let's say a tweet was made linking to www.example.com/one/long/uri (shortened via t.co), and i do a search: http://search.twitter.com/search.json?since_id=q=www.example.comrpp=100 That search will fail to find the tweet in question. But this will succeed: http://search.twitter.com/search.json?since_id=q=example.comrpp=100 Having noticed exactly this (on a real client's domain), i looked through our DB to notice that no searches on domains prefixed with www. domains had ever succeeded, and a quick sampling showed that tweets had been made on those domains, provided i excised the 'www.' from the search term. I couldn't find this behaviour documented anywhere, and i'm wondering - can it be trusted? If i start stripping www. from my search terms, is it a reasonable expectation that tweets linking to the www. subdomain (and shortened versions of those links) will continue to show in the search? Thanks, Phil -- 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
Re: [twitter-dev] Confused about rate limits
Hey Alin, What do you mean by *I authenticated, verified the credentials and ** queried*? In this context (API call) authenticating means signing your request using OAuth. Signing-in with your account on twitter.com is a completely different thing and has no effect on your API requests. Arnaud / @rno http://twitter.com/rno On Mon, Apr 11, 2011 at 12:48 PM, impeto impet...@gmail.com wrote: Hey guys, maybe this question has been asked before, but I just joined the group. I just ran into a little problem that threw me off. I'm developing a website that uses the REST API extensively. The documentation says that anonymous requests get limited to 150 requests/ hour/IP and authenticated requests get limited to 350 requests/hour/ user. I did the anonymous request to account/rate_limit_status and I got 150; and then I authenticated, verified the credentials and queried account/rate_limit_status again. Got the same result. Why is that? When you are authenticated, aren't you supposed to get 350 back from account/rate_limit_status? Thanks in advance. Alin -- 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
