[twitter-dev] response schema of trends/location
Hi, Quick question: Is there any chance that the trends/location method returns multiple locations (which woeid is different from the specified woeid) in the response? Thans, Yusuke
[twitter-dev] Re: Deprecating /statuses/public_timeline resource on 4/5/10
Just to throw my 2 cents in. Without a reasonable replacement for mobile devices, we'll likely remove it, and I'm expecting a substantial backlash from UberTwitter users. It does look like it would be relatively simple to roll-your own with the streaming api, which makes me wonder why this is being removed. I don't have metrics on how many of my users access this endpoint, but I can say that in the past year when there were issues with it, we would get plenty of feedback. People like to use it to randomly find interesting people. If sounds like the twitter folks are re-considering, I hope so. -Paul On Mar 5, 10:39 pm, Raffi Krikorian ra...@twitter.com wrote: hi all. i just wanted to let you know that we've heard all the issues around this deprecation and potential removal of public_statuses -- we're currently reviewing and thinking this over and will have more to say next week. thanks for your patience. fixed. BTW, it doesn't look like the docs on the apiwiki have been updated with the deprecation notice. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi
Re: [twitter-dev] response schema of trends/location
not currently, however, the schema is laid out so that we have that ability at a later date (think, hierarchically, you may ask for all the trends in california, and we return the trends in los angeles, san francisco, san diego, etc.). On Sun, Mar 7, 2010 at 8:40 AM, Yusuke yus...@mac.com wrote: Hi, Quick question: Is there any chance that the trends/location method returns multiple locations (which woeid is different from the specified woeid) in the response? Thans, Yusuke -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] web application launch...Tweetmasher
http://tweetmasher.com/ At the moment mostly 3d window dressing on the Twitter search api...but slowly adding new features.
[twitter-dev] Re: web application launch...Tweetmasher
Looks nice - font is a little small but other than that, it looks great! When do location-based searches show up on your road map? On Mar 7, 11:09 am, eco_bach bac...@gmail.com wrote: http://tweetmasher.com/ At the moment mostly 3d window dressing on the Twitter search api...but slowly adding new features.
[twitter-dev] Pin-based authorization via .NET
I'm working on version 2 of Twitterizer, a .NET library for using the Twitter API, but I've run into a weird issue with pin-based OAuth. I have a sample web application and a sample desktop application. From the web application I am able to perform pin-based authentication without any issues, but through the desktop application every call for access tokens are refused with Invalid oauth_verifier parameter. I've stepped through the code (non-stop for an hour) and I'm sure that the exact code is executing for each call. I've tried changing the calls to GET, instead of POST, and the results are the same. From the web app it works great, from the desktop app, not so much. Using fiddler, I've captured the HTTP request/response from each, and they look exactly the same (to me). Here is the call from the web application (works): POST http://twitter.com/oauth/access_token?oauth_verifier=2068385 HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm=Twitter API,oauth_consumer_key=Ds8w95QVNTITV16pqMwtHA,oauth_nonce=6E723378,oauth_signature_method=HMAC- SHA1,oauth_timestamp=1267995036,oauth_token=Vy5cCHkomrAKocY9c8J18hAEf1PJ2ONwBtQxmdGGaI,oauth_version=1.0,oauth_signature=OU3Qfi2tq %2Fwyaij0NezCARqLVCA%3D User-Agent: Twitterizer/2.0.0.0 Host: twitter.com And here is the call from the desktop application (does not work): POST http://twitter.com/oauth/access_token?oauth_verifier=541907 HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm=Twitter API,oauth_consumer_key=Ds8w95QVNTITV16pqMwtHA,oauth_nonce=7F8D82E3,oauth_signature_method=HMAC- SHA1,oauth_timestamp=1267995086,oauth_token=uTcERUybyJF0WKi77w5dPCTZbwO7DZJX1hQuJK0fg,oauth_version=1.0,oauth_signature=iUUcdVtM %2B4nxfDKrqPqElE9IPgY%3D User-Agent: Twitterizer/2.0.0.0 Host: twitter.com The response body is: ?xml version=1.0 encoding=UTF-8? hash request/oauth/access_token?oauth_verifier=541907/request errorInvalid oauth_verifier parameter/error /hash This may be more of a .NET question, as there may be some kind of nuance when making requests through a windows application, but I thought it might be worth my time to ask everyone, in case I'm doing something dumb (it happens). Thanks for your time, Ricky www.twitterizer.net
Re: [twitter-dev] Pin-based authorization via .NET
Why are you using PIN based authorization for web applications? Web applications don't use PINs. Ryan Sent from my DROID On Mar 7, 2010 4:59 PM, Ricky ri...@digitally-born.com wrote: I'm working on version 2 of Twitterizer, a .NET library for using the Twitter API, but I've run into a weird issue with pin-based OAuth. I have a sample web application and a sample desktop application. From the web application I am able to perform pin-based authentication without any issues, but through the desktop application every call for access tokens are refused with Invalid oauth_verifier parameter. I've stepped through the code (non-stop for an hour) and I'm sure that the exact code is executing for each call. I've tried changing the calls to GET, instead of POST, and the results are the same. From the web app it works great, from the desktop app, not so much. Using fiddler, I've captured the HTTP request/response from each, and they look exactly the same (to me). Here is the call from the web application (works): POST http://twitter.com/oauth/access_token?oauth_verifier=2068385 HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm=Twitter API,oauth_consumer_key=Ds8w95QVNTITV16pqMwtHA,oauth_nonce=6E723378,oauth_signature_method=HMAC- SHA1,oauth_timestamp=1267995036,oauth_token=Vy5cCHkomrAKocY9c8J18hAEf1PJ2ONwBtQxmdGGaI,oauth_version=1.0,oauth_signature=OU3Qfi2tq %2Fwyaij0NezCARqLVCA%3D User-Agent: Twitterizer/2.0.0.0 Host: twitter.com And here is the call from the desktop application (does not work): POST http://twitter.com/oauth/access_token?oauth_verifier=541907 HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm=Twitter API,oauth_consumer_key=Ds8w95QVNTITV16pqMwtHA,oauth_nonce=7F8D82E3,oauth_signature_method=HMAC- SHA1,oauth_timestamp=1267995086,oauth_token=uTcERUybyJF0WKi77w5dPCTZbwO7DZJX1hQuJK0fg,oauth_version=1.0,oauth_signature=iUUcdVtM %2B4nxfDKrqPqElE9IPgY%3D User-Agent: Twitterizer/2.0.0.0 Host: twitter.com The response body is: ?xml version=1.0 encoding=UTF-8? hash request/oauth/access_token?oauth_verifier=541907/request errorInvalid oauth_verifier parameter/error /hash This may be more of a .NET question, as there may be some kind of nuance when making requests through a windows application, but I thought it might be worth my time to ask everyone, in case I'm doing something dumb (it happens). Thanks for your time, Ricky www.twitterizer.net
Re: [twitter-dev] Pin-based authorization via .NET
You are missing a digit from the desktop PIN. It should always be 7 digits. Abraham On Sun, Mar 7, 2010 at 12:57, Ricky ri...@digitally-born.com wrote: I'm working on version 2 of Twitterizer, a .NET library for using the Twitter API, but I've run into a weird issue with pin-based OAuth. I have a sample web application and a sample desktop application. From the web application I am able to perform pin-based authentication without any issues, but through the desktop application every call for access tokens are refused with Invalid oauth_verifier parameter. I've stepped through the code (non-stop for an hour) and I'm sure that the exact code is executing for each call. I've tried changing the calls to GET, instead of POST, and the results are the same. From the web app it works great, from the desktop app, not so much. Using fiddler, I've captured the HTTP request/response from each, and they look exactly the same (to me). Here is the call from the web application (works): POST http://twitter.com/oauth/access_token?oauth_verifier=2068385 HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm=Twitter API,oauth_consumer_key=Ds8w95QVNTITV16pqMwtHA,oauth_nonce=6E723378,oauth_signature_method=HMAC- SHA1,oauth_timestamp=1267995036,oauth_token=Vy5cCHkomrAKocY9c8J18hAEf1PJ2ONwBtQxmdGGaI,oauth_version=1.0,oauth_signature=OU3Qfi2tq %2Fwyaij0NezCARqLVCA%3D User-Agent: Twitterizer/2.0.0.0 Host: twitter.com And here is the call from the desktop application (does not work): POST http://twitter.com/oauth/access_token?oauth_verifier=541907 HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm=Twitter API,oauth_consumer_key=Ds8w95QVNTITV16pqMwtHA,oauth_nonce=7F8D82E3,oauth_signature_method=HMAC- SHA1,oauth_timestamp=1267995086,oauth_token=uTcERUybyJF0WKi77w5dPCTZbwO7DZJX1hQuJK0fg,oauth_version=1.0,oauth_signature=iUUcdVtM %2B4nxfDKrqPqElE9IPgY%3D User-Agent: Twitterizer/2.0.0.0 Host: twitter.com The response body is: ?xml version=1.0 encoding=UTF-8? hash request/oauth/access_token?oauth_verifier=541907/request errorInvalid oauth_verifier parameter/error /hash This may be more of a .NET question, as there may be some kind of nuance when making requests through a windows application, but I thought it might be worth my time to ask everyone, in case I'm doing something dumb (it happens). Thanks for your time, Ricky www.twitterizer.net -- Abraham Williams | Community Advocate | http://abrah.am TwitterOAuth | http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: Pin-based authorization via .NET
I'm developing a library that can be used with either web or desktop. Since I had code already going in a web application, I use it to do my initial development. Ricky On Mar 7, 5:03 pm, Ryan Alford ryanalford...@gmail.com wrote: Why are you using PIN based authorization for web applications? Web applications don't use PINs. Ryan Sent from my DROID On Mar 7, 2010 4:59 PM, Ricky ri...@digitally-born.com wrote: I'm working on version 2 of Twitterizer, a .NET library for using the Twitter API, but I've run into a weird issue with pin-based OAuth. I have a sample web application and a sample desktop application. From the web application I am able to perform pin-based authentication without any issues, but through the desktop application every call for access tokens are refused with Invalid oauth_verifier parameter. I've stepped through the code (non-stop for an hour) and I'm sure that the exact code is executing for each call. I've tried changing the calls to GET, instead of POST, and the results are the same. From the web app it works great, from the desktop app, not so much. Using fiddler, I've captured the HTTP request/response from each, and they look exactly the same (to me). Here is the call from the web application (works): POSThttp://twitter.com/oauth/access_token?oauth_verifier=2068385HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm=Twitter API,oauth_consumer_key=Ds8w95QVNTITV16pqMwtHA,oauth_nonce=6E723378,oau th_signature_method=HMAC- SHA1,oauth_timestamp=1267995036,oauth_token=Vy5cCHkomrAKocY9c8J18hAEf1P J2ONwBtQxmdGGaI,oauth_version=1.0,oauth_signature=OU3Qfi2tq %2Fwyaij0NezCARqLVCA%3D User-Agent: Twitterizer/2.0.0.0 Host: twitter.com And here is the call from the desktop application (does not work): POSThttp://twitter.com/oauth/access_token?oauth_verifier=541907HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm=Twitter API,oauth_consumer_key=Ds8w95QVNTITV16pqMwtHA,oauth_nonce=7F8D82E3,oau th_signature_method=HMAC- SHA1,oauth_timestamp=1267995086,oauth_token=uTcERUybyJF0WKi77w5dPCTZbwO 7DZJX1hQuJK0fg,oauth_version=1.0,oauth_signature=iUUcdVtM %2B4nxfDKrqPqElE9IPgY%3D User-Agent: Twitterizer/2.0.0.0 Host: twitter.com The response body is: ?xml version=1.0 encoding=UTF-8? hash request/oauth/access_token?oauth_verifier=541907/request errorInvalid oauth_verifier parameter/error /hash This may be more of a .NET question, as there may be some kind of nuance when making requests through a windows application, but I thought it might be worth my time to ask everyone, in case I'm doing something dumb (it happens). Thanks for your time, Rickywww.twitterizer.net
[twitter-dev] Re: Pin-based authorization via .NET
I thought the same thing, but Twitter has absolutely given me 6 digit pins. Ricky On Mar 7, 5:07 pm, Abraham Williams 4bra...@gmail.com wrote: You are missing a digit from the desktop PIN. It should always be 7 digits. Abraham On Sun, Mar 7, 2010 at 12:57, Ricky ri...@digitally-born.com wrote: I'm working on version 2 of Twitterizer, a .NET library for using the Twitter API, but I've run into a weird issue with pin-based OAuth. I have a sample web application and a sample desktop application. From the web application I am able to perform pin-based authentication without any issues, but through the desktop application every call for access tokens are refused with Invalid oauth_verifier parameter. I've stepped through the code (non-stop for an hour) and I'm sure that the exact code is executing for each call. I've tried changing the calls to GET, instead of POST, and the results are the same. From the web app it works great, from the desktop app, not so much. Using fiddler, I've captured the HTTP request/response from each, and they look exactly the same (to me). Here is the call from the web application (works): POSThttp://twitter.com/oauth/access_token?oauth_verifier=2068385HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm=Twitter API,oauth_consumer_key=Ds8w95QVNTITV16pqMwtHA,oauth_nonce=6E723378,oau th_signature_method=HMAC- SHA1,oauth_timestamp=1267995036,oauth_token=Vy5cCHkomrAKocY9c8J18hAEf1P J2ONwBtQxmdGGaI,oauth_version=1.0,oauth_signature=OU3Qfi2tq %2Fwyaij0NezCARqLVCA%3D User-Agent: Twitterizer/2.0.0.0 Host: twitter.com And here is the call from the desktop application (does not work): POSThttp://twitter.com/oauth/access_token?oauth_verifier=541907HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm=Twitter API,oauth_consumer_key=Ds8w95QVNTITV16pqMwtHA,oauth_nonce=7F8D82E3,oau th_signature_method=HMAC- SHA1,oauth_timestamp=1267995086,oauth_token=uTcERUybyJF0WKi77w5dPCTZbwO 7DZJX1hQuJK0fg,oauth_version=1.0,oauth_signature=iUUcdVtM %2B4nxfDKrqPqElE9IPgY%3D User-Agent: Twitterizer/2.0.0.0 Host: twitter.com The response body is: ?xml version=1.0 encoding=UTF-8? hash request/oauth/access_token?oauth_verifier=541907/request errorInvalid oauth_verifier parameter/error /hash This may be more of a .NET question, as there may be some kind of nuance when making requests through a windows application, but I thought it might be worth my time to ask everyone, in case I'm doing something dumb (it happens). Thanks for your time, Ricky www.twitterizer.net -- Abraham Williams | Community Advocate |http://abrah.am TwitterOAuth |http://github.com/abraham/twitteroauth This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] Re: Pin-based authorization via .NET
Actually, ignore me. You were totally right. I accidentally limited the text box in the desktop app to 6 chars, so it was truncating them. I need a nap. Thanks, Ricky On Mar 7, 5:07 pm, Abraham Williams 4bra...@gmail.com wrote: You are missing a digit from the desktop PIN. It should always be 7 digits. Abraham On Sun, Mar 7, 2010 at 12:57, Ricky ri...@digitally-born.com wrote: I'm working on version 2 of Twitterizer, a .NET library for using the Twitter API, but I've run into a weird issue with pin-based OAuth. I have a sample web application and a sample desktop application. From the web application I am able to perform pin-based authentication without any issues, but through the desktop application every call for access tokens are refused with Invalid oauth_verifier parameter. I've stepped through the code (non-stop for an hour) and I'm sure that the exact code is executing for each call. I've tried changing the calls to GET, instead of POST, and the results are the same. From the web app it works great, from the desktop app, not so much. Using fiddler, I've captured the HTTP request/response from each, and they look exactly the same (to me). Here is the call from the web application (works): POSThttp://twitter.com/oauth/access_token?oauth_verifier=2068385HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm=Twitter API,oauth_consumer_key=Ds8w95QVNTITV16pqMwtHA,oauth_nonce=6E723378,oau th_signature_method=HMAC- SHA1,oauth_timestamp=1267995036,oauth_token=Vy5cCHkomrAKocY9c8J18hAEf1P J2ONwBtQxmdGGaI,oauth_version=1.0,oauth_signature=OU3Qfi2tq %2Fwyaij0NezCARqLVCA%3D User-Agent: Twitterizer/2.0.0.0 Host: twitter.com And here is the call from the desktop application (does not work): POSThttp://twitter.com/oauth/access_token?oauth_verifier=541907HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm=Twitter API,oauth_consumer_key=Ds8w95QVNTITV16pqMwtHA,oauth_nonce=7F8D82E3,oau th_signature_method=HMAC- SHA1,oauth_timestamp=1267995086,oauth_token=uTcERUybyJF0WKi77w5dPCTZbwO 7DZJX1hQuJK0fg,oauth_version=1.0,oauth_signature=iUUcdVtM %2B4nxfDKrqPqElE9IPgY%3D User-Agent: Twitterizer/2.0.0.0 Host: twitter.com The response body is: ?xml version=1.0 encoding=UTF-8? hash request/oauth/access_token?oauth_verifier=541907/request errorInvalid oauth_verifier parameter/error /hash This may be more of a .NET question, as there may be some kind of nuance when making requests through a windows application, but I thought it might be worth my time to ask everyone, in case I'm doing something dumb (it happens). Thanks for your time, Ricky www.twitterizer.net -- 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: Pin-based authorization via .NET
Take a look at http://twittervb.codeplex.com/ for some examples. John Meyer Freelance Consultant http://www.pueblonative.com/blog If something goes wrong at the plant, blame the guy who can’t speak English. */Homer Simpson/* --- @ WiseStamp Signature http://my.wisestamp.com/link?u=42bgx5rfnpr43zfjsite=www.wisestamp.com/email-install. Get it now http://my.wisestamp.com/link?u=42bgx5rfnpr43zfjsite=www.wisestamp.com/email-install On 3/7/2010 4:19 PM, Ricky wrote: I'm developing a library that can be used with either web or desktop. Since I had code already going in a web application, I use it to do my initial development. Ricky On Mar 7, 5:03 pm, Ryan Alfordryanalford...@gmail.com wrote: Why are you using PIN based authorization for web applications? Web applications don't use PINs. Ryan Sent from my DROID On Mar 7, 2010 4:59 PM, Rickyri...@digitally-born.com wrote: I'm working on version 2 of Twitterizer, a .NET library for using the Twitter API, but I've run into a weird issue with pin-based OAuth. I have a sample web application and a sample desktop application. From the web application I am able to perform pin-based authentication without any issues, but through the desktop application every call for access tokens are refused with Invalid oauth_verifier parameter. I've stepped through the code (non-stop for an hour) and I'm sure that the exact code is executing for each call. I've tried changing the calls to GET, instead of POST, and the results are the same. From the web app it works great, from the desktop app, not so much. Using fiddler, I've captured the HTTP request/response from each, and they look exactly the same (to me). Here is the call from the web application (works): POSThttp://twitter.com/oauth/access_token?oauth_verifier=2068385HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm=Twitter API,oauth_consumer_key=Ds8w95QVNTITV16pqMwtHA,oauth_nonce=6E723378,oau th_signature_method=HMAC- SHA1,oauth_timestamp=1267995036,oauth_token=Vy5cCHkomrAKocY9c8J18hAEf1P J2ONwBtQxmdGGaI,oauth_version=1.0,oauth_signature=OU3Qfi2tq %2Fwyaij0NezCARqLVCA%3D User-Agent: Twitterizer/2.0.0.0 Host: twitter.com And here is the call from the desktop application (does not work): POSThttp://twitter.com/oauth/access_token?oauth_verifier=541907HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm=Twitter API,oauth_consumer_key=Ds8w95QVNTITV16pqMwtHA,oauth_nonce=7F8D82E3,oau th_signature_method=HMAC- SHA1,oauth_timestamp=1267995086,oauth_token=uTcERUybyJF0WKi77w5dPCTZbwO 7DZJX1hQuJK0fg,oauth_version=1.0,oauth_signature=iUUcdVtM %2B4nxfDKrqPqElE9IPgY%3D User-Agent: Twitterizer/2.0.0.0 Host: twitter.com The response body is: ?xml version=1.0 encoding=UTF-8? hash request/oauth/access_token?oauth_verifier=541907/request errorInvalid oauth_verifier parameter/error /hash This may be more of a .NET question, as there may be some kind of nuance when making requests through a windows application, but I thought it might be worth my time to ask everyone, in case I'm doing something dumb (it happens). Thanks for your time, Rickywww.twitterizer.net
[twitter-dev] Re: OAuth newbie question
A lot of people have found my presentation on OAuth useful when trying
to learn the ins and outs of the entire request cycle with an OAuth-
protected API: http://bit.ly/oauth-zero-to-hero
When accessing a protected resource with OAuth, the oauth_token and
oauth_token_secret you receive become your access token. You include
oauth_token as an OAuth parameter in your signature base string and
authorization header, and then sign your entire OAuth request with a
composite signing secret:
{url_escaped(consumer_secret)}{url_escaped(oauth_token_secret)}
Taylor
On Mar 6, 2:55 pm, IDOLpeeps i...@idolpeeps.com wrote:
I've overcome the nuances of generating the oauth signature. It
shocks me that the API documentation provides no clear indication of
how to send the tokens along with an API call. It's not even a PHP-
specific question. Simply put: Where do the oauth_token and
oauth_token_secret get embedded in API call: As posted parameters?
If so, with what parameter names? Can anybody provide guidance? I
have seen many people ask this question, yet see no answer.
As far as why one would want to use their own library vs. somebody
else's, that's a question for the ages. One specific answer is that
many of us have created our own application-specific libraries that
accommodate traditional http authentication and we'd like to keep our
libraries when we add Oauth. To do so, it's best to have an answer to
this question.
Thank you.
Re: [twitter-dev] Re: A PubSubHubbub hub for Twitter
Why doesn't Twitter just open up their API and patent and then the Twitter API becomes the standard? We all change less code that way. :-) I like all these open standards, but it would be so much easier if we could just use the existing APIs as standards that we've already integrated into all our code. I think Twitter's losing out on a huge opportunity here by not opening up their API. Jesse On Tue, Mar 2, 2010 at 8: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 Twitter PubSubHubbub hub if it was available? Yes 33 97% No 1 3% Have you already implemented PubSubHubbub? 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 that PubSubHubbub should 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 working PubSubHubbub subscriber 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 PubSubHubbub vs. 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 via PubSubHubbub 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 the PubSubHubbub protocol. 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] Re: A PubSubHubbub hub for Twitter
uh - how are we not opening up our API? On Sun, Mar 7, 2010 at 6:54 PM, Jesse Stay jesses...@gmail.com wrote: Why doesn't Twitter just open up their API and patent and then the Twitter API becomes the standard? We all change less code that way. :-) I like all these open standards, but it would be so much easier if we could just use the existing APIs as standards that we've already integrated into all our code. I think Twitter's losing out on a huge opportunity here by not opening up their API. Jesse On Tue, Mar 2, 2010 at 8: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 Twitter PubSubHubbub hub if it was available? Yes 33 97% No 1 3% Have you already implemented PubSubHubbub? 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 that PubSubHubbub should 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 working PubSubHubbub subscriber 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 PubSubHubbub vs. 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 via PubSubHubbub 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 the PubSubHubbub protocol. 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. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: Pin-based authorization via .NET
TwitterVB is actually a port of version 1 of Twitterizer. (I'm named in the source :D) Ricky On Mar 7, 6:34 pm, John Meyer john.l.me...@gmail.com wrote: Take a look athttp://twittervb.codeplex.com/for some examples. John Meyer Freelance Consultanthttp://www.pueblonative.com/blog If something goes wrong at the plant, blame the guy who can t speak English. */Homer Simpson/* --- @ WiseStamp Signature http://my.wisestamp.com/link?u=42bgx5rfnpr43zfjsite=www.wisestamp.co Get it now http://my.wisestamp.com/link?u=42bgx5rfnpr43zfjsite=www.wisestamp.co... On 3/7/2010 4:19 PM, Ricky wrote: I'm developing a library that can be used with either web or desktop. Since I had code already going in a web application, I use it to do my initial development. Ricky On Mar 7, 5:03 pm, Ryan Alfordryanalford...@gmail.com wrote: Why are you using PIN based authorization for web applications? Web applications don't use PINs. Ryan Sent from my DROID On Mar 7, 2010 4:59 PM, Rickyri...@digitally-born.com wrote: I'm working on version 2 of Twitterizer, a .NET library for using the Twitter API, but I've run into a weird issue with pin-based OAuth. I have a sample web application and a sample desktop application. From the web application I am able to perform pin-based authentication without any issues, but through the desktop application every call for access tokens are refused with Invalid oauth_verifier parameter. I've stepped through the code (non-stop for an hour) and I'm sure that the exact code is executing for each call. I've tried changing the calls to GET, instead of POST, and the results are the same. From the web app it works great, from the desktop app, not so much. Using fiddler, I've captured the HTTP request/response from each, and they look exactly the same (to me). Here is the call from the web application (works): POSThttp://twitter.com/oauth/access_token?oauth_verifier=2068385HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm=Twitter API,oauth_consumer_key=Ds8w95QVNTITV16pqMwtHA,oauth_nonce=6E723378,oau th_signature_method=HMAC- SHA1,oauth_timestamp=1267995036,oauth_token=Vy5cCHkomrAKocY9c8J18hAEf1P J2ONwBtQxmdGGaI,oauth_version=1.0,oauth_signature=OU3Qfi2tq %2Fwyaij0NezCARqLVCA%3D User-Agent: Twitterizer/2.0.0.0 Host: twitter.com And here is the call from the desktop application (does not work): POSThttp://twitter.com/oauth/access_token?oauth_verifier=541907HTTP/ 1.1 Content-Type: application/x-www-form-urlencoded Authorization: OAuth realm=Twitter API,oauth_consumer_key=Ds8w95QVNTITV16pqMwtHA,oauth_nonce=7F8D82E3,oau th_signature_method=HMAC- SHA1,oauth_timestamp=1267995086,oauth_token=uTcERUybyJF0WKi77w5dPCTZbwO 7DZJX1hQuJK0fg,oauth_version=1.0,oauth_signature=iUUcdVtM %2B4nxfDKrqPqElE9IPgY%3D User-Agent: Twitterizer/2.0.0.0 Host: twitter.com The response body is: ?xml version=1.0 encoding=UTF-8? hash request/oauth/access_token?oauth_verifier=541907/request errorInvalid oauth_verifier parameter/error /hash This may be more of a .NET question, as there may be some kind of nuance when making requests through a windows application, but I thought it might be worth my time to ask everyone, in case I'm doing something dumb (it happens). Thanks for your time, Rickywww.twitterizer.net
[twitter-dev] Re: Need help with the streaming API syntax....specifically how to point to the track text file without using curl
It turns out you were right with this and John was right with the POST. Thanks to all who replied. As soon as I changed (request.readuntilend()) to (request.readline()) the data started flowing in. I don't want to muddy the water on this thread but I will by asking the next predictable problem. If I have query string that is ? track=peter,paul,mary, etc for 1000 terms..won't that exceed some http limit on length? How does one track about 1000 terms on a single stream connection? even if there is a method called request.query(track=peter,paul,mary,etc) isn't that just a substitute for putting it on the actual URL thus still exceding some length limit? Thanks, peter On Mar 5, 4:38 pm, Mark McBride mmcbr...@twitter.com wrote: I think this is slightly backwards. You want to use the GET method, but set up the URI you have (with the track=Microsoft parameter). You will also need to authenticate. Note that this is a streaming API. I don't know VB all that well, but there's a reasonable chance that this call only returns data when the HTTP call has finished. The streaming API will *never* finish, so you'll need to parse data as it's available. Without looking at VB doc I have no idea how you would set that up. ---Mark http://twitter.com/mccv On Fri, Mar 5, 2010 at 9:54 AM, Mad Euchre mad.ukrain...@gmail.com wrote: Thanks. Now I'm using the post method. How should I use the track parameter? Something like this? address = New Uri(http://stream.twitter.com/1/statuses/filter.json? track=Microsoft) I'm getting connected but no data that matches Microsoft is streaming over.No data for that matter. I'm passing my name and pw in the request.credentials method. The server returned a 200 OK when I added the credentials but not when it was in the URL alone. ie; address = New Uri(http://stream.twitter.com/1/statuses/ filter.json?track=Microsoft - name:pw Thanks, Peter On Mar 2, 5:19 pm, John Kalucki j...@twitter.com wrote: The text file approach only applies to POST parameters set from the curl command, and in no other case. When creating an HTTP client from within a program, you should be able to configure the POST parameters via method calls. If you can't, it's a pretty worthless HTTP library. Each client library is different, check your docs. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, Mar 2, 2010 at 12:42 PM, Mad Euchre mad.ukrain...@gmail.com wrote: This is the VB code I would use to start any http stream request = DirectCast(WebRequest.Create(http:// stream.twitter.com/1/statuses/filter.json - name:pw), HttpWebRequest) request.Credentials = New NetworkCredential(name, pw) ' Get response response = DirectCast(request.GetResponse(), HttpWebResponse) ' Get the response stream into a reader reader = New StreamReader(response.GetResponseStream()) The streaming api documentation says to create a file called track.txt and add text similar to this without the quotes. track=peter, paul, mary Then use curl @track.txthttp:// stream.twitter.com/1/statuses/filter.json - name:pw I can't believe I have to shell out to DOS and run the curl command line. My direct question is how do others incorportate the @track.txt in the VB.Net web request? Maybe something like this? http://stream.twitter.com/1/statuses/filter.json-name:pw? track.txt Thanks- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text -
[twitter-dev] Re: web application launch...Tweetmasher
Nice site. I can profile it on http://twi5.com , need few more details such as your twitter handle -Nischal On Mar 8, 12:09 am, eco_bach bac...@gmail.com wrote: http://tweetmasher.com/ At the moment mostly 3d window dressing on the Twitter search api...but slowly adding new features.
Re: [twitter-dev] Re: Need help with the streaming API syntax....specifically how to point to the track text file without using curl
There is indeed a hard limit to the length of URLs. POST parameters, however, can be quite large. We have many clients that send parameters with hundreds of thousands to millions of terms, so this is broadly possible., Your HTTP client may or many not support this scale. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Sun, Mar 7, 2010 at 5:57 PM, Mad Euchre mad.ukrain...@gmail.com wrote: It turns out you were right with this and John was right with the POST. Thanks to all who replied. As soon as I changed (request.readuntilend()) to (request.readline()) the data started flowing in. I don't want to muddy the water on this thread but I will by asking the next predictable problem. If I have query string that is ? track=peter,paul,mary, etc for 1000 terms..won't that exceed some http limit on length? How does one track about 1000 terms on a single stream connection? even if there is a method called request.query(track=peter,paul,mary,etc) isn't that just a substitute for putting it on the actual URL thus still exceding some length limit? Thanks, peter On Mar 5, 4:38 pm, Mark McBride mmcbr...@twitter.com wrote: I think this is slightly backwards. You want to use the GET method, but set up the URI you have (with the track=Microsoft parameter). You will also need to authenticate. Note that this is a streaming API. I don't know VB all that well, but there's a reasonable chance that this call only returns data when the HTTP call has finished. The streaming API will *never* finish, so you'll need to parse data as it's available. Without looking at VB doc I have no idea how you would set that up. ---Mark http://twitter.com/mccv On Fri, Mar 5, 2010 at 9:54 AM, Mad Euchre mad.ukrain...@gmail.com wrote: Thanks. Now I'm using the post method. How should I use the track parameter? Something like this? address = New Uri(http://stream.twitter.com/1/statuses/filter.json? track=Microsoft) I'm getting connected but no data that matches Microsoft is streaming over.No data for that matter. I'm passing my name and pw in the request.credentials method. The server returned a 200 OK when I added the credentials but not when it was in the URL alone. ie; address = New Uri(http://stream.twitter.com/1/statuses/ filter.json?track=Microsoft - name:pw Thanks, Peter On Mar 2, 5:19 pm, John Kalucki j...@twitter.com wrote: The text file approach only applies to POST parameters set from the curl command, and in no other case. When creating an HTTP client from within a program, you should be able to configure the POST parameters via method calls. If you can't, it's a pretty worthless HTTP library. Each client library is different, check your docs. -John Kaluckihttp://twitter.com/jkalucki Infrastructure, Twitter Inc. On Tue, Mar 2, 2010 at 12:42 PM, Mad Euchre mad.ukrain...@gmail.com wrote: This is the VB code I would use to start any http stream request = DirectCast(WebRequest.Create(http:// stream.twitter.com/1/statuses/filter.json - name:pw), HttpWebRequest) request.Credentials = New NetworkCredential(name, pw) ' Get response response = DirectCast(request.GetResponse(), HttpWebResponse) ' Get the response stream into a reader reader = New StreamReader(response.GetResponseStream()) The streaming api documentation says to create a file called track.txt and add text similar to this without the quotes. track=peter, paul, mary Then use curl @track.txthttp:// stream.twitter.com/1/statuses/filter.json - name:pw I can't believe I have to shell out to DOS and run the curl command line. My direct question is how do others incorportate the @track.txt in the VB.Net web request? Maybe something like this? http://stream.twitter.com/1/statuses/filter.json-name:pw? track.txt Thanks- Hide quoted text - - Show quoted text -- Hide quoted text - - Show quoted text -
Re: [twitter-dev] Re: A PubSubHubbub hub for Twitter
Raffi, it is not clear the legalities of duplicating the Twitter API in other environments. For instance, if I wanted to run users/show_user on Wordpress.com's API and get data in exactly the same format as Twitter returns data for that, along with any other method Twitter provides, is that legal? Is Status.net's duplication of the Twitter API legal? It is not clear in the Terms. It is not open unless Twitter allows this, at least according to the Open Web Foundation (if I understand correctly). I think DeWitt Clinton has brought this up before, and IMO, this would be an even more ideal situation than Pubsubhubbub support, as we wouldn't have to change our code to do this elsewhere. It would make the Twitter API format itself a standard. Make sense? Jesse On Sun, Mar 7, 2010 at 8:00 PM, Raffi Krikorian ra...@twitter.com wrote: uh - how are we not opening up our API? On Sun, Mar 7, 2010 at 6:54 PM, Jesse Stay jesses...@gmail.com wrote: Why doesn't Twitter just open up their API and patent and then the Twitter API becomes the standard? We all change less code that way. :-) I like all these open standards, but it would be so much easier if we could just use the existing APIs as standards that we've already integrated into all our code. I think Twitter's losing out on a huge opportunity here by not opening up their API. Jesse On Tue, Mar 2, 2010 at 8:57 AM, Julien julien.genest...@gmail.comwrote: 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 Twitter PubSubHubbub hub if it was available? Yes 33 97% No 1 3% Have you already implemented PubSubHubbub? 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 that PubSubHubbub should 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 working PubSubHubbub subscriber 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 PubSubHubbub vs. 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 via PubSubHubbub 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 the PubSubHubbub protocol. 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. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
