[twitter-dev] Re: Follower analysis without whitelisting breaks limits?
On 21 Feb., 06:50, Orian Marx (@orian) or...@orianmarx.com wrote: I don't know what the current state of this is but it looks like Site Streams will support unfollow events for this purpose:http://groups.google.com/group/twitter-development-talk/browse_thread... From the mentioned thread: I'm only seeing unfollow events where the tracked user is doing the unfollowing. So if only those unfollowings are reported by the stream, that the tracked user is doing himself, I am not able to watch the followers, that he has lost (other followers unfollow the tracked user). That's not sufficient for follower tracking how we do it. Unfortunately no statement from the twitter guys... Cheers. Jo Seibert On Feb 18, 5:11 pm, Jo jseib...@seibert-media.net wrote: It seems as if no one at twitter as an answer or a solution on this. That's bad... Or are they still thinking about it? Cheers. Jo Seibert On 15 Feb., 11:03, Dewald Pretorius dpr...@gmail.com wrote: Thanks Tim. So the point is, we still need to rely on the follower ids list API method if we want to maintain an up to date picture of an account's followers. For larger accounts this becomes impractical with a limit of 350 calls per hour. On Feb 15, 4:13 am, Tim Haines tmhai...@gmail.com wrote: It sends you an event when our subject user follows someone else, unfollows someone else, or when they are followed by someone else. It does not send an event when they are unfollowed by someone else. Tim. On Tue, Feb 15, 2011 at 3:08 AM, Dewald Pretorius dpr...@gmail.com wrote: If I remember correctly, Site Streams sends you a transaction only when the user follows another user (adding to Following). It does not send you a transaction when someone else follows that user (adding to Followers). I don't know if this work the same in User Streams. Clarification by Twitter will be appreciated. On Feb 14, 12:38 pm, David Giamanco dgiama...@gmail.com wrote: I believe the new way to do this is to initially call the REST API to get all of the ids for the first time you process this user. Then you setup a User Stream on the user and process any requests that come in through there. For your uses, if you only show users the differences in follower counts then you don't need the initial call to the REST API to collect all ids. All you need is a count of the ids and then to initiate a User Stream. The User Stream will give you the differences in real time and you can store just the differences, instead of the entire set of ids. David Giamanco -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Getting 500:Something is broken
Hi there, I discovered the same errors and was told, that these errors are a symptom of overload of the API. In this case you should handle them exactly like 502 or 503 errors. See also the discussion thread: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/b32dc292eb0c68ca And yes: I would appreciate too if the API gives the right kind of errors in these situations. Greetings. Jo Seibert On 29 Sep., 01:32, nischalshetty nischalshett...@gmail.com wrote: For many API calls (retrieving friend Ids, follower Ids) I'm getting 500:Something is broken. Please post to the group so the Twitter team can investigate. as error message. Is the twitter API having problems? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: 500: Something is technically wrong while calling lists/memberships
Hi Matt, any updates on this thread? I still see this error from time to time. Greetings. Jo Seibert On 1 Sep., 22:57, Joachim Seibert jseib...@seibert-media.net wrote: Hi Matt, the problem seems to be getting worse. No I see this error quite often and with other calls than lists/memberships too. One example with statuses/retweets: Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Request: Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - GEThttp://api.twitter.com/1/statuses/retweets/18334417346.json?count=100 Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - OAuth base string: GEThttp%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses%2Fretweets%2F18334417346.js onco unt%3D100%26oauth_consumer_key%3DWlcg5zbNH60gCZAHCswGIw%26oauth_nonce%3D314 8833036%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1283373740 %26oaut h_token%3D14150654-pkmqfsHKGaD9Uj6Ahus2Zv8euQ1zyKrgrU1v7kwUq%26oauth_versio n%3D1.0 Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - OAuth signature: rZds70A8TKCKmCSfdRPFpEGURsc= Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Authorization: *** * *** *** *** *** Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - X-Twitter-Client-URL:http://twitter4j.org/en/twitter4j-2.1.3.xml Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - X-Twitter-Client: Twitter4J Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Accept-Encoding: gzip Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - X-Twitter-Client-Version: 2.1.3 Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Connection: close Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Response: Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - HTTP/1.1 500 Internal Server ErrorSep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - X-Transaction: 1283373740-97223-912Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - X-RateLimit-Limit: 2Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Content-Length: 1729Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - X-RateLimit-Remaining: 19967 Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Expires: Tue, 31 Mar 1981 05:00:00 GMT Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Last-Modified: Wed, 01 Sep 2010 20:42:20 GMTSep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - X-RateLimit-Reset: 1283377034Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - X-RateLimit-Class: api_whitelistedSep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - X-Revision: DEVSep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCA8zCc8qAToHaWQiJTljNTJlM2Q0ZjQ3MTY3% 250AOGE0ODM2NGMzMjQwYjJiN2M0IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy%250AOjpGbG FzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--466cc297d1c8f9370081fbe2ffba832a8f03b68 2; domain=.twitter.com; path=/Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Set-Cookie: lang=en; path=/Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Set-Cookie: guest_id=128337374080975974; path=/; expires=Fri, 01 Oct 2010 20:42:20 GMTSep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Set-Cookie: k=75.101.167.21.1283373740806509; path=/; expires=Wed, 08-Sep-10 20:42:20 GMT; domain=.twitter.comSep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Connection: closeSep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Server: hiSep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Pragma: no-cacheSep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Status: 500 Internal Server ErrorSep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Date: Wed, 01 Sep 2010 20:42:20 GMTSep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Vary: Accept-EncodingSep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Content-Encoding: gzipSep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - Content-Type: text/html; charset=utf-8 Sep 1 20:42:20 consumer1 [ActiveMQ Session Task] DEBUG - !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;#012html xmlns=http://www.w3.org/1999/xhtml; lang=en xml:lang=en#012 head#012 meta http-equiv=Content-Type content=text/html; charset=utf-8 /#012 meta http-equiv=Content-Language content=en-us /#012
