[twitter-dev] Re: OAuth rate limit question
Hey Raffi So, would Twitter prefer that clients use the headers instead of relying on the (now misleading) account/rate_limit_status method to verify the rate limit? http://apiwiki.twitter.com/Twitter-REST-API-Method:-account%C2%A0rate_limit_status As, even with Oauth-signed requests, this method is still returning 150 per hour. Thanks! Nik On Mar 3, 7:26 am, Raffi Krikorian ra...@twitter.com wrote: are you connecting via oauth to api.twitter.com? if so, then please take a look at the rate limit headers and let me know what you see? On Tue, Mar 2, 2010 at 10:48 PM, Ben Novakovic bennovako...@gmail.comwrote: Hi, I have been reading about twitter api limits lately as a lot of my users are exhausting their 150reqs/h on a fairly regular basis. I came across the following post and noticed that if users login with OAuth, they are given 350 reqs/hr. http://groups.google.com/group/twitter-development-talk/msg/b09f2a332... This was fair enough as you guys are trying to make twitter more secure (good work!); so we set about implementing OAuth on our client. We completed the implementation today, but fail to see the 350 reqs/ hr. We are still being limited by the 150 reqs/hr. I was just wondering whether there was something special we needed to do to get our req limits up to 350 for those users who login to our client with OAuth. Just to give you some background info, the client is a mobile web based client and all requests to twitter are made on our server on behalf of our users. If they are logged in with OAuth, the appropriate OAuth details are also handed through as part of the request. We know they are using OAuth as our 'updated via xxx' changes with using OAuth. Any help would be greatly appreciated! Thanks! Ben -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: OAuth Rate Limit Increase - Not seeing it
Hi there We also thought we were not receiving the correct rate limit - however the account/rate_limit_status method doesn't actually correctly reflect these new request limits. Instead, you'll need to (at least, until - or if - Twitter change this method to respond appropriately to OAuth calls) use the X-RateLimit-Limit HTTP header to detect the current rate limit. The good news is that the HTTP header *does* reflect the new 350 RPH limit :-) I've also just posted about this here: http://groups.google.com/group/twitter-development-talk/t/b9e2aa61f2af0911 So it might be worth keeping an eye out for @raffi's reply. Cheers -N On Mar 2, 6:47 pm, eclipsed4utoo ryanalford...@gmail.com wrote: I thought that the OAuth Rate Limit went up to 350? I am still getting 150. Here is the returned XML from my request tohttp://api.twitter.com/1/account/rate_limit_status.xml ?xml version=1.0 encoding=UTF-8? hash reset-time type=datetime2010-03-02T19:42:28+00:00/reset-time hourly-limit type=integer150/hourly-limit reset-time-in-seconds type=integer1267558948/reset-time-in- seconds remaining-hits type=integer150/remaining-hits /hash I am using OAuth and using the new version of the REST API. What else do I need to do?
Re: [twitter-dev] Data rates from yesterday's meeting?
Related question: is there any technical difference between http://stream.twitter.com/spritzer.json and http://stream.twitter.com/1/statuses/sample.json? spritzer.json is what one gets if you click on the link to sample.json in the firehose page on the wiki. -- -ed costello @epc / +13474080372
Re: [twitter-dev] Re: OAuth rate limit question
Well - it seems to me that rate limit status may have an issue with it. We will have to take a look. On Mar 3, 2010, at 2:56 AM, Nik Fletcher nik.fletc...@gmail.com wrote: Hey Raffi So, would Twitter prefer that clients use the headers instead of relying on the (now misleading) account/rate_limit_status method to verify the rate limit? http://apiwiki.twitter.com/Twitter-REST-API-Method:-account%C2%A0rate_limit_status As, even with Oauth-signed requests, this method is still returning 150 per hour. Thanks! Nik On Mar 3, 7:26 am, Raffi Krikorian ra...@twitter.com wrote: are you connecting via oauth to api.twitter.com? if so, then please take a look at the rate limit headers and let me know what you see? On Tue, Mar 2, 2010 at 10:48 PM, Ben Novakovic bennovako...@gmail.comwrote: Hi, I have been reading about twitter api limits lately as a lot of my users are exhausting their 150reqs/h on a fairly regular basis. I came across the following post and noticed that if users login with OAuth, they are given 350 reqs/hr. http://groups.google.com/group/twitter-development-talk/msg/b09f2a332 ... This was fair enough as you guys are trying to make twitter more secure (good work!); so we set about implementing OAuth on our client. We completed the implementation today, but fail to see the 350 reqs/ hr. We are still being limited by the 150 reqs/hr. I was just wondering whether there was something special we needed to do to get our req limits up to 350 for those users who login to our client with OAuth. Just to give you some background info, the client is a mobile web based client and all requests to twitter are made on our server on behalf of our users. If they are logged in with OAuth, the appropriate OAuth details are also handed through as part of the request. We know they are using OAuth as our 'updated via xxx' changes with using OAuth. Any help would be greatly appreciated! Thanks! Ben -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] Re: OAuth rate limit question
Just to add, I also get the 150 rate limit when using the account/rate_limit_status method. I am using OAuth and api.twitter.com. Ryan On Wed, Mar 3, 2010 at 8:57 AM, Raffi Krikorian ra...@twitter.com wrote: Well - it seems to me that rate limit status may have an issue with it. We will have to take a look. On Mar 3, 2010, at 2:56 AM, Nik Fletcher nik.fletc...@gmail.com wrote: Hey Raffi So, would Twitter prefer that clients use the headers instead of relying on the (now misleading) account/rate_limit_status method to verify the rate limit? http://apiwiki.twitter.com/Twitter-REST-API-Method:-account%C2%A0rate_limit_status As, even with Oauth-signed requests, this method is still returning 150 per hour. Thanks! Nik On Mar 3, 7:26 am, Raffi Krikorian ra...@twitter.com wrote: are you connecting via oauth to api.twitter.com? if so, then please take a look at the rate limit headers and let me know what you see? On Tue, Mar 2, 2010 at 10:48 PM, Ben Novakovic bennovako...@gmail.com wrote: Hi, I have been reading about twitter api limits lately as a lot of my users are exhausting their 150reqs/h on a fairly regular basis. I came across the following post and noticed that if users login with OAuth, they are given 350 reqs/hr. http://groups.google.com/group/twitter-development-talk/msg/b09f2a332. .. This was fair enough as you guys are trying to make twitter more secure (good work!); so we set about implementing OAuth on our client. We completed the implementation today, but fail to see the 350 reqs/ hr. We are still being limited by the 150 reqs/hr. I was just wondering whether there was something special we needed to do to get our req limits up to 350 for those users who login to our client with OAuth. Just to give you some background info, the client is a mobile web based client and all requests to twitter are made on our server on behalf of our users. If they are logged in with OAuth, the appropriate OAuth details are also handed through as part of the request. We know they are using OAuth as our 'updated via xxx' changes with using OAuth. Any help would be greatly appreciated! Thanks! Ben -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: xAuth
Isn't that using a GET request versus the docs saying POST? And I thought parameters were supposed to be normalized except for signature which gets attached at the end? On Mar 2, 3:40 pm, Marc Mims marc.m...@gmail.com wrote: * Berto mstbe...@gmail.com [100302 13:28]: At first I thought this might be because HttpURLConnection wasn't handling SSL, but then I switched over to HttpPost (this code is in Java) which I know will handle SSL and I'm still getting a 401. I'm doing everything the same as with oauth, except passing the request token (I'm not even getting a request token any more) and I'm passing the x_auth_* parameters as regular parameters in the POST body. The three x_auth_* parameters are my only parameters and the normal OAuth header is in the Authorization field. I'm POSTing to the new access URL as specified in the xAuth docs with no success . Thoughts anyone? I feel like such a noob asking for so much help with oAuth/xAuth :\. I have successfully implemented xAuth in the Perl Net::Twitter library. Here's what a Net::Twitter generated xAuth request looks like: GEThttps://twitter.com/oauth/access_token?oauth_consumer_key=CONSUMER_KE... User-Agent: Net::Twitter/3.11008 (Perl) X-Twitter-Client: Perl Net::Twitter X-Twitter-Client-URL:http://search.cpan.org/dist/Net-Twitter/ X-Twitter-Client-Version: 3.11008 For this example, I used: consumer_key = 'CONSUMER_KEY' consumer_secret = 'CONSUMER_SECRET' x_auth_username = 'fred' x_auth_secret = 'secret' Hope this helps. @semifor
[twitter-dev] Re: OAuth Rate Limit Increase - Not seeing it
I reported this bug yesterday. Instead of making that extra call, why not look at the response headers which come back with each API ACCESS - you'll get the info you need: X-Ratelimit-Limit = 150; X-Ratelimit-Remaining = 133; X-Ratelimit-Reset = 1267576025; Andrew Stone Twitter / @twittelator http://www.stone.com got iPhone? http://j.mp/twitpro http://j.mp/tweettv-app On Mar 2, 11:47 am, eclipsed4utoo ryanalford...@gmail.com wrote: I thought that the OAuth Rate Limit went up to 350? I am still getting 150. Here is the returned XML from my request tohttp://api.twitter.com/1/account/rate_limit_status.xml ?xml version=1.0 encoding=UTF-8? hash reset-time type=datetime2010-03-02T19:42:28+00:00/reset-time hourly-limit type=integer150/hourly-limit reset-time-in-seconds type=integer1267558948/reset-time-in- seconds remaining-hits type=integer150/remaining-hits /hash I am using OAuth and using the new version of the REST API. What else do I need to do?
[twitter-dev] Follow me on Twitter
I am creating a project for a rather large client, and have run into a twitter api question. The client wants to create a follow me on twitter bug on the page, but they do not want to land on any page that is a twitter.com address? is it possible to create an experience in a browser where someone can choose to follow another twitter user without every going to the twitter site? thanks alex
[twitter-dev] Obj-C xAuth Demo
Hi guys, For those looking to implement xAuth for Mac OS X, I've set up a complete working demo app. It uses MGTwitterEngine and the OAConsumer libs to do the dirty work and just adds enough to implement the new xAuth flow. I've tried to keep the code as simple to understand as possible, but it does the basics: - Adds the required parameters to the access token request - Overloads the request method in MGTwitterEngine with a signed request. - Shows how to store the access key in the Mac OS X Keychain. - Performs a basic tweet post and fetches the home timeline. It's just meant to help people get going and see a complete solution in action or a as a resource to compare their own solution. I did one of these for OAuth last summer and it was pretty popular, so I figured I'd just keep the ball rolling. You can see the github repo here: http://github.com/yourhead/xAuth_ObjC_Test_App And if you're not approved for xAuth you can download a complete Mac OS X binary that was compiled with working keys -- in case you just need something simple to TCP dump. You can download the binary here: http://github.com/yourhead/xAuth_ObjC_Test_App/downloads I'd be pleased with any sort of feedback, about the code, about the app, or just ways that it could be made more approachable for people new to the topic. isaiah http://twitter.com/isaiah/ http://twitter.com/kiwi-app/
[twitter-dev] Re: forcing api.twitter.com resources - tomorrow
Hmm.. I tested with oauth via both 'api.twitter.com' and 'twitter.com'. Both works well. And I can see the xauth uri has 'api.twitter.com' in front. Can I just change all those twitter.com to api.twitter.com? including oauth methods? It seems like api documentation for oauth method is not yet updated. On 3월3일, 오전11시09분, Raffi Krikorian ra...@twitter.com wrote: brian - this is exactly my understanding as well. we'll be putting a bunch more eyes on this. On Tue, Mar 2, 2010 at 3:51 PM, Brian Smith br...@briansmith.org wrote: Dewald Pretorius wrote: Raffi, There appears to be ground for confusion here. I'm sure some folks are still sending some API calls to twitter.com. Could you please put up a page that explains which calls *must* go to api.twitter.com, and after tomorrow won't work on twitter.com? And vice versa, which calls must go to twitter.com, and won't work on api.twitter.com. Here is my understanding: Right now, you might be able to access resources through api.twitter.comthat aren't part of the official public API. Starting tomorrow, api.twitter.com will only implement the official, public API. If you rely on resources that aren't in the official public API, and you are accessing them through api.twitter.com, your program will probably stop working tomorrow. If you are only using the published API through api.twitter.com, or you are accessing resources through the twitter.com domain, this change doesn't affect you (AFAICT), but, you should change your code to use http[s]://api.twitter.com/1/ instead of http[s]://twitter.com/ as the base URI at your earliest convenience, as Twitter said a few months ago. Since the OAuth resources are documented as being on twitter.com (not api.twitter.com), you should be accessing them through twitter.com (not api.twitter.com), even though you should be accessing the Twitter API through api.twitter.com. Correct? - Brian (@BRIAN_) -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: icon size issue
Noted in issue http://code.google.com/p/twitter-api/issues/detail?id=601 If you're developing for mobile, try http://tinysrc.net/ to dynamically resize the avatars. On Feb 27, 1:44 am, eco_bach bac...@gmail.com wrote: Anyone know what the eta is for fixing the icon size issue? I just came across 1 that was 432X432 pixels!!! Obviously won't work for mobile...
[twitter-dev] Updates Since Last API Call
Hello, Just wondering if there is any way to grab all updates since the last API call for the user logged in? Best Regards, Craig Brass
[twitter-dev] Guidance over a Twitter API project
Hello, I`m Edie and I am a Webdesigner. Here is the thing. I was asked to do a freelancer with some twitter interactions. The client has a website and wanted to do a promotion. What is suppose to do? The user follows the twitter sites owner. After the following action, automatically sends to the user an e-mail with a form. But the form is just open for the user who follow the twitter. What I need is guidance to where to start and if is actually possible to do this with twitter API or other method. Thank You in advance Edie
Re: [twitter-dev] Re: OAuth Rate Limit Increase - Not seeing it
I was able to get that working. I didn't notice that those headers were only sent for requests that counted against the rate limit. Ryan On Tue, Mar 2, 2010 at 6:33 PM, twittelator and...@stone.com wrote: I reported this bug yesterday. Instead of making that extra call, why not look at the response headers which come back with each API ACCESS - you'll get the info you need: X-Ratelimit-Limit = 150; X-Ratelimit-Remaining = 133; X-Ratelimit-Reset = 1267576025; Andrew Stone Twitter / @twittelator http://www.stone.com got iPhone? http://j.mp/twitpro http://j.mp/tweettv-app On Mar 2, 11:47 am, eclipsed4utoo ryanalford...@gmail.com wrote: I thought that the OAuth Rate Limit went up to 350? I am still getting 150. Here is the returned XML from my request tohttp:// api.twitter.com/1/account/rate_limit_status.xml ?xml version=1.0 encoding=UTF-8? hash reset-time type=datetime2010-03-02T19:42:28+00:00/reset-time hourly-limit type=integer150/hourly-limit reset-time-in-seconds type=integer1267558948/reset-time-in- seconds remaining-hits type=integer150/remaining-hits /hash I am using OAuth and using the new version of the REST API. What else do I need to do?
[twitter-dev] What is the correct OAuth API endpoint
What is the correct API end-point for OAuth authenticated, *documented* API calls? http(s)://twitter.com http(s)://api.twitter.com http(s)://api.twitter.com/1
Re: [twitter-dev] Re: xAuth
* Berto mstbe...@gmail.com [100303 06:42]: Isn't that using a GET request versus the docs saying POST? And I thought parameters were supposed to be normalized except for signature which gets attached at the end? Hmmm. I completely missed the fact that the documentation specifies POST. I used GET and it worked. When I use a POST, I get a 401. Doc bug? The order you *send* the parameters doesn't matter---the order of the base string used for generating the signature does. The underlying libraries I use assemble the parameters in an arbitrary order. Generation of the signature is a separate call and builds it's own base string from a hash (associative array). @semifor
Re: [twitter-dev] Re: OAuth Rate Limit Increase - Not seeing it
I just want to ask how you guys handle the following situation. And please correct anything that is incorrect. The user starts up your application, and they have exhausted all of their rate limit(using another application). Your application does not know this when it is first starting because you haven't made a rate limited request yet. You now make the rate limited request, and you get the 403: Forbidden error back. I can only assume that Twitter will send the X-Ratelimit-Limit header with the response error. Does your application allow this request and then process the error, set the rate limit information(you would need the date to tell the user when the rate limit will reset), and go about your business? In my app, I do a rate limit check before making the request(using the account/rate_limit_status method). Since I can no longer do this(since that method returns 150 instead of 350), I was wondering how others handle this. Just my personal opinion, but I think it's a horrible decision to have the rate limiting headers ONLY returned for rate limited methods. This now requires me to make a rate limited call just to get the rate limit, which brings the previous scenario into play. Thanks, Ryan On Wed, Mar 3, 2010 at 9:44 AM, Ryan Alford ryanalford...@gmail.com wrote: I was able to get that working. I didn't notice that those headers were only sent for requests that counted against the rate limit. Ryan On Tue, Mar 2, 2010 at 6:33 PM, twittelator and...@stone.com wrote: I reported this bug yesterday. Instead of making that extra call, why not look at the response headers which come back with each API ACCESS - you'll get the info you need: X-Ratelimit-Limit = 150; X-Ratelimit-Remaining = 133; X-Ratelimit-Reset = 1267576025; Andrew Stone Twitter / @twittelator http://www.stone.com got iPhone? http://j.mp/twitpro http://j.mp/tweettv-app On Mar 2, 11:47 am, eclipsed4utoo ryanalford...@gmail.com wrote: I thought that the OAuth Rate Limit went up to 350? I am still getting 150. Here is the returned XML from my request tohttp:// api.twitter.com/1/account/rate_limit_status.xml ?xml version=1.0 encoding=UTF-8? hash reset-time type=datetime2010-03-02T19:42:28+00:00/reset-time hourly-limit type=integer150/hourly-limit reset-time-in-seconds type=integer1267558948/reset-time-in- seconds remaining-hits type=integer150/remaining-hits /hash I am using OAuth and using the new version of the REST API. What else do I need to do?
Re: [twitter-dev] Re: forcing api.twitter.com resources - tomorrow
yes - you could just use api.twitter.com for oauth methods. we're working on getting those moved to the versioned endpoints as well, just FYI - so you may have to move them again to api.twitter.com/1 at some point. 2010/3/3 Caizer cai...@gmail.com Hmm.. I tested with oauth via both 'api.twitter.com' and 'twitter.com'. Both works well. And I can see the xauth uri has 'api.twitter.com' in front. Can I just change all those twitter.com to api.twitter.com? including oauth methods? It seems like api documentation for oauth method is not yet updated. On 3월3일, 오전11시09분, Raffi Krikorian ra...@twitter.com wrote: brian - this is exactly my understanding as well. we'll be putting a bunch more eyes on this. On Tue, Mar 2, 2010 at 3:51 PM, Brian Smith br...@briansmith.org wrote: Dewald Pretorius wrote: Raffi, There appears to be ground for confusion here. I'm sure some folks are still sending some API calls to twitter.com. Could you please put up a page that explains which calls *must* go to api.twitter.com, and after tomorrow won't work on twitter.com? And vice versa, which calls must go to twitter.com, and won't work on api.twitter.com. Here is my understanding: Right now, you might be able to access resources through api.twitter.comthat aren't part of the official public API. Starting tomorrow, api.twitter.com will only implement the official, public API. If you rely on resources that aren't in the official public API, and you are accessing them through api.twitter.com, your program will probably stop working tomorrow. If you are only using the published API through api.twitter.com, or you are accessing resources through the twitter.com domain, this change doesn't affect you (AFAICT), but, you should change your code to use http[s]://api.twitter.com/1/ instead of http[s]://twitter.com/ as the base URI at your earliest convenience, as Twitter said a few months ago. Since the OAuth resources are documented as being on twitter.com (not api.twitter.com), you should be accessing them through twitter.com(not api.twitter.com), even though you should be accessing the Twitter API through api.twitter.com. Correct? - Brian (@BRIAN_) -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Data rates from yesterday's meeting?
I think in megabits per second, not megabytes per second. If I said megabytes on Monday night, apologies. This rate is now easy enough to deduce. A JSON tweet is about 1,400 bytes. We announced 50mm tweets per day: 5000 * 1400 / (24*3600) * 8 6481480 Or 6.4mbit, average. Peak rate is somewhat higher than the average. So, very, very roughly... -John On Tue, Mar 2, 2010 at 9:15 PM, M. Edward (Ed) Borasky zzn...@gmail.comwrote: I'm looking at the tweet chat from yesterday's meeting. I see these numbers: 1. Firehose is 8 MB/sec. 2. Gardenhose is 15% of Firehose 3. Spritzer is 5% of Firehose A little math gives Gardenhose at 1.2 MB/sec and Spritzer at 400 KB/ sec. I'm currently connected to sample, which I am assuming is Spritzer. The peak rate I've seen in about 1.5 weeks is 38000 bytes per second. So - is 8 MB/sec. 8 megaBytes per second, or is it only 8 megabits = 1 megaByte per second???
Re: [twitter-dev] Data rates from yesterday's meeting?
Spritzer.json was depreciated in September 2009. It currently rewrites to /1/statuses/sample.json, and that rewrite rule is being removed. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Mar 3, 2010 at 5:41 AM, Ed Costello epcoste...@gmail.com wrote: Related question: is there any technical difference between http://stream.twitter.com/spritzer.json and http://stream.twitter.com/1/statuses/sample.json? spritzer.json is what one gets if you click on the link to sample.json in the firehose page on the wiki. -- -ed costello @epc / +13474080372
Re: [twitter-dev] Data rates from yesterday's meeting?
Yep - I used the same logic. I didn't hear the Monday session, just saw the archived tweet stream. It was stated in MB/s, which is why I asked. My calculations agreed with the assumption of bits instead of bytes. ;-) Now I can go write my blog post. ;-) -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky/ A mathematician is a device for turning coffee into theorems. ~ Paul Erd?s Quoting John Kalucki j...@twitter.com: I think in megabits per second, not megabytes per second. If I said megabytes on Monday night, apologies. This rate is now easy enough to deduce. A JSON tweet is about 1,400 bytes. We announced 50mm tweets per day: 5000 * 1400 / (24*3600) * 8 6481480 Or 6.4mbit, average. Peak rate is somewhat higher than the average. So, very, very roughly... -John On Tue, Mar 2, 2010 at 9:15 PM, M. Edward (Ed) Borasky zzn...@gmail.comwrote: I'm looking at the tweet chat from yesterday's meeting. I see these numbers: 1. Firehose is 8 MB/sec. 2. Gardenhose is 15% of Firehose 3. Spritzer is 5% of Firehose A little math gives Gardenhose at 1.2 MB/sec and Spritzer at 400 KB/ sec. I'm currently connected to sample, which I am assuming is Spritzer. The peak rate I've seen in about 1.5 weeks is 38000 bytes per second. So - is 8 MB/sec. 8 megaBytes per second, or is it only 8 megabits = 1 megaByte per second???
Re: [twitter-dev] Re: forcing api.twitter.com resources - tomorrow
For the OAuth endpoints on api.twitter.com, was the sign off redirection bug [1] ever fixed? This was one issue keeping me from switching from twitter.com - api.twitter.com for the OAuth methods. Josh [1] http://code.google.com/p/twitter-api/issues/detail?id=1207 2010/3/3 Raffi Krikorian ra...@twitter.com yes - you could just use api.twitter.com for oauth methods. we're working on getting those moved to the versioned endpoints as well, just FYI - so you may have to move them again to api.twitter.com/1 at some point. 2010/3/3 Caizer cai...@gmail.com Hmm.. I tested with oauth via both 'api.twitter.com' and 'twitter.com'. Both works well. And I can see the xauth uri has 'api.twitter.com' in front. Can I just change all those twitter.com to api.twitter.com? including oauth methods? It seems like api documentation for oauth method is not yet updated. On 3월3일, 오전11시09분, Raffi Krikorian ra...@twitter.com wrote: brian - this is exactly my understanding as well. we'll be putting a bunch more eyes on this. On Tue, Mar 2, 2010 at 3:51 PM, Brian Smith br...@briansmith.org wrote: Dewald Pretorius wrote: Raffi, There appears to be ground for confusion here. I'm sure some folks are still sending some API calls to twitter.com. Could you please put up a page that explains which calls *must* go to api.twitter.com, and after tomorrow won't work on twitter.com? And vice versa, which calls must go to twitter.com, and won't work on api.twitter.com. Here is my understanding: Right now, you might be able to access resources through api.twitter.comthat aren't part of the official public API. Starting tomorrow, api.twitter.com will only implement the official, public API. If you rely on resources that aren't in the official public API, and you are accessing them through api.twitter.com, your program will probably stop working tomorrow. If you are only using the published API through api.twitter.com, or you are accessing resources through the twitter.com domain, this change doesn't affect you (AFAICT), but, you should change your code to use http[s]://api.twitter.com/1/ instead of http[s]://twitter.com/ as the base URI at your earliest convenience, as Twitter said a few months ago. Since the OAuth resources are documented as being on twitter.com (not api.twitter.com), you should be accessing them through twitter.com(not api.twitter.com), even though you should be accessing the Twitter API through api.twitter.com. Correct? - Brian (@BRIAN_) -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: A PubSubHubbub hub for Twitter
All, we just posted the results on our blog : http://blog.superfeedr.com/API/PubSubHubbub/Twitter/feeds/streaming/a-hub-for-twitter/ I'll also sent them to John Kalucki and Ryan Sarver. It's their time to play :D On Mar 2, 7:57 am, Julien julien.genest...@gmail.com wrote: Andrew, it's not so much about making a simpler API, but making it standard : having the same API to get content from 6A blogs, Tumblr's blogs, media sites, social networks... is much easier than implementing one for each service out there. After a small day of poll, here are some results : Do you currently use the Twitter Streaming API? Yes 18 53% No 16 47% Would you use a TwitterPubSubHubbubhub if it was available? Yes 33 97% No 1 3% Have you already implementedPubSubHubbub? Yes 24 71% No 10 29% Obviously, 34 is _not_ a big enough number that I think we have a representative panel of respondant, but we also have big names in here, (including some who have access in the firehose), which makes me think thatPubSubHubbubshould be a viable option for Twitter. If you read this, please take some take to respond : http://bit.ly/hub4twitter Thanks all. Cheers, Julien On Mar 1, 9:02 pm, Andrew Badera and...@badera.us wrote: But how much simpler does it need to be? The streaming API is dead simple. I implemented what seems to be a full client with delete, limit and backoff in parts of two working days. Honestly I think it took me longer to write a workingPubSubHubbubsubscriber client than it did a Twitter Streaming API client. It would be nice if the world was full of free data and universal standards, but if it ain't broke, and it's already invested in, why fix it? ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me:http://www.google.com/search?q=andrew%20badera On Mon, Mar 1, 2010 at 8:44 PM, Julien julien.genest...@gmail.com wrote: Ed, On Mar 1, 5:23 pm, M. Edward (Ed) Borasky zzn...@gmail.com wrote: In light of today's announcement, I'm not sure what the benefits of a middleman would be. http://blog.twitter.com/2010/03/enabling-rush-of-innovation.html Can you clarify a. How much it would cost me to get Twitter data from you via PubSubHubbubvs. getting the feeds directly from Twitter? Free, obviously... as with the use of any hub we host! b. What benefits there are to acquiring Twitter data viaPubSubHubbub over direct access? Much simpler to deal with than a specific streaming Twitter API, specifically if your app has already implemented the protocol for Identica, Buzz, Tumblr, sixapart, posterous, google reader... it's all about standards. On Mar 1, 3:08 pm, Julien julien.genest...@gmail.com wrote: Ola! I know this s some kind of recurring topic for this mailing list. I know all the heat around it, but I think that Twitter's new strategy concerning their firehose is a good occasion to push them to implement thePubSubHubbubprotocol. Superfeedr makes RSS feeds realtime. We host hubs for several big publishers, including Tumblr, Posterous, HuffingtonPost, Gawker and several others. We want to make one for Twitter. Help us assessing the need and convince Twitter they need one (hosted by us or even them, if they'd rather go down that route) : http://bit.ly/hub4twitter Any comment/suggestion is more than welcome.
Re: [twitter-dev] Obj-C xAuth Demo
I saw your repository this morning, it all looks fantastic. I appreciate the work you've done. I'll probably appreciate it more when I actually get around to using it +Clint On Tue, Mar 2, 2010 at 10:29 PM, Isaiah Carew isa...@me.com wrote: Hi guys, For those looking to implement xAuth for Mac OS X, I've set up a complete working demo app. It uses MGTwitterEngine and the OAConsumer libs to do the dirty work and just adds enough to implement the new xAuth flow. I've tried to keep the code as simple to understand as possible, but it does the basics: - Adds the required parameters to the access token request - Overloads the request method in MGTwitterEngine with a signed request. - Shows how to store the access key in the Mac OS X Keychain. - Performs a basic tweet post and fetches the home timeline. It's just meant to help people get going and see a complete solution in action or a as a resource to compare their own solution. I did one of these for OAuth last summer and it was pretty popular, so I figured I'd just keep the ball rolling. You can see the github repo here: http://github.com/yourhead/xAuth_ObjC_Test_App And if you're not approved for xAuth you can download a complete Mac OS X binary that was compiled with working keys -- in case you just need something simple to TCP dump. You can download the binary here: http://github.com/yourhead/xAuth_ObjC_Test_App/downloads I'd be pleased with any sort of feedback, about the code, about the app, or just ways that it could be made more approachable for people new to the topic. isaiah http://twitter.com/isaiah/ http://twitter.com/kiwi-app/
[twitter-dev] Deprecating /statuses/public_timeline resource on 4/5/10
This is an announcement that we will be deprecating the * /statuses/public_timeline* resource as of April 5th (4/5/10). Please let us know if there are any major concerns. Thanks, Ryan
Re: [twitter-dev] Deprecating /statuses/public_timeline resource on 4/5/10
This is an announcement that we will be deprecating the * /statuses/public_timeline* resource as of April 5th (4/5/10). Please let us know if there are any major concerns. Why? -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Tell the truth, and run. -- Yugoslav proverb ---
Re: [twitter-dev] What is the correct OAuth API endpoint
Hi Zhami, http(s)://api.twitter.com is best for OAuth-related operations like the requestToken, accessToken, and authorizeToken steps of the OAuth flow. These aren't versioned the way that resource-based APIs are. http://api.twitter.com/oauth/request_token http://api.twitter.com/oauth/authorize http://api.twitter.com/oauth/access_token For resource requests for things like tweets, timelines, lists, etc. use the versioned URL scheme with the api.twitter.com. Adopting the versioning scheme helps protect you from future changes to what might be considered the default version of the API, should things ever change significantly. http://api.twitter.com/1/statuses/friends_timeline.json Taylor On Wed, Mar 3, 2010 at 7:02 AM, Zhami stu...@zhameesha.com wrote: What is the correct API end-point for OAuth authenticated, *documented* API calls? http(s)://twitter.com http(s)://api.twitter.com http(s)://api.twitter.com/1
Re: [twitter-dev] Follow me on Twitter
Hello Alex, Not really, no. They'll at least have to travel to the Twitter site to go through the OAuth process. Scott. On 3 Mar 2010, at 02:58, AlexBeck wrote: I am creating a project for a rather large client, and have run into a twitter api question. The client wants to create a follow me on twitter bug on the page, but they do not want to land on any page that is a twitter.com address? is it possible to create an experience in a browser where someone can choose to follow another twitter user without every going to the twitter site? thanks alex smime.p7s Description: S/MIME cryptographic signature
Re: [twitter-dev] What is the correct OAuth API endpoint
Zhami, I'd go with https://api.twitter.com/1 Scott. On 3 Mar 2010, at 15:02, Zhami wrote: What is the correct API end-point for OAuth authenticated, *documented* API calls? http(s)://twitter.com http(s)://api.twitter.com http(s)://api.twitter.com/1 smime.p7s Description: S/MIME cryptographic signature
[twitter-dev] What is limit for receiving direct messages?
What is the limit for receiving direct messages? Whether I would be able to receive more than 250 direct messages ?? from different users? Thanks Shan
[twitter-dev] Monday's Dev Meeting
Has anyone published notes about the meeting somewhere?
[twitter-dev] Are there anyway to retrieve user profile from twitter API
I now want to enable user to link their twitter account to our website, that means, after OAuth, twitter will forward user to my website, and then I want to retrieve that user's profile, such as twitterId, name..., and prefill the form for user to register. This steps is pretty straightforword, just like any other social websites, such as linkedIn, myspace. But I didn't realize that after Oauth step, I am lost in finding a suitable API to retrieve that user's profile. I would like to use this one, http://api.twitter.com/1/users/show.format But this API require the userID or screenName, that is what I don't have. So question is: how to retrieve the userId or screen name and other profile information for the user? Thanks
[twitter-dev] Re: xAuth
Raffi, Can you comment on the first part of Marc's last reply? Thanks! On Mar 3, 9:24 am, Marc Mims marc.m...@gmail.com wrote: * Berto mstbe...@gmail.com [100303 06:42]: Isn't that using a GET request versus the docs saying POST? And I thought parameters were supposed to be normalized except for signature which gets attached at the end? Hmmm. I completely missed the fact that the documentation specifies POST. I used GET and it worked. When I use a POST, I get a 401. Doc bug? The order you *send* the parameters doesn't matter---the order of the base string used for generating the signature does. The underlying libraries I use assemble the parameters in an arbitrary order. Generation of the signature is a separate call and builds it's own base string from a hash (associative array). @semifor
Re: [twitter-dev] Introduce yourself!
Hi, I'm Roberto Etcheverry (@retcheverry) and I develop twavel.com (@twaveltak), a travel deal site that feeds on tweets and lets users post their travel deals on Twitter among other things. I'm a Perl and Python programmer, Linux fan and vi addict. I'm using the excellent Net::Twitter Perl module done by Marc Mims (@semifor). Abraham Williams wrote: We have not had an introductions thread in a long time (or ever that I could find) so I'm starting one. Don't forget to add an answer to the tools thread [1](Gmail link [2]) as well. I'm Abraham Williams, I've been working with the Twitter API and this group since early 2008. I do mostly freelance Drupal and Twitter API integration and personal projects. I love seeing the creative projects developers build or integrate with the API and look forward to meeting many of you at Chirp. TwitterOAuth [3] the first PHP library to support OAuth is built and maintained by me, and will hopefully see a new release soon. I also built a fun Chrome extension [4] that integrates common friends and followers into Twitter profiles. The feature I would most like added to the API is a conversation method to get replies to a specific status. So. Who are you, what do you do, what have you built, and what feature do you most want to see added? @Abraham [1] http://groups.google.com/group/twitter-development-talk/browse_thread/thread/c7cdaa0840f0de84/ [2] https://mail.google.com/mail/#inbox/12680cd0fa59011e [3] https://chrome.google.com/extensions/detail/npdjhmblakdjfnnajeomfbogokloiggg [4] http://code.google.com/p/twitter-api/issues/detail?id=142 -- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
Re: [twitter-dev] Re: Introduce yourself!
Hello Twitter Development Community, My name is Taylor Singletary (@episod on Twitter) and I'm Twitter's first developer advocate. I'm all about making the developer experience here awesome. I'm still learning and will always be learning. Learning is fun. A little about my history: I worked at LinkedIn for the past two and half years in a few different roles: a software engineer on the Light Engineering team, technical evangelist for LinkedIn's API programs (partnerships, open API program, OpenSocial-based application platform), as well as a product manager for their InApps platform and the two Twitter-based on-site applications Company Buzz and Tweets. A little about my areas of expertise: REST-based APIs. OAuth Ruby Ruby on Rails Perl PHP Javascript OpenSocial Some Java (I read much better than I write!) If you want to get an idea of how I like to teach things, take a look at some of my presentations on SlideShare: http://bit.ly/9K3Ans -- I think learning should be fun! I know a lot of developers have problems wrapping their heads around OAuth, or dealing with the often sorry state of client libraries out there. It's a fact of life that sometimes you need to get your hands dirty and really understand OAuth top to bottom to debug issues. I've come to love OAuth and I think you should too. OAuth libraries are frequently built with single use cases in mind, ignoring parts of the specification that didn't seem relevant at the time. We as a community need to do a better in making the OAuth library ecosystem a better one. Hold me closer, OAuth Dancer http://bit.ly/oauth-dancer Today I open sourced a Ruby on Rails tool that helps you debug and test OAuth 1.0a-based service providers. It's called the OAuth Dancer and you can get it from github at http://bit.ly/oauth-dancer -- this tool has many uses and I plan to keep it up to date with new features for awhile; it's nowhere near feature complete yet. I hope it helps ease the burden of developing with OAuth, offering you working golden examples that you can use in tandem with whatever implementation you're working on. I'm still ramping up here at Twitter, and it'll take some time before you'll see me here on the mailing list frequently. I'm watching and listening. We're in this together. And we're going to make it awesome together. Thanks, Taylor Singletary Developer Advocate Twitter http://www.twitter.com/episod On Tue, Mar 2, 2010 at 8:06 PM, Arnaud Meunier arnaud.meun...@twitoaster.com wrote: Hello folks, My name is Arnaud Meunier and I'm a Paris-based Twitter Developer Web Entrepreneur. I built http://twitoaster.com a real-time (thanks to the streaming API) conversation threading service / client helping people and businesses to improve and optimize the way they communicate with their Twitter followers. I signed up for Chirp, and I hope to meet many of you there! All the best, Arnaud. On Feb 19, 9:20 pm, Abraham Williams 4bra...@gmail.com wrote: We have not had an introductions thread in a long time (or ever that I could find) so I'm starting one. Don't forget to add an answer to the tools thread [1](Gmail link [2]) as well. I'm Abraham Williams, I've been working with the Twitter API and this group since early 2008. I do mostly freelance Drupal and Twitter API integration and personal projects. I love seeing the creative projects developers build or integrate with the API and look forward to meeting many of you at Chirp. TwitterOAuth [3] the first PHP library to support OAuth is built and maintained by me, and will hopefully see a new release soon. I also built a fun Chrome extension [4] that integrates common friends and followers into Twitter profiles. The feature I would most like added to the API is a conversation method to get replies to a specific status. So. Who are you, what do you do, what have you built, and what feature do you most want to see added? @Abraham [1] http://groups.google.com/group/twitter-development-talk/browse_thread... [2]https://mail.google.com/mail/#inbox/12680cd0fa59011e [3] https://chrome.google.com/extensions/detail/npdjhmblakdjfnnajeomfbogo... [4]http://code.google.com/p/twitter-api/issues/detail?id=142 -- Abraham Williams | Community Advocate |http://abrah.am Project | Out Loud |http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
[twitter-dev] Can't access old tweets via statuses/user_timeline
Hi, I am Trying to backup all my tweets (for @seiz) but it seems tweets of a certain age aren't accessible via the api (the oldest tweet i get is ID 1226937920 from 02/2009). I am even using since_id and max_id restrictions in the API call in order to avoid hitting a pagination limit and still can't get any very old tweets. Same goes for mentions (and i guess everything else like DMs too). How can i get all my tweets in order to back them up? Note, i basically have to do this only once and then only get a daily/ weekly or whatever delta using since_id, so it should not put too much load on the api. PS: there's also a BUG. when using max_id in the api call, the result will include tweets where ID==max_id which, according to the documentation should not be the case and only every thweet with an id between since_id and max_id (but not including max_id) should be returned. (I filed a ticket on help.twitter, but am also posting here, as past experience seemed to indicate, that the ticketing system is not maintained – sorry for the cross posting) Thanks Stefan
[twitter-dev] Re: Updates Since Last API Call
You have to somehow store the ID of the newest tweet you saw in your last API call and then use since_id in your new API call to only get tweets/mentions etc which are newer than said ID.
[twitter-dev] Re: Follow me on Twitter
Twitter API lets you follow and unfollow people. But, the user needs to login, and these days the fancy way to do login is through OAuth, which means a trip to twitter.com anyway. On Mar 2, 9:58 pm, AlexBeck alexbeck...@gmail.com wrote: I am creating a project for a rather large client, and have run into a twitter api question. The client wants to create a follow me on twitter bug on the page, but they do not want to land on any page that is a twitter.com address? is it possible to create an experience in a browser where someone can choose to follow another twitter user without every going to the twitter site? thanks alex
[twitter-dev] New way to get highest id?
With the upcoming deprecation of /statuses/public_timeline that was just announced, will there be any way to find out the (approximate) highest tweet id? I know the streaming API would work but it seems like overkill. Scenario: in my app I cache tweets for performance and to avoid over- calling the API. If someone references a tweet whose id doesn't exist (e.g. by searching), I'd like to be able to tell the difference between that tweet was deleted and that tweet id has never been used yet. I currently poll the public_timeline once every few minutes. Ids that are missing but are lower than the highest one are considered deleted. As you can see based on my current mechanism, exact precision doesn't matter much to me. A better alternative for this use case would be a deleted indicator (perhaps in the HTTP code?) if I try to retrieve a tweet that has been deleted. It could be different than the code returned if a tweet had never been created.
[twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
why? On Mar 3, 9:45 pm, Ryan Sarver rsar...@twitter.com wrote: This is an announcement that we will be deprecating the * /statuses/public_timeline* resource as of April 5th (4/5/10). Please let us know if there are any major concerns. Thanks, Ryan
Re: [twitter-dev] Re: Introduce yourself!
The single thing that would help me the most is a Twitter-created open source library to connect to Streaming, written in *C* and supplied with SWIG .i interface definition files. That way, I would know: a. I had the correct connection algorithm, backoffs, DNS time-to-live, etc. b. I had Twitter-supplied code. c. I could connect to Streaming using *any* scripting language SWIG supports. I haven't looked at all of the libraries, but the two I've worked with, one in Ruby and one in Perl, both translate the raw JSON coming out of Streaming into native objects. This isn't going to scale, and Twitter recommends against it. I simply want a C library to connect to Streaming with a specified parameter set, do the DNS time-to-live stuff right, do the reconnect stuff right, and present me with JSON text lines I can queue, write to a file, or, for that matter, drop on the floor. And really, I only care about JSON - you can go ahead and deprecate XML and I'll write a blog post telling the world how many kittens you've saved! ;-) I think the rest of the API is very well-covered in open source libraries. I only work in Perl and Ruby, so I can't comment on the other major languages, but I've never heard any complaints from my PHP and Python friends. ;-) -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky/ A mathematician is a device for turning coffee into theorems. ~ Paul Erdos
Re: [twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
Because you're suppose to use home_timeline now, which has everything public_timeline has, plus support for retweets. ~Patrick On Thu, Mar 4, 2010 at 10:40 AM, Carlos carlosju...@gmail.com wrote: why? On Mar 3, 9:45 pm, Ryan Sarver rsar...@twitter.com wrote: This is an announcement that we will be deprecating the * /statuses/public_timeline* resource as of April 5th (4/5/10). Please let us know if there are any major concerns. Thanks, Ryan
[twitter-dev] Retweets
I need to fix my retweets logic. Does anyone know someone (or some recommended service) that retweets ad nauseum (via twitter's formal retweet feature), or nearly so?
Re: [twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
One less method for Twitter to maintain when the data is available through the Streaming API. Abraham On Wed, Mar 3, 2010 at 20:21, Patrick Kennedy kenned...@gmail.com wrote: Because you're suppose to use home_timeline now, which has everything public_timeline has, plus support for retweets. ~Patrick On Thu, Mar 4, 2010 at 10:40 AM, Carlos carlosju...@gmail.com wrote: why? On Mar 3, 9:45 pm, Ryan Sarver rsar...@twitter.com wrote: This is an announcement that we will be deprecating the * /statuses/public_timeline* resource as of April 5th (4/5/10). Please let us know if there are any major concerns. Thanks, Ryan -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
Ops. Was thinking about user_timeline v. home_timeline. So, public_timeline is now going away too. On Thu, Mar 4, 2010 at 12:06 PM, Abraham Williams 4bra...@gmail.com wrote: One less method for Twitter to maintain when the data is available through the Streaming API. Abraham On Wed, Mar 3, 2010 at 20:21, Patrick Kennedy kenned...@gmail.com wrote: Because you're suppose to use home_timeline now, which has everything public_timeline has, plus support for retweets. ~Patrick On Thu, Mar 4, 2010 at 10:40 AM, Carlos carlosju...@gmail.com wrote: why? On Mar 3, 9:45 pm, Ryan Sarver rsar...@twitter.com wrote: This is an announcement that we will be deprecating the * /statuses/public_timeline* resource as of April 5th (4/5/10). Please let us know if there are any major concerns. Thanks, Ryan -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: Introduce yourself!
Hi, I’m Jaanus. My day job has nothing to do with Twitter, but a few months back, I started looking into Twitter and iPhone more closely out of personal interest as a hobby project. I wrote down how OAuth works [1] and made a simple Objective-C implementation [2]. Just now, I released a new iPhone Twitter app, Crème. It just hit the App Store, get it from http://cremeapp.com. As far as I’m aware, it’s one of the first general-purpose Twitter clients on the App Store that uses OAuth for authentication, I haven’t come across others. I use my own PlainOAuth. I think this app breaks some new ground in terms of how to interact with Twitter, I’d be interested in all the feedback. One thing that nobody seems to talk about is read/unread management, which I think about a lot. I’m not sure that it belongs in the API, perhaps at this stage it is better left to clients, but I think all the current clients and also the twitter.com site do a terrible job at it, so I propose a better way with Crème. This is still local to one device, but I do believe that there is potential in syncing reads/ unreads across devices. Until Twitter puts it in their API (if ever), I'll probably be forced to do my own solution. Looking forward to OAuth Echo to do the authentication part of it (e.g if I maintain my own unread server, I'd use OAuth Echo to make sure the reads/unreads of different users are separated and everyone only sees their own.) Twitter API was straightforward to work with, don’t really have any major gripes. There’s a bunch of inconstencies (e.g I can get my own mentions, but not others’), and one thing that is not advertised well is the HTML encoding/decoding (a bunch of fields are HTML-encoded and you need to remember to decode them on client side before displaying... I think this applies only to JSON, which I’m also using). My only “holy crap” moment with Twitter API was when I came across the REST and search user IDs are different bug (http://code.google.com/p/ twitter-api/issues/detail?id=214). That this has not been fixed after all this time, leaves an amateur and shenaniganish taste of the whole Twitter API operation. Fixing it does not get easier with time as increasingly more data is generated, you know... but, on the client side I do not need to do global matching for any users, I could work around it by simply using screen names throughout the app, so for my particular case it was not a showstopper, but it leaves a bad taste. One other thing I didn't find much info about is how Twitter works with profile images. As users upload them, multiple versions are generated, and you have to truncate and replace parts of filename to get the different versions, but I came across it as hearsay, I don't think it's documented. So, check out cremeapp.com :) [1] http://www.jaanuskase.com/en/2010/01/understanding_the_guts_of_twit.html [2] http://www.jaanuskase.com/en/2010/01/an_example_iphone_twitter_app.html rgds, Jaanus @jaanus http://www.jaanuskase.com/ On Feb 19, 3:20 pm, Abraham Williams 4bra...@gmail.com wrote: We have not had an introductions thread in a long time (or ever that I could find) so I'm starting one. Don't forget to add an answer to the tools thread [1](Gmail link [2]) as well. I'm Abraham Williams, I've been working with the Twitter API and this group since early 2008. I do mostly freelance Drupal and Twitter API integration and personal projects. I love seeing the creative projects developers build or integrate with the API and look forward to meeting many of you at Chirp. TwitterOAuth [3] the first PHP library to support OAuth is built and maintained by me, and will hopefully see a new release soon. I also built a fun Chrome extension [4] that integrates common friends and followers into Twitter profiles. The feature I would most like added to the API is a conversation method to get replies to a specific status. So. Who are you, what do you do, what have you built, and what feature do you most want to see added? @Abraham [1]http://groups.google.com/group/twitter-development-talk/browse_thread... [2]https://mail.google.com/mail/#inbox/12680cd0fa59011e [3]https://chrome.google.com/extensions/detail/npdjhmblakdjfnnajeomfbogo... [4]http://code.google.com/p/twitter-api/issues/detail?id=142 -- Abraham Williams | Community Advocate |http://abrah.am Project | Out Loud |http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
Re: [twitter-dev] Retweets
I need to fix my retweets logic. Does anyone know someone (or some recommended service) that retweets ad nauseum (via twitter's formal retweet feature), or nearly so? I certainly wouldn't call it ad nauseum, but the esteemed @NickKristof retweets fairly regularly. -josh
Re: [twitter-dev] Retweets
Also @scobleizer. Abraham On Wed, Mar 3, 2010 at 21:03, Josh Bleecher Snyder joshar...@gmail.comwrote: I need to fix my retweets logic. Does anyone know someone (or some recommended service) that retweets ad nauseum (via twitter's formal retweet feature), or nearly so? I certainly wouldn't call it ad nauseum, but the esteemed @NickKristof retweets fairly regularly. -josh -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Retweets
Moi (@znmeb) retweets almost exclusively from the web app with the built-in retweet and almost never using the old way. I'd say a good 25 percent of my tweets are retweets, too. Ad nauseam might well describe my stream. ;-) -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky/ A mathematician is a device for turning coffee into theorems. ~ Paul Erd?s Quoting Abraham Williams 4bra...@gmail.com: Also @scobleizer. Abraham On Wed, Mar 3, 2010 at 21:03, Josh Bleecher Snyder joshar...@gmail.comwrote: I need to fix my retweets logic. Does anyone know someone (or some recommended service) that retweets ad nauseum (via twitter's formal retweet feature), or nearly so? I certainly wouldn't call it ad nauseum, but the esteemed @NickKristof retweets fairly regularly. -josh -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.
