[twitter-dev] [SiteStreams] can't follow more than one user
Hi @all! Not sure if I'm posting to the correct list, but here it goes. I'm currently trying to migrate a website service that uses UserStreams to SiteStreams, as the documentation tells me to do. However I'm finding a difficult problem that I've been able to reproduce: If I try to follow 1 user_id, it works ok. If I try to follow 2 or more, SiteStreams always answers 401 Unauthorized. Example: (Host: betastream.twitter.com) - this works GET /2b/site.json?with=followingsfollow=11528912 HTTP/1.1 - this works too GET /2b/site.json?with=followingsfollow=9512582 HTTP/1.1 - this always returns 401 UNAUTHORIZED GET /2b/site.json?with=followingsfollow=11528912,9512582 HTTP/1.1 Any thing I'm missing here? Thank you! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: [SiteStreams] can't follow more than one user
Hi Thomas On Oct 6, 5:20 pm, Thomas Mango tsma...@gmail.com wrote: Hey, Ruben. That's the correct URL format. Are you sure your account was approved for Site Stream access? Yes it is, I filled all forms and received confirmation on monday. Maybe I'm wrong, but the fact that it works with only one person to follow proves that I have access to SiteStreams. Anyways my username is 'rubenfonseca' (no quotes). I'm using an OAuth token from that user on my application. Thank you! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: [SiteStreams] can't follow more than one user
Hi John! On Oct 6, 5:54 pm, John Kalucki j...@twitter.com wrote: It might be an OAuth encoding error with the ','. Which OAuth library are you using? That was exactly the problem! I was using node-oauth (from here http://github.com/ciaranj/node-oauth/) and realized the signature was being generated wrong. Patched the library and it now works great!! Thank you!!! -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
