[twitter-dev] Getting any users home timeline
So the statuses/friends_timeline api call gives an authentated users and his friends statuses. Basically that authentacted users home page. Now is there any similar way to get any users home timeline. statuses/ user_timeline gives the statuses for any user specified by a userid. But it gives what is posted by them only. An e.g to clear things up User X is authenticated through API. the App makes a call and gets his home timeline using statuses/ friends_timeline . User X has a friend User Y. App can call statuses/user_timeline for user Y but that will return only User Ys statutes (which can also be got from statuses/friends_timeline earlier). What i want is an easy way so the the App can get User Y;s home time- line ( User Ys statuses as well User Y friends statuses). One can find User Ys friends and then call statuses/user_timeline for each of friend to get what i want. Seems to expensive in terms of api calls Any better way of doing this? i could not see the api supporting this directly. --dharmesh
[twitter-dev] user_timeline API call returning a HTTP 301 response??
Hey Guys, I am the developer of a Twitter to Facebook sync app, and I noticed that in the last 12 hrs I have been occasionally receiving the following response to my user_timeline API call: !DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN htmlhead title301 Moved Permanently/title /headbody h1Moved Permanently/h1 pThe document has moved a href=http://twitter.com/statuses/ user_timeline.xml? oauth_version=1.0amp;oauth_nonce=xxxamp;oauth_timestamp=1252051201amp;oauth_consumer_key=xamp;since_id=amp;oauth_token=xxxamp;oauth_signature_method=HMAC- SHA1amp;oauth_signature=xhere/ a./p /body/html This app has been up and running for a couple of weeks now and have never seen this response before (it's not listed as a valid response on the API wiki). I'm guessing this is not normal or expected behaviour? Best Regards, Jason
[twitter-dev] Allowing password update or stopping allowing email update via api
I was wondering why we can not set user password via the user_update method. Email can be updated this way, and a bad app could then use the http://twitter.com/account/resend_password form to steal some twitter accounts. Maybe the user_update method shouldnt be able to update email. Or maybe creating a third access level would be an option (read, read / write, update email or password)..
[twitter-dev] Re: large user base push notification solutions?
Apple push notification for iPhone works when the app is closed. In that case the iPhone client is not able to pull data. Meanwhile users want any mentions or DMs to pushed to them when the iPhone client is closed. So we must use a server to check DM Mentions for users. On Aug 21, 8:10 pm, Andrew Badera and...@badera.us wrote: If you're already talking about a 2-minute delay, then why push and not pull ?? Polling clients will give you greater scalability with that range of latency easily achievable for little investment.Pushis meant for immediate notifications. Truepushto 500k+ clients is costly -- but you don't need millisecond latency here. Pull is much, much cheaper. ∞ Andy Badera ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera) On Fri, Aug 21, 2009 at 8:07 AM, Dewald Pretoriusdpr...@gmail.com wrote: In addition, your database will have to cope with 8,300 writes per second. And then you need to take into account the latency of the ApplePushNotificationservice. Dewald On Aug 21, 8:57 am, Dewald Pretorius dpr...@gmail.com wrote: On Aug 21, 12:06 am, ke...@nibirutech.com intelligent...@gmail.com wrote: What if we have a large user base, say , 500, 000 users at least? How can we use a proper solution to get a 2-minutes delaypush for any user's mentions and DMs? (we can't afford the server cost for half million requests every 2 minutes) You are actually talking about one million API calls every 2 minutes (1 for mentions, one for DMs). That's 8,300 API calls per second. My rough estimate is that you are going to need around 200 servers to cope with that workload. Dewald
[twitter-dev] Counter for rate limit remaining requests unreliable, often reaches 0 unduly
I'm having this problem for a few days, and I've been monitoring ALL requests sent to twitter, here is what I saw : The value of the X-RateLimit-Remaining header is totally unreliable. For instance, the response to a request will have it at 120, while the next response will have it at 40. Then subsequent request responses will have values such as 118, 39, 37, 36, 117, ... and so on. All responses have the same X-RateLimit-Reset ! It all looks like there are 2 unsynchronized counters, and responses get values from either one of them... The trouble is that one counter reaches 0 much too early, which makes my twitter client says the maximum allowed request has been reached !! I make 3 requests every 2 minutes, so I should never reach the max. I have the exact same behavior when using the rate_limit_status request. I made sure I have no other client on that account, and I can reproduce the problem each time. Even if I had, there would not be cases where it goes from 36 to 117 for 2 adjacent requests... Thanks for looking into that ! (I can provide traces of the requests) Regards, Xavier
[twitter-dev] Re: large user base push notification solutions?
Great ideas. thanks a lot. Based on your data: 40,000 users, pull every 15 minutes, that means 44.5 requests/ second. Do you pull the data for everyone , or are there any short cuts that we can save server load? Also, did you do DMs as well? if so then you will need to deal 90 requests/second. Can a single VPS do that? which VPS provider? I want to buy that VPS :) On Aug 21, 8:28 pm, Paul Kinlan paul.kin...@gmail.com wrote: When I developed Twe2, here are some of the things I have learnt - 2 minute delay is pretty short - users don't even notice it that much - at one point on Twe2 we changed it to a 15 minute delay an no one really complained. If users are getting pushed notifications they are normally away from a main terminal and thus are not watching twitter through TweetDeck; in short you don't need realtime to be that realtime - Also 99.99% of people don't get that many notifications a day, polling too often is a waste of time. - We supported about 40,000 users off 1 small VPS. - To get DM's you will need to use the users credentials (oauth or otherwise), a 2 minute interval means that you will use 30 of the users requests per hour (this might have changed) and as such they might get annoyed. - 500,000 users is pretty optimistic I wouldn't even worry about that scale just yet, just get your stuff working for now. - User since_id everywhere you can. - We launched with the ability to have quiet periods, that is no notifications while I am sleeping - people will thank you for this. Based on new developments of Twitter you can use something like follow, shadow and birddog - it offers a migration plan too, start with follow to get all the tweets from a user and to a user (200 users is good to test your API works), then when you launch request twitter to allow you to use shadow (50,000 users is a lot and will probably suit your app for a long time). Then as soon as you see a tweet on the stream you know it is for some of your users and you can fire it straight to them. the only issue is that these API's only get proper replies and not mentions. Currently none of the Streaming API's will help you for DM's (AFAIK). Paul Kinlan,http://www.Twollo.com 2009/8/21 ke...@nibirutech.com intelligent...@gmail.com Hi I am a developer , trying to figure out a way to develop a push notification solution for iPhone users. The easy way to do the push work, is to have a cron-job to check users' new mentions and DMs. It should work for small number of users. What if we have a large user base, say , 500, 000 users at least? How can we use a proper solution to get a 2-minutes delay push for any user's mentions and DMs? (we can't afford the server cost for half million requests every 2 minutes) I know there are a few Twitter push clients for iPhone , but none of them can work on a scaled user base, am I right? Is there a twitter tech support here? could you please give some suggestions?
[twitter-dev] Re: Counter for rate limit remaining requests unreliable, often reaches 0 unduly
According to the last api request you've done, X-RateLimit-Remaining can be user limit or IP limit (depends if you made an authentified request or not). This can explain the X-RateLimit-Remaining values you've posted. On Sep 4, 11:03 am, Reivax xavier.yo...@gmail.com wrote: I'm having this problem for a few days, and I've been monitoring ALL requests sent to twitter, here is what I saw : The value of the X-RateLimit-Remaining header is totally unreliable. For instance, the response to a request will have it at 120, while the next response will have it at 40. Then subsequent request responses will have values such as 118, 39, 37, 36, 117, ... and so on. All responses have the same X-RateLimit-Reset ! It all looks like there are 2 unsynchronized counters, and responses get values from either one of them... The trouble is that one counter reaches 0 much too early, which makes my twitter client says the maximum allowed request has been reached !! I make 3 requests every 2 minutes, so I should never reach the max. I have the exact same behavior when using the rate_limit_status request. I made sure I have no other client on that account, and I can reproduce the problem each time. Even if I had, there would not be cases where it goes from 36 to 117 for 2 adjacent requests... Thanks for looking into that ! (I can provide traces of the requests) Regards, Xavier
[twitter-dev] How to find people by api
Hi all, How we can find the people with the twitter API. We are not getting which method using for the. Anybody help me. Thanks Samal Pramod.
[twitter-dev] Re: Counter for rate limit remaining requests unreliable, often reaches 0 unduly
All requests are done authentified. Thanks Xavier On Sep 4, 11:26 am, fbparis fbou...@gmail.com wrote: According to the last api request you've done, X-RateLimit-Remaining can be user limit or IP limit (depends if you made an authentified request or not). This can explain the X-RateLimit-Remaining values you've posted. On Sep 4, 11:03 am, Reivax xavier.yo...@gmail.com wrote: I'm having this problem for a few days, and I've been monitoring ALL requests sent to twitter, here is what I saw : The value of the X-RateLimit-Remaining header is totally unreliable. For instance, the response to a request will have it at 120, while the next response will have it at 40. Then subsequent request responses will have values such as 118, 39, 37, 36, 117, ... and so on. All responses have the same X-RateLimit-Reset ! It all looks like there are 2 unsynchronized counters, and responses get values from either one of them... The trouble is that one counter reaches 0 much too early, which makes my twitter client says the maximum allowed request has been reached !! I make 3 requests every 2 minutes, so I should never reach the max. I have the exact same behavior when using the rate_limit_status request. I made sure I have no other client on that account, and I can reproduce the problem each time. Even if I had, there would not be cases where it goes from 36 to 117 for 2 adjacent requests... Thanks for looking into that ! (I can provide traces of the requests) Regards, Xavier
[twitter-dev] formatting post time
I would like some information about how to make the post date / time appear with one break below the tweet and right justified even if the tweet is left justified. I'm currently using Widgets by Twitter. should I be using something else to achieve this? Thanks, ~reblis
[twitter-dev] Search API cache HELP
From time to time some new Tweets would not be included in the query result, it seems like cache on the query on twitter side but it doesn't make any sense. For example right now http://search.twitter.com/search.atom?q=+nyfw+OR+%23nyfw+from%3AThisThatBeautyrpp=20 does not include the last 2 tweets that meet the search criteria. If I change the query to http://search.twitter.com/search.atom?q=+nyfw+from%3AThisThatBeautyrpp=20 it will include those tweets but later this query may have the same issue with newer tweets not returned. I have tried many: including/excluding the rpp param, including/ excluding the page=1 param, adding some random number at the end of the query to override local caching, etc. however nothing works. Ideas?
[twitter-dev] A few simple Search API questions
My app needs to retrieve tweets that match a specific phrase: 1- How many searches are allowed from a single IP address per hour? I'm thinking of doing one per minute, is that too many? 2- I cannot find examples of phrase-based searches in the API docs. Can someone post a working example of a curl search that requires a phrase match? Owkaye
[twitter-dev] Re: How to find people by api
no method exists. On Fri, Sep 4, 2009 at 03:21, HelloPK samalpra...@gmail.com wrote: Hi all, How we can find the people with the twitter API. We are not getting which method using for the. Anybody help me. Thanks Samal Pramod. -- Internets. Serious business.
[twitter-dev] Re: Mobile oAuth
I am also interested in mobile oath solution. twitter guys should think of something before deprecating basic auth On Aug 20, 8:01 am, Cameron Kaiser spec...@floodgap.com wrote: I have a mobile based twitter client in the field and have implemented oAuth for this client. Some of the devices are either very low memory or have primitive browsers that dont support the rendering of the 'allow' / 'deny' access page (http://twitter.com/oauth/authorize). I have tried the obvioushttp://m.twitter.com/oauth/authorizebut this seems to serve the same standard webage. So Im looking for nat previous info or plans of a lightweight implementation of oAuth access page for twitter. I'm also particularly interested in such a page, especially one a text browser could access such as Lynx or w3m. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- Adore, v.: To venerate expectantly. -- Ambrose Bierce --
[twitter-dev] Re: OAuth + Mobile nightmare
in addition to storing the access token somewhere , wouldn't it be better if twitter deliver mobile friendly version of the oauth pages? On Aug 19, 12:14 am, JDG ghil...@gmail.com wrote: That's what you should be doing. There's no reason to get a new Access Token every time. Per the OAuth spec, you should probably code your app to handle an expired token gracefully. The spec states that tokens MAY expire -- Twitter currently does not expire theirs, though. However, that doesn't mean that they couldn't in the future. 2009/8/18 André Arruda arrud...@gmail.com I'm thinking about storing the access token in the phone so the user won't have to go through all the auth process everytime the program is opened. I hope i won't find any new surprises by doing this. 2009/8/18 Otávio Ribeiro otavio.ribe...@gmail.com no.. just the same problem. On Mon, Aug 17, 2009 at 3:09 PM, AArruda arrud...@gmail.com wrote: I've been developing a Java/MIDP Twitter client for the past two months, and i still need a couple more months to publish a beta version. A few days ago i found out that the update source (app name) is no longer customizable unless the client uses OAuth for authentication, which means that any update sent through my client is shown as from API instead of my app's name. I understand that OAuth is important for many security reasons, but it still has important issues with mobile applications, forcing the user to open a page through a mobile device, writing down the PIN, switching back to the app and logging in again is just hell. Not to mention the smartphones that don't support programs running in the background. The current API's methods shouldn't be restricted to OAuth unless these issues are solved first. We, developers and mobile users, would be thankful. Is anyone using any other solution for OAuth and mobile devices, if there is any? -- Internets. Serious business.
[twitter-dev] Whitelist domain name instead of IP
My IP is already whitelisted but is it possible to whitelist the domain, because my app will be in trouble if they change my IP from the hosting center?
[twitter-dev] Re: Search API Rate Limiting and Performance
Search API will rock if it would only be reliable what we see looks to be some sort of a funky cache, a query (atom) can be missing some latest tweets and then after a while they show up, if you tweak the query you can see 'em. you ever seen this problem? also what did you do special with user agent? On Sep 2, 12:12 pm, Amitab hiamita...@gmail.com wrote: I have exchanged emails with Twitter on this and I believe they are working on it. We use search extensively atwww.Twaller.com. The errors in search that we are seing is as follows: (1) HTTP status code: 403 Message:The request is understood, but it has been refused. An accompanying error message will explain why. (2)HTTP status code: 503 Message:Service Unavailable: The Twitter servers are up, but overloaded with requests. Try again later. The search and trend methods use this to indicate when you are being rate limited. (3) HTTP status code: -1 Message:Read timed out These errors are becoming more and more frequent lately. /Amitab On Sep 1, 5:41 pm, Dewald Pretorius dpr...@gmail.com wrote: Twitter team, can you please do something about the performance and rate limiting of the Search API. It is becoming completely unworkable. I have jumped through all the hoops, with unique User Agents, sleeping my scripts in-between API calls, and yet the rate limiting is just becoming more severe, and the performance is just becoming slower and slower. Please help. A lot of us are using Search to provide services, and I am sure it is not only my service that is hurting very much under the present circumstances. Dewald
[twitter-dev] Re: Read Status in API
On Aug 7, 2:56 am, Abraham Williams 4bra...@gmail.com wrote: I've heard Al3x mention adding flags so that application A tells twitter the user read their friends timeline up to stats xyz so when they start using application B it can jump over already read statuses. I have no idea the status of this feature or if it is still being considered. Yes, I would imagine adding a flag that when the authenticated user pulls from the API it would flag it as consumed.
[twitter-dev] Re: Is twitter a fad or worth development efforts?
There are some faulty premises in operation here. While these don't affect the substance of the answer to the OP's question, you do tend to follow them beyond to some unnecessary conclusions. On Thu, 3 Sep 2009 15:21:38 -1000 Kevin Mesiab ke...@mesiablabs.com wrote: You're asking the wrong folks. Most of the developers here do not have any real capital investment in their projects to speak of. Fewer still have a profit model. I don't have a profit model, but I do have a revenue model. It's a non-profit model built around free will donations, a value added service and a niche community. I run a self-supporting hobby server that is at the low end of its scalability. In other words, I can add additional services and 10 times as many users on the current hardware. A profit model is not necessary. A revenue model is. Is Twitter a Fad? The easy answer, yes. The long answer? Yes, but it needn't be... Unless Twitter makes a very real move to legitimize itself as a stable and growing (relevant) platform for end users, you will be better off focusing your capital on social media projects with more long term sustainability. Or diversify. Don't develop for just one Social Media Site. My strategy is to pick low hanging fruit like Twitter and MeetUps, but concentrate on OpenSocial for long term. Be aware, very few actual businesses have invested real dollars and labor into integration w/ Twitter (sales force, dell, whoot, et al) as opposed to the thousands who have adopted Facebook's API. And that's a concern. I think Twitter has hinted at a revenue model in the past couple weeks. Tightening security and making the Tweet stream accessible on a metered basis while providing the means for businesses to extract meaningful data is potentially viable. I think that there probably needs to be some additional progress made in natural language processing and AI agents for much of that value to be realized, but the value is there and at least partially monetizable. The reason is not a matter of playing favorites, it's a matter of mitigating risk. Presently, Twitter is a fad. It's popularity and its current growth pattern is a result of novelty and a media bubble. Microblogging is here to stay. The question is whether it is enough or whether users will want Statuses plus, for some value of plus that means plus polls, plus features, plus complications. There is a niche, currently close to 45 million users large, for just microblogging. Doing that and doing it well is one path to success. Speaking as someone building a Social Networking site for an existing game application, I don't care about Facebook statuses or similar features on other sites. I want to push and pull statuses with Twitter first because that's where the users who care about that feature live. I'll add the ability to work with other similar feeds later. However, Twitter has a very real chance to galvanize that momentum into a serious business (one that includes us third party developers), but it must move swiftly. Facebook is posturing to take over Twitter's market space. Not because it wants to obliterate Twitter as a competitor, but because they know what we know. The 'correct' social network exists somewhere between FB and Twitter. The quotes are good, but not good enough. There won't ever be a correct social network. 'Correct' is different things for different people at different times. It's only network effect that makes it worthwhile to accept a sub-optimal feature set for individual needs. FB has plus. That's a good place for them. They can't plus simplicity, however, and that's what Twitter has going for it. Both companies _should_ be racing towards that space. Whoever dominates it (and thusly deserves our investment) will be the one who a.) gets there first and b.) properly courts the developer community to enrich it. I'm originally from Maine. There's an expression there that says, You can't get there from here. The 're' in there and here as well as the word you are pronounced -uh, that's a voiced glottal aspirate followed by a schwa. Race is the wrong word. Facebook can't get there. It's too hard to get simpler. Twitter needs to set its own course into that space and take just as much of that space as needed to serve its core functionality. If it gets away from core function then the revenue model issue becomes pathological. There are only two ways to convince real companies to invest real capital: 1.) Prove the users are there 2.) Guarantee a market The users are here, but they may not stay if they are treated like a market. Marketing with social media is entirely different than using broadcast media. It's viable and monetizable, but it is not easy to scale. The challenge will be to see if Twitter can become a financial success without become a soulless waste of electrons like MySpace. Apple has shown us this model at scale. Models from hardware vendors may not apply. The only
[twitter-dev] Re: Search API Rate Limiting and Performance
The Search team is working on indexing latency and throughput, along with a many other things. There have been big improvements recently and more are on the way. In the mean time, if you need closer to real-time results, consider the track parameter on the Streaming API. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Sep 4, 6:58 am, pxpilot pxpi...@gmail.com wrote: Search API will rock if it would only be reliable what we see looks to be some sort of a funky cache, a query (atom) can be missing some latest tweets and then after a while they show up, if you tweak the query you can see 'em. you ever seen this problem? also what did you do special with user agent? On Sep 2, 12:12 pm, Amitab hiamita...@gmail.com wrote: I have exchanged emails with Twitter on this and I believe they are working on it. We use search extensively atwww.Twaller.com. The errors in search that we are seing is as follows: (1) HTTP status code: 403 Message:The request is understood, but it has been refused. An accompanying error message will explain why. (2)HTTP status code: 503 Message:Service Unavailable: The Twitter servers are up, but overloaded with requests. Try again later. The search and trend methods use this to indicate when you are being rate limited. (3) HTTP status code: -1 Message:Read timed out These errors are becoming more and more frequent lately. /Amitab On Sep 1, 5:41 pm, Dewald Pretorius dpr...@gmail.com wrote: Twitter team, can you please do something about the performance and rate limiting of the Search API. It is becoming completely unworkable. I have jumped through all the hoops, with unique User Agents, sleeping my scripts in-between API calls, and yet the rate limiting is just becoming more severe, and the performance is just becoming slower and slower. Please help. A lot of us are using Search to provide services, and I am sure it is not only my service that is hurting very much under the present circumstances. Dewald
[twitter-dev] Re: Search API Rate Limiting and Performance
John, the original message of this thread is about rate limit being totally erratic, as several users have noticed. here is the detail of what I'm seeing: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/40c82b4dbc0536bd Here is another user reporting the problem : http://groups.google.com/group/twitter-development-talk/browse_thread/thread/51bd6667d3b0a0a6 Basically the X-RateLimit-Remaining header goes up and down and up again between adjacent requests (all authenticated requests). The result is that the limit can appear to be reached way before 150 requests were issued... Thanks On Sep 4, 6:30 pm, John Kalucki jkalu...@gmail.com wrote: The Search team is working on indexing latency and throughput, along with a many other things. There have been big improvements recently and more are on the way. In the mean time, if you need closer to real-time results, consider the track parameter on the Streaming API. -John Kaluckihttp://twitter.com/jkalucki Services, Twitter Inc. On Sep 4, 6:58 am, pxpilot pxpi...@gmail.com wrote: Search API will rock if it would only be reliable what we see looks to be some sort of a funky cache, a query (atom) can be missing some latest tweets and then after a while they show up, if you tweak the query you can see 'em. you ever seen this problem? also what did you do special with user agent? On Sep 2, 12:12 pm, Amitab hiamita...@gmail.com wrote: I have exchanged emails with Twitter on this and I believe they are working on it. We use search extensively atwww.Twaller.com. The errors in search that we are seing is as follows: (1) HTTP status code: 403 Message:The request is understood, but it has been refused. An accompanying error message will explain why. (2)HTTP status code: 503 Message:Service Unavailable: The Twitter servers are up, but overloaded with requests. Try again later. The search and trend methods use this to indicate when you are being rate limited. (3) HTTP status code: -1 Message:Read timed out These errors are becoming more and more frequent lately. /Amitab On Sep 1, 5:41 pm,Dewald Pretoriusdpr...@gmail.com wrote: Twitter team, can you please do something about the performance and rate limiting of the Search API. It is becoming completely unworkable. I have jumped through all the hoops, with unique User Agents, sleeping my scripts in-between API calls, and yet the rate limiting is just becoming more severe, and the performance is just becoming slower and slower. Please help. A lot of us are using Search to provide services, and I am sure it is not only my service that is hurting very much under the present circumstances. Dewald
[twitter-dev] Re: Search API Rate Limiting and Performance
Various APIs have their own rate limiting mechanisms. The www, search and streaming rate limits are all customized to their usage patterns and share little to no code and/or state. -John On Sep 4, 9:49 am, Reivax xavier.yo...@gmail.com wrote: John, the original message of this thread is about rate limit being totally erratic, as several users have noticed. here is the detail of what I'm seeing: http://groups.google.com/group/twitter-development-talk/browse_thread... Here is another user reporting the problem :http://groups.google.com/group/twitter-development-talk/browse_thread... Basically the X-RateLimit-Remaining header goes up and down and up again between adjacent requests (all authenticated requests). The result is that the limit can appear to be reached way before 150 requests were issued... Thanks On Sep 4, 6:30 pm, John Kalucki jkalu...@gmail.com wrote: The Search team is working on indexing latency and throughput, along with a many other things. There have been big improvements recently and more are on the way. In the mean time, if you need closer to real-time results, consider the track parameter on the Streaming API. -John Kaluckihttp://twitter.com/jkalucki Services, Twitter Inc. On Sep 4, 6:58 am, pxpilot pxpi...@gmail.com wrote: Search API will rock if it would only be reliable what we see looks to be some sort of a funky cache, a query (atom) can be missing some latest tweets and then after a while they show up, if you tweak the query you can see 'em. you ever seen this problem? also what did you do special with user agent? On Sep 2, 12:12 pm, Amitab hiamita...@gmail.com wrote: I have exchanged emails with Twitter on this and I believe they are working on it. We use search extensively atwww.Twaller.com. The errors in search that we are seing is as follows: (1) HTTP status code: 403 Message:The request is understood, but it has been refused. An accompanying error message will explain why. (2)HTTP status code: 503 Message:Service Unavailable: The Twitter servers are up, but overloaded with requests. Try again later. The search and trend methods use this to indicate when you are being rate limited. (3) HTTP status code: -1 Message:Read timed out These errors are becoming more and more frequent lately. /Amitab On Sep 1, 5:41 pm,Dewald Pretoriusdpr...@gmail.com wrote: Twitter team, can you please do something about the performance and rate limiting of the Search API. It is becoming completely unworkable. I have jumped through all the hoops, with unique User Agents, sleeping my scripts in-between API calls, and yet the rate limiting is just becoming more severe, and the performance is just becoming slower and slower. Please help. A lot of us are using Search to provide services, and I am sure it is not only my service that is hurting very much under the present circumstances. Dewald
[twitter-dev] Re: Search API Rate Limiting and Performance
Dewald, I'm not on the search team, but there are a lot of discussions over there this morning about search api rate limits and related issues. Search rate limiting issues (vs. www.twitter.com or api.twitter.com) probably boil down to one of three categories: 1) Search service interruptions - We're working on these, obviously. You may see odd behavior when search capacity is reduced due to some operational issue, and the system is running far too hot. 2) General API limit reductions - We're slightly less generous than we have been in the past due to persistent abuse of the search api and due to overall capacity issues. We can't always provide for all valid use cases, although that is certainly a high priority. 3) Bugs. There could be defects that prevent valid use of the API. Detailed data of limiting mishaps would be helpful here. Timestamps, queries and statistics around reasonable use that was denied may allow us to identify a previously unknown defect. The search team is quite interested in working on #3. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Sep 1, 5:41 pm, Dewald Pretorius dpr...@gmail.com wrote: Twitter team, can you please do something about the performance and rate limiting of the Search API. It is becoming completely unworkable. I have jumped through all the hoops, with unique User Agents, sleeping my scripts in-between API calls, and yet the rate limiting is just becoming more severe, and the performance is just becoming slower and slower. Please help. A lot of us are using Search to provide services, and I am sure it is not only my service that is hurting very much under the present circumstances. Dewald
[twitter-dev] Search API limits
How can I retrieve the maximum number of tweets in a search? Can rpp be set to more than 100? What if I do not send a rpp value, does twitter default to returning more than 100 per page? Owkaye
[twitter-dev] Change in API
Hi: A couple of months ago, I received an email from Twitter about some changes in the API. I was, at that time, up to my eyeballs with a time sensitive project and did not have time to follow up. Now, I notice that a very simple function that I created, allowing a user to fill in a text field from a web page and post a Tweet, no longer works. Is there something I missed? What do I need to do to make sure my old code (March '09) now works with the API changes. Any insight would be very helpful. Thanks Sean
[twitter-dev] Re: Change in API
It may be that posts were changed to gets. On Sep 4, 2009, at 2:21 PM, Sean Fawcett s...@fawcettassociates.com wrote: Hi: A couple of months ago, I received an email from Twitter about some changes in the API. I was, at that time, up to my eyeballs with a time sensitive project and did not have time to follow up. Now, I notice that a very simple function that I created, allowing a user to fill in a text field from a web page and post a Tweet, no longer works. Is there something I missed? What do I need to do to make sure my old code (March '09) now works with the API changes. Any insight would be very helpful. Thanks Sean
[twitter-dev] screen_name param for /statuses/mentions and/or xml format for search results?
Background... I'm attempting to build an app that can display a conversation graph of all the tweets to/from people in a small group ... the use case being a set of friends, or coworkers in an office all wanting a quick view of the various public tweets and public reply tweets posted by other people in the group -- along with the full context of those tweets: tweets they are in reply to, or replies to those tweets, even if they are from people not included in the group. Current Approach... The /statuses/user_status REST API makes it trivial to get public tweets *by* a set of known individuals and using the XML format i can immediately inspect the in_reply_to_status_id element to see if there is a parent status i should fetch using /statuses/show to fetch the previous tweets for context context on the conversation -- even those tweets were from outside users not in the group. The next step is to find public statuses posted *from* outside users in reply to tweets by users who *are*in my set. The to param of the / search API makes it fairly easy to find a super set of these messages, but there's just one catch... The Problem... The /search API only supports the atom and json formats; since it doesn't support the xml format option, the only way (i can see) to determine if an item returned by /search is an actual reply to a previous tweet (and not just a shout out) is to fetch each individual tweet using the /status/show API ... but that feels like a very hackish solution, requiring numerous REST fetches of tweets (one at a time using the /statuses/show) just to backfill one additional property. In an ideal world the /search API would support the xml format so in_reply_to_status_id was included in the response, and things that weren't a reply could be easily excluded. (even better: if there was an optional param on the /search API that would allow you to restrict the results to only tweets that were replies) Alternately: it would be really great if the /statuses/mentions API (which does support the xml format) didn't require authentication, and allowed clients to pass a screen_name param to fetch public tweets mentioning a specific user. The Question... Obviously, my comments above constitute a suggested change to the existing APIs, but does anyone see any solutions to the problem i describe that would be less kludgy then using the /statuses/show API to fetch *every* individual item returned by the /search API in order to get the in_reply_to_status_id ?
[twitter-dev] Re: screen_name param for /statuses/mentions and/or xml format for search results?
ATOM _is_ XML ... not sure what the problem is? ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera) On Fri, Sep 4, 2009 at 6:18 PM, Hosshoss...@gmail.com wrote: Background... I'm attempting to build an app that can display a conversation graph of all the tweets to/from people in a small group ... the use case being a set of friends, or coworkers in an office all wanting a quick view of the various public tweets and public reply tweets posted by other people in the group -- along with the full context of those tweets: tweets they are in reply to, or replies to those tweets, even if they are from people not included in the group. Current Approach... The /statuses/user_status REST API makes it trivial to get public tweets *by* a set of known individuals and using the XML format i can immediately inspect the in_reply_to_status_id element to see if there is a parent status i should fetch using /statuses/show to fetch the previous tweets for context context on the conversation -- even those tweets were from outside users not in the group. The next step is to find public statuses posted *from* outside users in reply to tweets by users who *are*in my set. The to param of the / search API makes it fairly easy to find a super set of these messages, but there's just one catch... The Problem... The /search API only supports the atom and json formats; since it doesn't support the xml format option, the only way (i can see) to determine if an item returned by /search is an actual reply to a previous tweet (and not just a shout out) is to fetch each individual tweet using the /status/show API ... but that feels like a very hackish solution, requiring numerous REST fetches of tweets (one at a time using the /statuses/show) just to backfill one additional property. In an ideal world the /search API would support the xml format so in_reply_to_status_id was included in the response, and things that weren't a reply could be easily excluded. (even better: if there was an optional param on the /search API that would allow you to restrict the results to only tweets that were replies) Alternately: it would be really great if the /statuses/mentions API (which does support the xml format) didn't require authentication, and allowed clients to pass a screen_name param to fetch public tweets mentioning a specific user. The Question... Obviously, my comments above constitute a suggested change to the existing APIs, but does anyone see any solutions to the problem i describe that would be less kludgy then using the /statuses/show API to fetch *every* individual item returned by the /search API in order to get the in_reply_to_status_id ?
[twitter-dev] Re: Is twitter a fad or worth development efforts?
First, Why you are here??? For me, i'm trying to develop with twitter api for fun and learning. Now i know more about php that a month ago. I'm doing this with the hope of doing a best site that twitter, giving more options to cuztomize to the user and new services (and the hope of winning some money). You're asking the wrong folks. Most of the developers here do not have any real capital investment in their projects to speak of. Fewer still have a profit model. - Kevin Mesiab Is twitter a fad or worth development efforts?
[twitter-dev] Re: Mobile oAuth
OAuth is great, in certain circumstances. In others, it's not so great. Circumstances for which it is great include: - consumer web sites; and - consumer client applications that have access to a reasonable browser on the client device in both cases with the qualification that the authorization pages of the service provider are in a language (e.g., English, Japanese, etc.) that is the same as that used by the consumer. In these circumstances, OAuth as defined by the specifications and implemented by twitter works very well. Circumstances for which it is not so great include: - consumer client applications that do not have access to a reasonable browser on the client device; and - consumer client applications and web sites that are in languages for which service authorization pages in those languages are not available. In these circumstances, OAuth as defined by the specifications and implemented by twitter does not work so well. Currently, in circumstances where OAuth does not work very well, twitter client applications and web-sites can resort to Basic Authentication. The drawbacks to this are obvious: - the user must give their twitter password to the client; - at some point twitter will no longer support Basic Authentication; and - the source of tweets created by these clients is API rather than the client's name. Pooh pooh the last drawback if you will, but to some it is important. Now, the fact of the matter is that some users are perfectly comfortable in giving their twitter passwords to client applications and web-sites, even where those clients support OAuth. I don't think these users should be penalized and forced to use OAuth if'n and when'n twitter drops support for Basic Authentication. And if'n and when'n twitter drops support for Basic Authentication, client applications and web-sites that now only support Basic Authentication will be forced to support OAuth. Myself, I don't think that's an unreasonable requirement, but others may differ. And I don't think these creators should have to forgo having their client's name as the source of tweets their clients create, now or ever, just because their users chose to trust them to use Basic Authentication. So I propose the following enhancement to twitter's OAuth implementation: Allow a userID and password to be included as optional parameters of an oauth/access_token request. If supplied and authentic, they would cause a valid access token to be returned without the user having visited the authorize URL and approved the access. Alternately, the userID and password could be optional on an oauth/request_token request, in which case, if supplied and authentic, the request would return a valid access token, rather than a request token, again without the user having visited the authorize URL and approved the access. The advantage to this alternative is it reduces by one the number of API calls needed. I believe either of these alternatives is a viable solution for the circumstances where the existing OAuth implementation does not work so great. Comments expected and welcome. Jim Renkel -Original Message- From: twitter-development-talk@googlegroups.com [mailto:twitter-development-t...@googlegroups.com] On Behalf Of twittme_mobi Sent: Friday, September 04, 2009 08:39 To: Twitter Development Talk Subject: [twitter-dev] Re: Mobile oAuth I am also interested in mobile oath solution. twitter guys should think of something before deprecating basic auth On Aug 20, 8:01 am, Cameron Kaiser spec...@floodgap.com wrote: I have a mobile based twitter client in the field and have implemented oAuth for this client. Some of the devices are either very low memory or have primitive browsers that dont support the rendering of the 'allow' / 'deny' access page (http://twitter.com/oauth/authorize). I have tried the obvioushttp://m.twitter.com/oauth/authorizebut this seems to serve the same standard webage. So Im looking for nat previous info or plans of a lightweight implementation of oAuth access page for twitter. I'm also particularly interested in such a page, especially one a text browser could access such as Lynx or w3m. -- personal:http://www.cameronkaiser.com/-- Cameron Kaiser * Floodgap Systems *www.floodgap.com* ckai...@floodgap.com -- Adore, v.: To venerate expectantly. -- Ambrose Bierce --
[twitter-dev] Followers/IDs Change/Error?
Hi All, Until today this: http://twitter.com/followers/ids.xml had always been working OK for me. One query to it returned all my followers (around 10,000.) Today it seems to have changed to showing me just 5,000 on the first page, which is OK except for the fact that when I try to get Page 2 it shows me 0 results now. Has anyone else noticed changes to this call or figured out how to make it work? Thanks in advance.
[twitter-dev] Re: Is twitter a fad or worth development efforts?
I just accidentally banned someone posting to this thread from the group. If you find it was you please email me offlist and I will get you back on. My apologizes, Abraham -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Getting screen_name from id without gazillion API calls?
Hi, When i request friends (or followers) from the Twitter API i want to get the screen_name's based on the id's. I use users/show for this, inputting the id and getting back de screen_name. This costs ALOT of API calls and i run into the API rate limit fast, especially with many friends. Is there a better way of getting screen_names for friends / followers? ( Better, meaning in fewer API calls.) Thank you.
[twitter-dev] Re: Search API limits
The rpp defaults to 15 or something if you don't specify it. Sounds like you need to mess around and play with things a bit more. The key to max search results isn't in paging or rpp, but in max_id. Be careful what you ask for. Retrieval of everything available can take a long time (hours) dave fisher http://webecologyproject.org On Sep 4, 10:16 am, owkaye owk...@gmail.com wrote: How can I retrieve the maximum number of tweets in a search? Can rpp be set to more than 100? What if I do not send a rpp value, does twitter default to returning more than 100 per page? Owkaye
[twitter-dev] OAuth changes?
Hi, I was curious if anyone has seen any calls to statuses/update stop working using OAuth/PHP Pecl. I recently started getting errors of Incorrect Signature with some code that had been working perfectly fine for the past month. I'd be happy to elaborate more, but just shooting out this general inquiry in case if this is the wrong forum for it. Thanks Bobby
[twitter-dev] Re: Followers/IDs Change/Error?
Just came here to ask the same question. Looks a change to me. On Sep 5, 1:38 am, Zensae ch...@sandman.com wrote: Hi All, Until today this: http://twitter.com/followers/ids.xmlhad always been working OK for me. One query to it returned all my followers (around 10,000.) Today it seems to have changed to showing me just 5,000 on the first page, which is OK except for the fact that when I try to get Page 2 it shows me 0 results now. Has anyone else noticed changes to this call or figured out how to make it work? Thanks in advance.
[twitter-dev] Re: Followers count
Until today you could use: http://twitter.com/followers/ids.xml and get the total - this was way more accurate than getting it from user/show. They appear to ahve just lowerd this total to 5000 so that will no longer work (unless that's a bug). On Sep 3, 7:24 am, Waldron Faulkner waldronfaulk...@gmail.com wrote: Same oddness w. friends count as well? I'd guess so. My problem is that if I try to get followers using paging, I get different numbers (and different followers) than if I pull the entire list w/o paging. Also, followers disappear and reappear from one hour to the next. On Sep 2, 5:44 pm, Jason Tan jasonw...@gmail.com wrote: Hello, I have spent a good portion of today reading through closed, merged, and open issues onhttp://code.google.com/p/twitter-api/issues/list I am trying to figure out the best way to get an accurate followers count. Initially, I was using /users/show which returns the full user object, including the followers_count item. However, I have noticed that this number only updates when the user posts a tweet. If the user has no new tweets, the follower count is not updated. Data I was pulling in was many days old. I understand the need to cache data, but being unable to pull up an approximate count of followers from the past several days is a problem. I have seen this issue posted many times, but it is always merged into issue 474, which appears to only deal with the following flag, and not the followers_count. There was one issue (which I can't find anymore) where there was acknowledgment that the users/show data was cached until a new post was made but no mention of any fix or solution. My next approach was to use the statuses/user_timeline. I wasn't sure if the user object for each status would have the current value or the value at the time of the status update. When I grabbed the xml formatted response, I got (starting from the most recent status and going back): 1686, 1653, 1685, 1685, 1685, 1685, 1685... Through the rest of the statuses, it stayed the same. Interestingly, 1686 is the current value listed on the website. 1653 was the value I got from /users/show. And I'm quite certain that the followers count did not stay constant at 1685. Moreover, when I grabbed the json version of statuses/user_timeline, I got entirely different results: 1653, 1653, 1683, 1675, 1652, 1661, 1644... This seems to reflect the current number of followers at the time of the status update, unlike the XML feed. Anyways, to get back to my original question. How do I get an accurate followers count for a user? Also, why are there still XML/ JSON discrepancies (I came across a few reported issues that said they had been resolved). Any help or suggestions would be very much appreciated! Thanks, Jason P.S. The account I was using for the above examples was DailyPHP- Hide quoted text - - Show quoted text -
[twitter-dev] Followers Friends IDs Are Seriously MESSED Up!
Not only do the social graph calls now suddenly, without any prior warning of announcement, return only 5,000 ids, it is messed up even when you do the paging as per the API documentation. Case in point. @socialoomph has 16,598 followers. If you page through the follower ids with page, you get only 12,017 entries. This is highly frustrating, and it has now completely screwed up my follower processing. It does not help that Twitter has rolled out something into production without any kind of testing, right before a weekend. Dewald
[twitter-dev] Re: Getting screen_name from id without gazillion API calls?
statuts/friends and status/followers i guess On Sep 5, 3:01 am, dizid glasw...@gmail.com wrote: Hi, When i request friends (or followers) from the Twitter API i want to get the screen_name's based on the id's. I use users/show for this, inputting the id and getting back de screen_name. This costs ALOT of API calls and i run into the API rate limit fast, especially with many friends. Is there a better way of getting screen_names for friends / followers? ( Better, meaning in fewer API calls.) Thank you.
[twitter-dev] Re: Search API limits
The key to max search results isn't in paging or rpp, but in max_id. Hi David, I do not understand how max_id can help me. If I want to get the 10,000 most recent tweets that match the phrase michael jackson changing the max_id value doesn't seem like it's going to help at all. In fact, it doesn't even make sense to use it when trying to retrieve the most recent tweets, does it? Be careful what you ask for. Retrieval of everything available can take a long time (hours). My understanding is that every request is limited to 100 tweets max, and this forces multiple requests when trying to retrieve more than 100 tweets. Am I wrong about this? Owkaye
[twitter-dev] Re: Followers Friends IDs Are Seriously MESSED Up!
For @dewaldp I get, via the API social graph methods with paging: Friends: 764 , Followers: 3,977. While on my web profile the numbers are: Friends: 747 , Followers: 3,911. On Sep 4, 11:56 pm, Dewald Pretorius dpr...@gmail.com wrote: Not only do the social graph calls now suddenly, without any prior warning of announcement, return only 5,000 ids, it is messed up even when you do the paging as per the API documentation. Case in point. @socialoomph has 16,598 followers. If you page through the follower ids with page, you get only 12,017 entries. This is highly frustrating, and it has now completely screwed up my follower processing. It does not help that Twitter has rolled out something into production without any kind of testing, right before a weekend. Dewald
[twitter-dev] Re: Followers Friends IDs Are Seriously MESSED Up!
We're aware of the problem with the following API not returning more than 5,000 followers. Apparently this call has recently been unreliable was often timing out and returning 503s. A change to fix the 503s limited the results to 5000 followers prematurely. We're going to get this back to the 5000 followers, but with 503's state as soon as we can, but we're fighting several fires at once tonight. More in a few minutes. -John On Sep 4, 7:56 pm, Dewald Pretorius dpr...@gmail.com wrote: Not only do the social graph calls now suddenly, without any prior warning of announcement, return only 5,000 ids, it is messed up even when you do the paging as per the API documentation. Case in point. @socialoomph has 16,598 followers. If you page through the follower ids with page, you get only 12,017 entries. This is highly frustrating, and it has now completely screwed up my follower processing. It does not help that Twitter has rolled out something into production without any kind of testing, right before a weekend. Dewald
[twitter-dev] Re: Followers/IDs Change/Error?
Working to fix this. On Sep 4, 6:45 pm, freefall tehgame...@googlemail.com wrote: Just came here to ask the same question. Looks a change to me. On Sep 5, 1:38 am, Zensae ch...@sandman.com wrote: Hi All, Until today this: http://twitter.com/followers/ids.xmlhadalways been working OK for me. One query to it returned all my followers (around 10,000.) Today it seems to have changed to showing me just 5,000 on the first page, which is OK except for the fact that when I try to get Page 2 it shows me 0 results now. Has anyone else noticed changes to this call or figured out how to make it work? Thanks in advance.
[twitter-dev] Re: Followers Friends IDs Are Seriously MESSED Up!
There have been times when a friend or follower id has been reported multiple times. Did you check to see if any of the friend or follower ids that you get back were duplicates? - h On Fri, Sep 4, 2009 at 20:17, Dewald Pretorius dpr...@gmail.com wrote: For @dewaldp I get, via the API social graph methods with paging: Friends: 764 , Followers: 3,977. While on my web profile the numbers are: Friends: 747 , Followers: 3,911. On Sep 4, 11:56 pm, Dewald Pretorius dpr...@gmail.com wrote: Not only do the social graph calls now suddenly, without any prior warning of announcement, return only 5,000 ids, it is messed up even when you do the paging as per the API documentation. Case in point. @socialoomph has 16,598 followers. If you page through the follower ids with page, you get only 12,017 entries. This is highly frustrating, and it has now completely screwed up my follower processing. It does not help that Twitter has rolled out something into production without any kind of testing, right before a weekend. Dewald
[twitter-dev] Re: Followers Friends IDs Are Seriously MESSED Up!
Several months ago there were multiple subtle problems with consistency in following lists. We've since rolled to a new system that have numerous constraints in place to prevent duplicates and provide much stronger consistency guarantees. There is, however, a known issue around pagination. You may see some jitter as you page through a long list -- off by one errors. We're working to fix this to make pagination completely solid. If you are seeing duplicates that aren't on a page boundary, please let us know. -John On Sep 4, 8:42 pm, Howard Siegel hsie...@gmail.com wrote: There have been times when a friend or follower id has been reported multiple times. Did you check to see if any of the friend or follower ids that you get back were duplicates? - h On Fri, Sep 4, 2009 at 20:17, Dewald Pretorius dpr...@gmail.com wrote: For @dewaldp I get, via the API social graph methods with paging: Friends: 764 , Followers: 3,977. While on my web profile the numbers are: Friends: 747 , Followers: 3,911. On Sep 4, 11:56 pm, Dewald Pretorius dpr...@gmail.com wrote: Not only do the social graph calls now suddenly, without any prior warning of announcement, return only 5,000 ids, it is messed up even when you do the paging as per the API documentation. Case in point. @socialoomph has 16,598 followers. If you page through the follower ids with page, you get only 12,017 entries. This is highly frustrating, and it has now completely screwed up my follower processing. It does not help that Twitter has rolled out something into production without any kind of testing, right before a weekend. Dewald
[twitter-dev] Re: Followers count
The 5k limit is a bug. Working to fix. On Sep 4, 6:51 pm, freefall tehgame...@googlemail.com wrote: Until today you could use:http://twitter.com/followers/ids.xml and get the total - this was way more accurate than getting it from user/show. They appear to ahve just lowerd this total to 5000 so that will no longer work (unless that's a bug). On Sep 3, 7:24 am, Waldron Faulkner waldronfaulk...@gmail.com wrote: Same oddness w. friends count as well? I'd guess so. My problem is that if I try to get followers using paging, I get different numbers (and different followers) than if I pull the entire list w/o paging. Also, followers disappear and reappear from one hour to the next. On Sep 2, 5:44 pm, Jason Tan jasonw...@gmail.com wrote: Hello, I have spent a good portion of today reading through closed, merged, and open issues onhttp://code.google.com/p/twitter-api/issues/list I am trying to figure out the best way to get an accurate followers count. Initially, I was using /users/show which returns the full user object, including the followers_count item. However, I have noticed that this number only updates when the user posts a tweet. If the user has no new tweets, the follower count is not updated. Data I was pulling in was many days old. I understand the need to cache data, but being unable to pull up an approximate count of followers from the past several days is a problem. I have seen this issue posted many times, but it is always merged into issue 474, which appears to only deal with the following flag, and not the followers_count. There was one issue (which I can't find anymore) where there was acknowledgment that the users/show data was cached until a new post was made but no mention of any fix or solution. My next approach was to use the statuses/user_timeline. I wasn't sure if the user object for each status would have the current value or the value at the time of the status update. When I grabbed the xml formatted response, I got (starting from the most recent status and going back): 1686, 1653, 1685, 1685, 1685, 1685, 1685... Through the rest of the statuses, it stayed the same. Interestingly, 1686 is the current value listed on the website. 1653 was the value I got from /users/show. And I'm quite certain that the followers count did not stay constant at 1685. Moreover, when I grabbed the json version of statuses/user_timeline, I got entirely different results: 1653, 1653, 1683, 1675, 1652, 1661, 1644... This seems to reflect the current number of followers at the time of the status update, unlike the XML feed. Anyways, to get back to my original question. How do I get an accurate followers count for a user? Also, why are there still XML/ JSON discrepancies (I came across a few reported issues that said they had been resolved). Any help or suggestions would be very much appreciated! Thanks, Jason P.S. The account I was using for the above examples was DailyPHP- Hide quoted text - - Show quoted text -
[twitter-dev] Re: Followers Friends IDs Are Seriously MESSED Up!
Can Twitter remove the following per hour limit for a little bit after they fix this (at least for whitelisted IPs and/or OAuth)? This has caused us, and I'm sure many other apps to pre-emptively unfollow people that they were not supposed to. This is a BIG problem! I completely agree with Dewald's frustrations. If the limits can be removed after this for at least a short bit so we can make it back up to those users affected it would be sincerely appreciated. Jesse On Fri, Sep 4, 2009 at 8:56 PM, Dewald Pretorius dpr...@gmail.com wrote: Not only do the social graph calls now suddenly, without any prior warning of announcement, return only 5,000 ids, it is messed up even when you do the paging as per the API documentation. Case in point. @socialoomph has 16,598 followers. If you page through the follower ids with page, you get only 12,017 entries. This is highly frustrating, and it has now completely screwed up my follower processing. It does not help that Twitter has rolled out something into production without any kind of testing, right before a weekend. Dewald
[twitter-dev] unexpected 401 unauthorized from streaming api
I'm running into a problem reconnecting to the streaming api. On reconnect I get 401 unauthorized. I run for example curl 'http://stream.twitter.com/1/statuses/filter.json? follow=123,12085,11' -ugsnap_api:... -vv and it works and I get the output * About to connect() to stream.twitter.com port 80 (#0) * Trying 128.121.146.231... connected * Connected to stream.twitter.com (128.121.146.231) port 80 (#0) * Server auth using Basic with user 'gsnap_api' GET /1/statuses/filter.json?follow=123,12085,11 HTTP/1.1 Authorization: Basic ... User-Agent: curl/7.18.2 (x86_64-redhat-linux-gnu) libcurl/7.18.2 NSS/3.12.1.1 zlib/1.2.3 libidn/0.6.14 libssh2/0.18 Host: stream.twitter.com Accept: */* I wait 10 sec, hit ^c, wait another 10 sec, and run the command again but this time I get 401 unauthorized * About to connect() to stream.twitter.com port 80 (#0) * Trying 128.121.146.231... connected * Connected to stream.twitter.com (128.121.146.231) port 80 (#0) * Server auth using Basic with user 'gsnap_api' GET /1/statuses/filter.json?follow=123,12085,11 HTTP/1.1 Authorization: Basic ... User-Agent: curl/7.18.2 (x86_64-redhat-linux-gnu) libcurl/7.18.2 NSS/3.12.1.1 zlib/1.2.3 libidn/0.6.14 libssh2/0.18 Host: stream.twitter.com Accept: */* HTTP/1.1 401 Unauthorized * Authentication problem. Ignoring this. WWW-Authenticate: Basic realm=Firehose Cache-Control: must-revalidate,no-cache,no-store Content-Type: text/html; charset=iso-8859-1 Content-Length: 1296 Server: Jetty(6.1.17) html head meta http-equiv=Content-Type content=text/html; charset=ISO-8859-1/ titleError 401 UNAUTHORIZED/title /head body h2HTTP ERROR: 401/h2 pProblem accessing /1/statuses/filter.json. Reason: preUNAUTHORIZED/pre/p hr /ismallPowered by Jetty:///small/i After a few minutes during which I don't run the command, I'm able to repeat the above scenario. Does anyone know what I'm doing wrong or what the problem is? I used to be able to run such scenarios fine, but now they fail (with both the old and new streaming api). thanks for any help, John
