Re: [twitter-dev] Re: Can our twitter app call /oauth/revoke?
On Sun, May 02, 2010 at 07:12:00PM -0700, Mr-Yellow wrote: oAuth Core 1.0 Service Providers SHOULD allow Users to revoke Access Tokens. Without this end-point it's impossible for users to disconnect a twitter account. If a user links the wrong account then wishes to remove this link they their only option is a lot of navigation to twitters controls. Your app can still have a 'logout' button which causes the app to forget the user's oauth credentials. As far as your app is concerned, this is the same as if the credentials had been revoked. It's not the ideal situation (if a third party had intercepted the user's credentials and also had access to your app's credentials, they could still use them to impersonate the user), but it *is* possible for a user to disconnect one twitter account from an app and link another without having to go to twitter.com and find the 'revoke credentials' page. -- Dave Sherohman
[twitter-dev] Re: Search API or Streaming API?
Woops, my bad. I meant a meta search that would make use of all third party APIs to display the results. But I got your explanation. So if I intend to process the tweets and make sense of it, the Streaming API is what I would need to take a look at. But if I intend to get the search results and just display them on my site, then I guess the search API is what I should use! Pretty much clears everything, so cool! Thanks a lot! -Nischal On May 4, 3:27 am, John Kalucki j...@twitter.com wrote: If you are going to build a search engine, you'll need all of the Tweets to search over them. For this, you'll want to take the Firehose of all public statuses. http://apiwiki.twitter.com/Streaming-API-Documentation You'll need a commercial data license to do this. Email api to get started. GAE currently does not allow standing connections to the Streaming API. Also, you'll need considerably more resources than GAE to build a search engine. You'll need dozens of cores and hundreds of spindles just to get started. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sun, May 2, 2010 at 5:28 AM, nischalshetty nischalshett...@gmail.com wrote: I plan to build a search engine which would utilize the search APIs. Should I be using the Twitter Search API or the Streaming API to do the same? What is the difference between the two and would the Streaming API work on the Google App Engine?
[twitter-dev] Re: Mobile OAuth Summary
Hello Raffi, Could you please, get back to us on this? Do you have any plans on resolving that issue? Is there any show stopper? What are we doing with this?! Thanks. On Apr 29, 12:07 pm, Raffi Krikorian ra...@twitter.com wrote: hi. i'll follow up on this - do you have a notion of what browsers, what phones, etc. your users are coming from On Thu, Apr 29, 2010 at 1:49 AM, twittme_mobi nlupa...@googlemail.comwrote: Hello, I migrated my mobile web site to OAuth. Now, I have a lot of users complaining that the OAuth page of twitter is not mobile friendly.Some of them are getting just a blank screen or just cannot open it. My honest question is - this is being discussed many times but where are we with this? Are all those users really suppose to get such a bad user experience? Why would you need a javascript on a login page?Is it so hard to create such page just for mobile browsers? Is anybody handling this - I mean it is an obvious problem that we have for more than a year already. Any comments on this are highly appreciated. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Re: Tweeting from PHP backed will also require OAuth in the upcoming changes?
Many thanks, guys. Got it On May 4, 12:35 am, Abraham Williams 4bra...@gmail.com wrote: You can checkout this page describing using a script to post to a single Twitter account:http://dev.twitter.com/pages/oauth_single_token One of the examples is for my PHP library:http://github.com/abraham/twitteroauth Abraham On Mon, May 3, 2010 at 13:04, YCBM youcannotb...@gmail.com wrote: Hi Paul, Posting status updates using Basic Auth like that won't work any more after 6/30. You'll need to use a PHP oAuth class (there are a few of them athttp://dev.twitter.com/pages/oauth_libraries#php) as well as register an oAuth app. Best, Y On May 3, 3:17 pm, Paul A. hellodev@gmail.com wrote: Hi guys, Quick question that hunts me and can't find an answer. I'm using this line of code to post tweets to my account direclty from my website $host = http://twitter.com/statuses/update.xml? status=.urlencode(stripslashes(urldecode($message))) and posting it with curl with my user/password Will this still going to work after Twitter upcoming June requirement for Oauth. It's unclear to me. Thanks, Paul -- Abraham Williams | Developer for hire |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: invalid response from
I was quoting a part of the reply that I got from my POST-request to retrieve an access-token from an authorized request-token. Tried to reproduce, but now all I get are the oauth_token, oauth_token_secret, user_id and screen_name attributes. So it's fixed already :) Thanks for following up, Cheers, Mark On May 3, 5:20 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Mark, We shouldn't (and don't as far as I can tell) return an oauth_version parameter on the response to an access token request -- at least when using header-based OAuth. Are you using query-string based OAuth and receiving this? Taylor Singletary Developer Advocate, Twitterhttp://twitter.com/episod On Mon, May 3, 2010 at 2:03 AM, Mark Dobrinic mdobri...@gearjunkies.comwrote: The oauth_version parameter as response from an access_key request (https://api.twitter.com/oauth/access_token) is wrongly returned; it now returns something like this: oauth_version=1.0oauth_token=130421609- lnF0m7YLuI0TRXPAWdPaLqjmlQ65Dx7aXE7N1ri0 It is probably a little thing for Twitter to fix though ;) Cheers! Mark
[twitter-dev] Re: Getting error 6 on geo/nearby_places
Okay Raffi, thanks for the insight. Let me know when more international data sets are available. Might also be useful to know which cheesehole parts of Germany are already covered. :) On May 3, 10:17 pm, Raffi Krikorian ra...@twitter.com wrote: we're definitely working through the issues involved launching bigger data sets - the data sets that we're publicly supporting right now is the united states. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
[twitter-dev] Drastic drop in Streaming API bandwidth usage..
Hi, Ssince May 1 I have noticed a huge drop in bandwidth usage of a machine that I use for processing the streaming API (sample stream). See attached screenshot. Has there been any change on Twitter's side which would cause this? I have not changed any code on my side. Please ignore the peaks; there are some other low-volume services on the machine that could cause it. thanks, -- Harshad RJ http://hrj.wikidot.com attachment: bandwidthScreenshot.png
[twitter-dev] Problem in getting rate-limit status with OAuth.
Hi there, I am studying Abraham's code on github for Oauth to deal with my problem. In my app, user is not going to do authentication. I have two account with(username/password) and I have to use it to get ratelimit status. Studying code shows that, it is redirected(redirect.php) to twitter's window for user authentication. So instead of authenticating user on authentication window, can I get ratelimit status of these two accounts authenticated through the code on github. Is it possible to do or alternatively what should I do? can you suggest me any clue, please? Thank you in advance.
[twitter-dev] Any good iphone twitter engine support xauth?
MGTwitterEngine is great. And updated for oauth and xauth. But the updated looks for Cocoa.h only? Here is other open source obj-c twitter projects. http://github.com/search?langOverride=language=objective-cq=twitterrepo=start_value=1type=Repositoriesx=12y=29 Some of them support oauth or xauth. http://github.com/bengottlieb/Twitter-OAuth-iPhone http://github.com/kimptoc/MGTwitterEngine-1.0.8-OAuth-MyTwitter So a litter confused... which one is better ?
[twitter-dev] Re: MGTwitterEngine with OAuth and XAuth support
Thank you for the great update. Under Cocoa.h (Mac OS X SDK) Build succeeded. But under Foundation.h(iPhone SDK) Can not clear Build. missing some class like SecKeychainRef ... Is this version not iphone friendly? On May 2, 10:57 am, Steve Streza stevestr...@gmail.com wrote: Hey everyone, I'm one of the collaborators on the MGTwitterEngine project for Mac and iPhone developers. We've finished our initial implementation of OAuth and XAuth support within MGTwitterEngine. This uses the OAuthConsumer framework to handle the business end of OAuth, meaning that there are only a couple new MGTwitterEngine APIs you need to use (and we've got a wiki guide for migrating to OAuth). We expect most users of the framework to want to use XAuth to obtain an access token, so we have a convenience API for handling that (of course, you'll need to obtain the opt-in from Twitter). After getting XAuth access, it shouldn't take more than a half hour to get set up to obtain your access token and start sending requests. We're also planning on releasing a new version of MGTwitterEngine with support for some new APIs and bug fixes, as well as OAuth. We're hoping to get this out by WWDC, or at least before the OAuth deadline. We're aware of the buffer needed for App Store approval, so we'll be trying to finish this up ASAP. You can grab the code from the project page here:http://github.com/mattgemmell/MGTwitterEngine/ You can read the migration guide here:http://wiki.github.com/mattgemmell/MGTwitterEngine/migrating-from-bas... Feedback is always welcome. If you have any issues, please file them in the project issue tracker here:http://github.com/mattgemmell/MGTwitterEngine/issues Now stop using basic auth already. Thanks, Steve
[twitter-dev] counting sms followers
I know it's come up, but mostly in the context of an API call to see if a specific user is following via sms; could we get a dumb statistical API call to give us at least a hint at this information-- perhaps with a minimum number of followers, if the concern is privacy- based? I'd be pretty happy even if it was severely rate limited. This could be very basic (% of your tweet load over the last 7 days was SMS based) or couched in a slightly more comprehensive report (i.e. in the last 7 days you tweeted this many times and the tweet was actually loaded this X many times by the following: Web - %, sms - %, Applications (All)- %, Retweets (All) - %). An iteration of the breakdown for Retweets would be nice, as well as a breakdown for mobile and desktop applications if you can tell, but beggars can't be choosers. We publish via twitter, but we don't know how we're being read, so we don't know how to tailor the experience we provide. If 20% of the actual loads of our tweets are via SMS, then we shouldn't start running links to flash-based visual poetry, for example. If only 3% of our loads were SMS or even rooted in mobile applications, it might make sense to soup up our content. Trying to satisfy a 97% web-based readership with content that is SMS/browserless-phone-safe might not be the best use of our time, if the reality of our readership is that everyone's already sitting at a computer. I realize broader usage statistics are being guarded fairly closely-- and I think the the tweet was loaded this many times, while useful on our end, is the most likely to expose information you'd like to hold close for now, and is therefore the most expendable; the percents allow room for tools that encourage users to better gear their content to the realities of their readership--and hopefully improve the ecosystem in the process.
[twitter-dev] 403 error's while debugging a windows service
I'm trying to debug a windows service that post to twitter via the TwitterVB .net library, every time I try and post to it I receive a 403 reply. The API doc's say 403 is 403 Forbidden: The request is understood, but it has been refused. An accompanying error message will explain why. This code is used when requests are being denied due to update limits. Can I assume from that, that the oAuth login is OK but their is a problem with the request? I don't think it a rate limiting issue, as the service is only trying to post once every few minutes.
[twitter-dev] OAuth license
I'm having ɑ problem to find your twitter oauth license. Could you help me find where this license is? Thank you :) Sent from my BlackBerry® powered by Sinyal Kuat INDOSAT
[twitter-dev] how to stop my API use
dear, Twitter Development Talk.. i want to stop my API use.. but how can i do? that is very annoy me.. it tweets automaticly and sending direct message automatically, without my permission, it was bothering me.. or would you please turn off the use of the API automatically .. I really hope you can disable the use of my API automatically because it was bothering me.. before I say many thanks..
Re: [twitter-dev] Drastic drop in Streaming API bandwidth usage..
Since you didn't provide your account name, we can only speculate as to your problem. You probably are getting caught up in anti-abuse measures and being thrown off the service. Are you seeing a higher rate of 401s and disconnects? -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, May 4, 2010 at 4:42 AM, Harshad RJ harshad...@gmail.com wrote: Hi, Ssince May 1 I have noticed a huge drop in bandwidth usage of a machine that I use for processing the streaming API (sample stream). See attached screenshot. Has there been any change on Twitter's side which would cause this? I have not changed any code on my side. Please ignore the peaks; there are some other low-volume services on the machine that could cause it. thanks, -- Harshad RJ http://hrj.wikidot.com
Re: [twitter-dev] Re: Search API or Streaming API?
Note that from GAE, your search rate will be throttled significantly, as you are sharing the Search API with every other GAE project on a single IP. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, May 4, 2010 at 12:34 AM, nischalshetty nischalshett...@gmail.com wrote: Woops, my bad. I meant a meta search that would make use of all third party APIs to display the results. But I got your explanation. So if I intend to process the tweets and make sense of it, the Streaming API is what I would need to take a look at. But if I intend to get the search results and just display them on my site, then I guess the search API is what I should use! Pretty much clears everything, so cool! Thanks a lot! -Nischal On May 4, 3:27 am, John Kalucki j...@twitter.com wrote: If you are going to build a search engine, you'll need all of the Tweets to search over them. For this, you'll want to take the Firehose of all public statuses. http://apiwiki.twitter.com/Streaming-API-Documentation You'll need a commercial data license to do this. Email api to get started. GAE currently does not allow standing connections to the Streaming API. Also, you'll need considerably more resources than GAE to build a search engine. You'll need dozens of cores and hundreds of spindles just to get started. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sun, May 2, 2010 at 5:28 AM, nischalshetty nischalshett...@gmail.com wrote: I plan to build a search engine which would utilize the search APIs. Should I be using the Twitter Search API or the Streaming API to do the same? What is the difference between the two and would the Streaming API work on the Google App Engine?
[twitter-dev] home_timeline and mentions from non-followed users
Hello, I understand that the home_timeline API usually does not show replies to people who you do not follow, but it appears that this is true even when you are the one being mentioned or replied to? E.g., my twitter ID is @mdesjardins. Someone I do *not* follow (e.g., @JustinBieber) posts @mdesjardins you look like a turnip shouldn't that show up in my (i.e., authenticated as @mdesjardins) home_timeline API call, even if I don't follow @JustinBieber? This is how the main site behaves, so I'm surprised that the API doesn't behave similarly. Thanks! - mike
Re: [twitter-dev] Problem in getting rate-limit status with OAuth.
Hi Rushikesh, You're asking a few things here, so I'll try to help clear them up: - Your app will need to do some kind of authentication for each of the users. If your application is a web application, and you plan to have more than just the two users you've mentioned, you'll want to implement the entire OAuth 1.0a flow: request token acquisition, sending the user to Twitter's authentication page, and then exchanging the request token for an access token. You would then use the access token for each member to make API calls. If the pool of users for your application will not go beyond the two you mentioned, you might find yourself better served by applying for a one-time use of xAuth to exchange your login credentials for access tokens. If you're building a desktop or mobile application, you will want to use either the OAuth 1.0A PIN/oauth_verifier flow or use xAuth. - Rate limiting is communicated through HTTP headers in the responses you get from the API server. See http://dev.twitter.com/pages/rate-limiting - You can also use the http://api.twitter.com/1/account/rate_limit_statusend point to query on rate limits. When using an access token in the request, the response will indicate the rate limit status for the user represented by that access token. If you aren't using an access token, it will indicate the rate limit for the IP address. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, May 4, 2010 at 2:00 AM, Rushikesh Bhanage rishibhan...@gmail.comwrote: Hi there, I am studying Abraham's code on github for Oauth to deal with my problem. In my app, user is not going to do authentication. I have two account with(username/password) and I have to use it to get ratelimit status. Studying code shows that, it is redirected(redirect.php) to twitter's window for user authentication. So instead of authenticating user on authentication window, can I get ratelimit status of these two accounts authenticated through the code on github. Is it possible to do or alternatively what should I do? can you suggest me any clue, please? Thank you in advance.
Re: [twitter-dev] OAuth license
What do you mean by OAuth license? Are you looking for the API Terms of Service? http://dev.twitter.com/pages/api_terms Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Mon, May 3, 2010 at 9:46 PM, aulia.ama...@gmail.com wrote: I'm having ɑ problem to find your twitter oauth license. Could you help me find where this license is? Thank you :) Sent from my BlackBerry® powered by Sinyal Kuat INDOSAT
[twitter-dev] Re: how to stop my API use
I think this page http://help.twitter.com/forums/10713/entries/31796 should help you. On May 4, 5:29 am, arfin_ardelius fin...@gmail.com wrote: dear, Twitter Development Talk.. i want to stop my API use.. but how can i do? that is very annoy me.. it tweets automaticly and sending direct message automatically, without my permission, it was bothering me.. or would you please turn off the use of the API automatically .. I really hope you can disable the use of my API automatically because it was bothering me.. before I say many thanks..
[twitter-dev] Malformed XML in some Atom feeds...
One very popular Twitter list is Scoble's Tech News Brands list: http://api.twitter.com/1/Scobleizer/lists/tech-news-brands/statuses.atom?per_page=200 I've got a program that's been watching this feed for a while now. Just yesterday I started getting some XML parsing errors. I can create a hack to make this work again on my end, but it's definitely best for Twitter to make sure their XML is well-formed. Here's what feed validator says: http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fapi.twitter.com%2F1%2FScobleizer%2Flists%2Ftech-news-brands%2Fstatuses.atom%3Fper_page%3D200 Sorry This feed does not validate. line 482http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fapi.twitter.com%2F1%2FScobleizer%2Flists%2Ftech-news-brands%2Fstatuses.atom%3Fper_page%3D200#l482, column 73: XML parsing error: unknown:482:73: not well-formed (invalid token) [help http://validator.w3.org/feed/docs/error/SAXError.html] a href=http://www.google.com/support/youtube/bin/answer.py?hl=enanswer=16 ... It looks like whenever a twitter:source of Google appears, it breaks the XML because of the ampersand in the URL: twitter:source a href= http://www.google.com/support/youtube/bin/answer.py?hl=enanswer=164577; rel=nofollowGoogle/a /twitter:source If the ampersand is fixed, I'm guessing things will be happy again. I hope I'm sending this to the right place. Not sure where else to send it. Thanks! -Brandon -- Brandon Stone http://brandonstone.com http://twitter.com/LBStone
Re: [twitter-dev] Malformed XML in some Atom feeds...
Hi Brandon, Thanks for the bug report. We'll work on getting this fixed quickly. Thanks! Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, May 4, 2010 at 7:54 AM, Brandon Stone st...@lbstone.com wrote: One very popular Twitter list is Scoble's Tech News Brands list: http://api.twitter.com/1/Scobleizer/lists/tech-news-brands/statuses.atom?per_page=200 I've got a program that's been watching this feed for a while now. Just yesterday I started getting some XML parsing errors. I can create a hack to make this work again on my end, but it's definitely best for Twitter to make sure their XML is well-formed. Here's what feed validator says: http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fapi.twitter.com%2F1%2FScobleizer%2Flists%2Ftech-news-brands%2Fstatuses.atom%3Fper_page%3D200 Sorry This feed does not validate. line 482http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fapi.twitter.com%2F1%2FScobleizer%2Flists%2Ftech-news-brands%2Fstatuses.atom%3Fper_page%3D200#l482, column 73: XML parsing error: unknown:482:73: not well-formed (invalid token) [help http://validator.w3.org/feed/docs/error/SAXError.html] a href=http://www.google.com/support/youtube/bin/answer.py?hl=enanswer=16 ... It looks like whenever a twitter:source of Google appears, it breaks the XML because of the ampersand in the URL: twitter:source a href= http://www.google.com/support/youtube/bin/answer.py?hl=enanswer=164577; rel=nofollowGoogle/a /twitter:source If the ampersand is fixed, I'm guessing things will be happy again. I hope I'm sending this to the right place. Not sure where else to send it. Thanks! -Brandon -- Brandon Stone http://brandonstone.com http://twitter.com/LBStone
[twitter-dev] Story on Chirp for DigitalMediaBuzz.com
Good morning, I understand Twitter had a developer's conference called Chirp a few weeks back. I would like to discuss potential trends for Twitter regarding this conference for our Web site, digitalmediabuzz.com. This story is due Friday, May 7th. If anyone knows any developers at the conference that wish to contribute to my story, let me know. You can reach me at jzipade...@gmail.com. Thank you, James Zipadelli
Re: [twitter-dev] Problem in getting rate-limit status with OAuth.
Like Rushikesh i am also facing same problem, before my application start working i need to check weather i have ample of call remaining to complete my task for that i had white listed my 2-3 accounts. so the idea that i am thinking is if the OAuth shall give me the remaining call then as per that i should switch automatically to my next white listed account without acknowledging user. Thank you in advance. On Tue, May 4, 2010 at 7:26 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Rushikesh, You're asking a few things here, so I'll try to help clear them up: - Your app will need to do some kind of authentication for each of the users. If your application is a web application, and you plan to have more than just the two users you've mentioned, you'll want to implement the entire OAuth 1.0a flow: request token acquisition, sending the user to Twitter's authentication page, and then exchanging the request token for an access token. You would then use the access token for each member to make API calls. If the pool of users for your application will not go beyond the two you mentioned, you might find yourself better served by applying for a one-time use of xAuth to exchange your login credentials for access tokens. If you're building a desktop or mobile application, you will want to use either the OAuth 1.0A PIN/oauth_verifier flow or use xAuth. - Rate limiting is communicated through HTTP headers in the responses you get from the API server. See http://dev.twitter.com/pages/rate-limiting - You can also use the http://api.twitter.com/1/account/rate_limit_status end point to query on rate limits. When using an access token in the request, the response will indicate the rate limit status for the user represented by that access token. If you aren't using an access token, it will indicate the rate limit for the IP address. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, May 4, 2010 at 2:00 AM, Rushikesh Bhanage rishibhan...@gmail.comwrote: Hi there, I am studying Abraham's code on github for Oauth to deal with my problem. In my app, user is not going to do authentication. I have two account with(username/password) and I have to use it to get ratelimit status. Studying code shows that, it is redirected(redirect.php) to twitter's window for user authentication. So instead of authenticating user on authentication window, can I get ratelimit status of these two accounts authenticated through the code on github. Is it possible to do or alternatively what should I do? can you suggest me any clue, please? Thank you in advance. -- Warm Regards, Gaurav Shaha 9823359549. Don't try to show off, just be youself and do what you ENJOY doing
Re: [twitter-dev] Problem in getting rate-limit status with OAuth.
Switching accounts to get around whitelisting is not in the spirit of the reason whitelisting exists. If your application needs more requests than the default rate limits provided to applications, you should request being whitelisted for increased rate limits. You can apply for expanded rate limiting here: http://twitter.com/help/request_whitelisting Here's a portion of the relevant Terms of Service regarding rate limiting: 3. Your use of the Twitter API and Twitter Content are subject to certain limitations on access, calls, and use of the Twitter API as set forth on dev.twitter.com or as otherwise provided to you by Twitter. If Twitter reasonably believes that you have attempted to exceed or circumvent the rate limits, your ability to use the Twitter API and Twitter Content may be temporarily or permanently blocked. Twitter may monitor your use of the Twitter API to improve the Twitter service and to ensure your compliance with these Rules. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, May 4, 2010 at 10:02 AM, Gaurav Shaha gauravshah...@gmail.comwrote: Like Rushikesh i am also facing same problem, before my application start working i need to check weather i have ample of call remaining to complete my task for that i had white listed my 2-3 accounts. so the idea that i am thinking is if the OAuth shall give me the remaining call then as per that i should switch automatically to my next white listed account without acknowledging user. Thank you in advance. On Tue, May 4, 2010 at 7:26 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Rushikesh, You're asking a few things here, so I'll try to help clear them up: - Your app will need to do some kind of authentication for each of the users. If your application is a web application, and you plan to have more than just the two users you've mentioned, you'll want to implement the entire OAuth 1.0a flow: request token acquisition, sending the user to Twitter's authentication page, and then exchanging the request token for an access token. You would then use the access token for each member to make API calls. If the pool of users for your application will not go beyond the two you mentioned, you might find yourself better served by applying for a one-time use of xAuth to exchange your login credentials for access tokens. If you're building a desktop or mobile application, you will want to use either the OAuth 1.0A PIN/oauth_verifier flow or use xAuth. - Rate limiting is communicated through HTTP headers in the responses you get from the API server. See http://dev.twitter.com/pages/rate-limiting - You can also use the http://api.twitter.com/1/account/rate_limit_status end point to query on rate limits. When using an access token in the request, the response will indicate the rate limit status for the user represented by that access token. If you aren't using an access token, it will indicate the rate limit for the IP address. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, May 4, 2010 at 2:00 AM, Rushikesh Bhanage rishibhan...@gmail.com wrote: Hi there, I am studying Abraham's code on github for Oauth to deal with my problem. In my app, user is not going to do authentication. I have two account with(username/password) and I have to use it to get ratelimit status. Studying code shows that, it is redirected(redirect.php) to twitter's window for user authentication. So instead of authenticating user on authentication window, can I get ratelimit status of these two accounts authenticated through the code on github. Is it possible to do or alternatively what should I do? can you suggest me any clue, please? Thank you in advance. -- Warm Regards, Gaurav Shaha 9823359549. Don't try to show off, just be youself and do what you ENJOY doing
[twitter-dev] Status Update - Incorrect Signature
Hi Folks, I have come till the point where I get the access_token and access token secret from twitter. I need to now update the status which keeps throwing incorrect signature error message. My request is an https POSTrequest. Signature String is POSThttps%3A%2F%2Ftwitter.com%2Fstatuses%2Fupdate.xml%3Fstatus %3D1272994211%2520testoauth_consumer_key%3D** %26oauth_nonce%3D1322660295%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1272994211%26oauth_token%3D- %26oauth_version%3D1.0a%26status %3D1272994211%2520test Response: ?xml version=1.0 encoding=UTF-8? hash request/statuses/update.xml?status=1272994211%20test/request errorIncorrect signature/error /hash Please help. Thanks.
[twitter-dev] Re: Search API or Streaming API?
Oh.. alright.. I thought GAE had multiple IP addresses... hmmm... then might have to look into Amazon Thanks a lot for the info :) -Nischal On May 4, 6:29 pm, John Kalucki j...@twitter.com wrote: Note that from GAE, your search rate will be throttled significantly, as you are sharing the Search API with every other GAE project on a single IP. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, May 4, 2010 at 12:34 AM, nischalshetty nischalshett...@gmail.com wrote: Woops, my bad. I meant a meta search that would make use of all third party APIs to display the results. But I got your explanation. So if I intend to process the tweets and make sense of it, the Streaming API is what I would need to take a look at. But if I intend to get the search results and just display them on my site, then I guess the search API is what I should use! Pretty much clears everything, so cool! Thanks a lot! -Nischal On May 4, 3:27 am, John Kalucki j...@twitter.com wrote: If you are going to build a search engine, you'll need all of the Tweets to search over them. For this, you'll want to take the Firehose of all public statuses. http://apiwiki.twitter.com/Streaming-API-Documentation You'll need a commercial data license to do this. Email api to get started. GAE currently does not allow standing connections to the Streaming API. Also, you'll need considerably more resources than GAE to build a search engine. You'll need dozens of cores and hundreds of spindles just to get started. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sun, May 2, 2010 at 5:28 AM, nischalshetty nischalshett...@gmail.com wrote: I plan to build a search engine which would utilize the search APIs. Should I be using the Twitter Search API or the Streaming API to do the same? What is the difference between the two and would the Streaming API work on the Google App Engine?
Re: [twitter-dev] Status Update - Incorrect Signature
Hi Sushma, It would be easier to assist you if we knew what OAuth library (if any) you are using and the programming language involved and whether you are using header-based or query-string-based authentication. A few quick recommendations: - Use api.twitter.com as the host name when making resource requests. - If you're using query-string based OAuth, considering using header-based OAuth instead. It makes debugging signifigantly easier and keeps concerns separated These are the most likely reasons for your denied signature, assuming everything else you are doing is correct: - Even though the current revision of OAuth is 1.0a, the oauth_version OAuth parameter should always be 1.0 - When using an HTTP method like POST, the key/value pairs that you are sending to Twitter should be part of the POST body, not the URL (the error message indicates you were passing the new status in the URL). In your signature base string you are placing the status=xxx parameters at the end of the request URI and ALSO at the end of the signature base string. Your status parameter should not be attached to the base URL and it should only appear at the end of your signature base string. The status should be specified in the POST body. Your signature base string should end up looking something more like: POSThttps%3A%2F%2Fapi.twitter.com %2Fstatuses%2Fupdate.xmloauth_consumer_key%3D*%26oauth_nonce%3D1322660295%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1272994211%26oauth_token%3D-%26oauth_version%3D1.0%26status%3D1272994211%2520test Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, May 4, 2010 at 10:37 AM, Sush sushma.sha...@gmail.com wrote: Hi Folks, I have come till the point where I get the access_token and access token secret from twitter. I need to now update the status which keeps throwing incorrect signature error message. My request is an https POSTrequest. Signature String is POSThttps%3A%2F%2Ftwitter.com%2Fstatuses%2Fupdate.xml%3Fstatus %3D1272994211%2520testoauth_consumer_key%3D** %26oauth_nonce%3D1322660295%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1272994211%26oauth_token%3D- %26oauth_version%3D1.0a%26status %3D1272994211%2520test Response: ?xml version=1.0 encoding=UTF-8? hash request/statuses/update.xml?status=1272994211%20test/request errorIncorrect signature/error /hash Please help. Thanks.
Re: [twitter-dev] Re: statuses/friends cursor parameter
I can reproduce this, and am taking a look now ---Mark http://twitter.com/mccv On Sat, May 1, 2010 at 2:08 PM, randomnoise jdrodrigues...@gmail.com wrote: I've got the same problem, previous_cursor does not work on: http://dev.twitter.com/doc/get/statuses/friends and may also be broken on : http://dev.twitter.com/doc/get/:user/:list_id/members but seems to work on : http://dev.twitter.com/doc/get/statuses/followers Anyone know anything about this? - jr
[twitter-dev] Re: Upcoming changes to userstream preview
The hydrated social events (as described in the previous email) are
now live. Please let me know if you have questions/issues/concerns
with the new data
---Mark
http://twitter.com/mccv
On Mon, May 3, 2010 at 10:50 AM, Mark McBride mmcbr...@twitter.com wrote:
Userstream previewers:
Coming soon there will be a number of changes that may impact applications.
The first is support for OAuth 1.0a. When rolled out, you will be
able to sign requests to all streaming API endpoints on
betastream.twitter.com. This means that you can use OAuth with both
user streams and other streaming calls (filter, sample, etc.) To
obtain access tokens use the regular twitter.com OAuth flow, then sign
requests to betastream.twitter.com. If you already have an access
token you should be able to use it with the streaming API.
The second is inclusion of fully hydrated objects for the social
events. Instead of just getting a source id, target id, and target
object id you will get the full user object in source and target
fields, and the full status in the target object field (if
applicable). You will also get a created_at field that indicates
the time the social event was created. This should dramatically reduce
the number of REST API calls needed to build a client. Note that most
parsers shouldn't need to change -- the ID field will still be set,
you will just have more fields available. The format is the same as
statuses retrieved via the rest API, with following exceptions:
1) The user's latest status may not be included
2) The user's status count may not be included
3) The user's favorites count may not be included
An example of a hydrated social event is
{created_at=Mon May 03 17:42:55 + 2010,
target_object=
{coordinates=nil,
truncated=false,
created_at=Sun Jun 28 23:10:35 + 2009,
favorited=false,
contributors=nil,
text=looking at cricket eyes!,
id=4,
geo=nil,
in_reply_to_user_id=nil,
source=web,
place=nil,
user=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
in_reply_to_screen_name=nil,
in_reply_to_status_id=nil},
event=favorite,
target=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
source=
{profile_background_tile=false,
name=Jack,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=San Francisco,
created_at=Wed Apr 28 00:00:00 + 2010,
profile_image_url=
http://s3.amazonaws.com/twitter_development/profile_images/2/jack_normal.jpg;,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=0,
id=3,
utc_offset=-28800,
profile_text_color=00,
protected=true,
lang=en,
followers_count=2,
notifications=nil,
verified=false,
description=love, love,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Pacific Time (US Canada),
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=2,
screen_name=jack,
following=nil}}
The third is an improvement to the direct message payload. Currently
it's a bit of a pain to disambiguate statuses and DMs. We'll be
wrapping direct messages in a higher level direct_message object,
e.g.
{direct_message=
{created_at=Wed Apr 28 14:56:31 + 2010,
sender_screen_name=user1,
sender=
{profile_background_tile=false,
name=User1,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=San Francisco,
created_at=Wed Apr 28
Re: [twitter-dev] Re: Upcoming changes to userstream preview
Who is updating earlybird? :-P
Zac Bowling
On Tue, May 4, 2010 at 1:59 PM, Mark McBride mmcbr...@twitter.com wrote:
The hydrated social events (as described in the previous email) are
now live. Please let me know if you have questions/issues/concerns
with the new data
---Mark
http://twitter.com/mccv
On Mon, May 3, 2010 at 10:50 AM, Mark McBride mmcbr...@twitter.com
wrote:
Userstream previewers:
Coming soon there will be a number of changes that may impact
applications.
The first is support for OAuth 1.0a. When rolled out, you will be
able to sign requests to all streaming API endpoints on
betastream.twitter.com. This means that you can use OAuth with both
user streams and other streaming calls (filter, sample, etc.) To
obtain access tokens use the regular twitter.com OAuth flow, then sign
requests to betastream.twitter.com. If you already have an access
token you should be able to use it with the streaming API.
The second is inclusion of fully hydrated objects for the social
events. Instead of just getting a source id, target id, and target
object id you will get the full user object in source and target
fields, and the full status in the target object field (if
applicable). You will also get a created_at field that indicates
the time the social event was created. This should dramatically reduce
the number of REST API calls needed to build a client. Note that most
parsers shouldn't need to change -- the ID field will still be set,
you will just have more fields available. The format is the same as
statuses retrieved via the rest API, with following exceptions:
1) The user's latest status may not be included
2) The user's status count may not be included
3) The user's favorites count may not be included
An example of a hydrated social event is
{created_at=Mon May 03 17:42:55 + 2010,
target_object=
{coordinates=nil,
truncated=false,
created_at=Sun Jun 28 23:10:35 + 2009,
favorited=false,
contributors=nil,
text=looking at cricket eyes!,
id=4,
geo=nil,
in_reply_to_user_id=nil,
source=web,
place=nil,
user=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
in_reply_to_screen_name=nil,
in_reply_to_status_id=nil},
event=favorite,
target=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
source=
{profile_background_tile=false,
name=Jack,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=San Francisco,
created_at=Wed Apr 28 00:00:00 + 2010,
profile_image_url=
http://s3.amazonaws.com/twitter_development/profile_images/2/jack_normal.jpg
,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=0,
id=3,
utc_offset=-28800,
profile_text_color=00,
protected=true,
lang=en,
followers_count=2,
notifications=nil,
verified=false,
description=love, love,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Pacific Time (US Canada),
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=2,
screen_name=jack,
following=nil}}
The third is an improvement to the direct message payload. Currently
it's a bit of a pain to disambiguate statuses and DMs. We'll be
wrapping direct messages in a higher level direct_message object,
e.g.
{direct_message=
[twitter-dev] search.twitter.com and hashtags
To whom that care. I am working on a twitter based application, and seem to run into some trouble with search.twitter.com Twitter search API's. In particular, neither search.twitter.com, nor the search API: http://search.twitter.com/search?q= returns all the posts made under some particular hashtags. For these hashtags, it returns some of the recent posts and for the remaining posts(that it should have, but didn't return), it says that they are temporarily unavailable. This (temporary unavailability) has been a problem for over two weeks now. I wanted to know if others have also suffered this problem, and if so, did they get it fixed or found an alternative route. Best, Shek
Re: [twitter-dev] Re: Upcoming changes to userstream preview
I can hack that together.
---Mark
http://twitter.com/mccv
On Tue, May 4, 2010 at 3:54 PM, Zac Bowling zbowl...@gmail.com wrote:
Who is updating earlybird? :-P
Zac Bowling
On Tue, May 4, 2010 at 1:59 PM, Mark McBride mmcbr...@twitter.com wrote:
The hydrated social events (as described in the previous email) are
now live. Please let me know if you have questions/issues/concerns
with the new data
---Mark
http://twitter.com/mccv
On Mon, May 3, 2010 at 10:50 AM, Mark McBride mmcbr...@twitter.com
wrote:
Userstream previewers:
Coming soon there will be a number of changes that may impact
applications.
The first is support for OAuth 1.0a. When rolled out, you will be
able to sign requests to all streaming API endpoints on
betastream.twitter.com. This means that you can use OAuth with both
user streams and other streaming calls (filter, sample, etc.) To
obtain access tokens use the regular twitter.com OAuth flow, then sign
requests to betastream.twitter.com. If you already have an access
token you should be able to use it with the streaming API.
The second is inclusion of fully hydrated objects for the social
events. Instead of just getting a source id, target id, and target
object id you will get the full user object in source and target
fields, and the full status in the target object field (if
applicable). You will also get a created_at field that indicates
the time the social event was created. This should dramatically reduce
the number of REST API calls needed to build a client. Note that most
parsers shouldn't need to change -- the ID field will still be set,
you will just have more fields available. The format is the same as
statuses retrieved via the rest API, with following exceptions:
1) The user's latest status may not be included
2) The user's status count may not be included
3) The user's favorites count may not be included
An example of a hydrated social event is
{created_at=Mon May 03 17:42:55 + 2010,
target_object=
{coordinates=nil,
truncated=false,
created_at=Sun Jun 28 23:10:35 + 2009,
favorited=false,
contributors=nil,
text=looking at cricket eyes!,
id=4,
geo=nil,
in_reply_to_user_id=nil,
source=web,
place=nil,
user=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
in_reply_to_screen_name=nil,
in_reply_to_status_id=nil},
event=favorite,
target=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
source=
{profile_background_tile=false,
name=Jack,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=San Francisco,
created_at=Wed Apr 28 00:00:00 + 2010,
profile_image_url=
http://s3.amazonaws.com/twitter_development/profile_images/2/jack_normal.jpg;,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=0,
id=3,
utc_offset=-28800,
profile_text_color=00,
protected=true,
lang=en,
followers_count=2,
notifications=nil,
verified=false,
description=love, love,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Pacific Time (US Canada),
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=2,
screen_name=jack,
following=nil}}
The third is an improvement to the direct message payload. Currently
it's a bit of a pain to disambiguate
Re: [twitter-dev] Re: Upcoming changes to userstream preview
I was going to tackle it if no body else did :-)
Already started working on a fork my self:
http://github.com/zbowling/earlybird
Zac Bowling
On Tue, May 4, 2010 at 4:01 PM, Mark McBride mmcbr...@twitter.com wrote:
I can hack that together.
---Mark
http://twitter.com/mccv
On Tue, May 4, 2010 at 3:54 PM, Zac Bowling zbowl...@gmail.com wrote:
Who is updating earlybird? :-P
Zac Bowling
On Tue, May 4, 2010 at 1:59 PM, Mark McBride mmcbr...@twitter.com
wrote:
The hydrated social events (as described in the previous email) are
now live. Please let me know if you have questions/issues/concerns
with the new data
---Mark
http://twitter.com/mccv
On Mon, May 3, 2010 at 10:50 AM, Mark McBride mmcbr...@twitter.com
wrote:
Userstream previewers:
Coming soon there will be a number of changes that may impact
applications.
The first is support for OAuth 1.0a. When rolled out, you will be
able to sign requests to all streaming API endpoints on
betastream.twitter.com. This means that you can use OAuth with both
user streams and other streaming calls (filter, sample, etc.) To
obtain access tokens use the regular twitter.com OAuth flow, then
sign
requests to betastream.twitter.com. If you already have an access
token you should be able to use it with the streaming API.
The second is inclusion of fully hydrated objects for the social
events. Instead of just getting a source id, target id, and target
object id you will get the full user object in source and target
fields, and the full status in the target object field (if
applicable). You will also get a created_at field that indicates
the time the social event was created. This should dramatically reduce
the number of REST API calls needed to build a client. Note that most
parsers shouldn't need to change -- the ID field will still be set,
you will just have more fields available. The format is the same as
statuses retrieved via the rest API, with following exceptions:
1) The user's latest status may not be included
2) The user's status count may not be included
3) The user's favorites count may not be included
An example of a hydrated social event is
{created_at=Mon May 03 17:42:55 + 2010,
target_object=
{coordinates=nil,
truncated=false,
created_at=Sun Jun 28 23:10:35 + 2009,
favorited=false,
contributors=nil,
text=looking at cricket eyes!,
id=4,
geo=nil,
in_reply_to_user_id=nil,
source=web,
place=nil,
user=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
in_reply_to_screen_name=nil,
in_reply_to_status_id=nil},
event=favorite,
target=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
source=
{profile_background_tile=false,
name=Jack,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=San Francisco,
created_at=Wed Apr 28 00:00:00 + 2010,
profile_image_url=
http://s3.amazonaws.com/twitter_development/profile_images/2/jack_normal.jpg
,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=0,
id=3,
utc_offset=-28800,
profile_text_color=00,
protected=true,
lang=en,
followers_count=2,
notifications=nil,
verified=false,
description=love,
Re: [twitter-dev] Re: Upcoming changes to userstream preview
Then by all means, hack away!
---Mark
http://twitter.com/mccv
On Tue, May 4, 2010 at 4:05 PM, Zac Bowling zbowl...@gmail.com wrote:
I was going to tackle it if no body else did :-)
Already started working on a fork my self:
http://github.com/zbowling/earlybird
Zac Bowling
On Tue, May 4, 2010 at 4:01 PM, Mark McBride mmcbr...@twitter.com wrote:
I can hack that together.
---Mark
http://twitter.com/mccv
On Tue, May 4, 2010 at 3:54 PM, Zac Bowling zbowl...@gmail.com wrote:
Who is updating earlybird? :-P
Zac Bowling
On Tue, May 4, 2010 at 1:59 PM, Mark McBride mmcbr...@twitter.com
wrote:
The hydrated social events (as described in the previous email) are
now live. Please let me know if you have questions/issues/concerns
with the new data
---Mark
http://twitter.com/mccv
On Mon, May 3, 2010 at 10:50 AM, Mark McBride mmcbr...@twitter.com
wrote:
Userstream previewers:
Coming soon there will be a number of changes that may impact
applications.
The first is support for OAuth 1.0a. When rolled out, you will be
able to sign requests to all streaming API endpoints on
betastream.twitter.com. This means that you can use OAuth with both
user streams and other streaming calls (filter, sample, etc.) To
obtain access tokens use the regular twitter.com OAuth flow, then
sign
requests to betastream.twitter.com. If you already have an access
token you should be able to use it with the streaming API.
The second is inclusion of fully hydrated objects for the social
events. Instead of just getting a source id, target id, and target
object id you will get the full user object in source and target
fields, and the full status in the target object field (if
applicable). You will also get a created_at field that indicates
the time the social event was created. This should dramatically
reduce
the number of REST API calls needed to build a client. Note that
most
parsers shouldn't need to change -- the ID field will still be set,
you will just have more fields available. The format is the same as
statuses retrieved via the rest API, with following exceptions:
1) The user's latest status may not be included
2) The user's status count may not be included
3) The user's favorites count may not be included
An example of a hydrated social event is
{created_at=Mon May 03 17:42:55 + 2010,
target_object=
{coordinates=nil,
truncated=false,
created_at=Sun Jun 28 23:10:35 + 2009,
favorited=false,
contributors=nil,
text=looking at cricket eyes!,
id=4,
geo=nil,
in_reply_to_user_id=nil,
source=web,
place=nil,
user=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
in_reply_to_screen_name=nil,
in_reply_to_status_id=nil},
event=favorite,
target=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
source=
{profile_background_tile=false,
name=Jack,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=San Francisco,
created_at=Wed Apr 28 00:00:00 + 2010,
profile_image_url=
http://s3.amazonaws.com/twitter_development/profile_images/2/jack_normal.jpg;,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=0,
id=3,
utc_offset=-28800,
[twitter-dev] Blackbird Pie
http://media.twitter.com/blackbird-pie/ Can you guys add a meta data element to a tweet, which will provide a blackbird pie hyperlink for a tweet. Basically, the code behind the link should generate the code block that Blackbird Pie currently generates. That way one can include a Blackbird Pie tweet in an iframe, with the iframe source link coming from the blackbird pie hyperlink in the tweet meta data. Just a thought.
