[twitter-dev] Re: Creating a list without description silently fails (on website as wel as using API
In my app, the list names are quite descriptive, so until this gets fixed - and I think it will be - I send description=name which makes some sense as the originally input name is transformed (loss of capitals and special characters) and does not appear in the Twitter UI anyway. On Oct 6, 1:06 am, Bert Lagaisse bert.lagai...@virtual-remote.com wrote: Posted ;-) I hadn't run my unittests for my upcoming WP7 twitter client in two weeks. Just ran them again and discovered this feature ;-) I now force the user to enter a description ;-) greets Bert Lagaissewww.virtual-remote.com/twozaic -- 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
Re: [twitter-dev] Adding twitter message
Thanks every one - correcting the clock on the server worked. - Original Message - From: Knutsford Software i...@knutsford-software.co.uk To: twitter-development-talk@googlegroups.com Sent: Tuesday, October 05, 2010 3:40 PM Subject: Re: [twitter-dev] Adding twitter message Stupid me - of course it doesn't. The server's clock appears to be way out. Thanks - Original Message - From: Tom van der Woerdt i...@tvdw.eu To: twitter-development-talk@googlegroups.com Sent: Tuesday, October 05, 2010 3:07 PM Subject: Re: [twitter-dev] Adding twitter message If you simply use time() then you'll get the correct timestamp, assuming that the server's clock is correct. Timezones do not influence time(). Tom On 10/5/10 3:29 PM, Knutsford Software wrote: PHP has now been upgraded to 5.2 on the server but it is now failing with Invalid / used nonce I gather that is due to the timezone not being liked. The site is being hosted in the UK so what do I do about the timezone so that twitter is happy pleas? so that Twitter is happy? Thanks -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] user details
Hello All, I have stored access token of some of the users in my database. Now, I want to retrieve friends and followers for these users. How can I retrieve this info? Any Ideas? thanks ashy -- 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
Re: [twitter-dev] user details
Once you have have authenticated the access tokens, you should be able to call the API directly to get a list of friends and followers using URLs such as http://api.twitter.com/1/followers/ids.json?user_id=12345 and http://api.twitter.com/1/friends/ids.json?user_id=12345 There is more information on the API document at: http://dev.twitter.com/doc/get/followers/ids and http://dev.twitter.com/doc/get/friends/ids I suppose more detailed information depends upon what language you are using, such as ruby, php, asp. I hope this helps. Regards, Ross t On 6 October 2010 12:56, ashy ashwinmo...@gmail.com wrote: Hello All, I have stored access token of some of the users in my database. Now, I want to retrieve friends and followers for these users. How can I retrieve this info? Any Ideas? thanks ashy -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] user details
Hi All, I have a python file and I am running it through command line. But it keeps giving error here CONSUMER = oauth.OAuthConsumer(CONSUMER_KEY, CONSUMER_SECRET) AttributeError: 'module' object has no attribute 'OAuthConsumer' whereas it works when trying to run it through web application. thanks ashy -- 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: user details
Hi All, Basically I am writing a cron job to retrieve friends and followers for the users. I have oauth token for these users stored in my database. Any Ideas? thanks ashy -- 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: @Anywhere communicate with PHP OAuth
Fantastic, thank you. I currently was just taking the cookie provided by @Anywhere and validating it. Once validated I made a OAuth call to users/show, which returned the users information. Am using it to provide single sign-on and need things such as name, username, etc.. this seams to do the trick. Will review the link further and implement it. On Oct 5, 4:17 pm, Abraham Williams 4bra...@gmail.com wrote: The functionality is there just not officially supported. http://blog.abrah.am/2010/09/using-twitter-anywhere-bridge-codes.html Abraham - Abraham Williams | Hacker Advocate |http://abrah.am Update:http://blog.abrah.am/2010/10/organizing-my-life.html @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Tue, Oct 5, 2010 at 12:39, Krileon krile...@gmail.com wrote: I've been reading that it is planned, but is it ever going to happen? Facebook does hits, Google Friend Connect does this (subsequently provides Twitter login as well through their API), so why can't twitters own API? Just pass a authorized key and secret with the cookie so we can through it through the OAuth request. This is making it an absolute nightmare to provide single sign-on for Twitter users as can be done with Facebook connect. 99% sites out there can't only superficially log users in with JS prettiness. They need to be stored inside the database so access permissions and what have you may function. -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: User_Timeline - include_rts not working
Ok, I think I may be closer to understanding what is not working or works in a strange way. The returned data, when retweets are included is of this structure. Each tweet that is a retweet, has the original tweet information underneath it. Tweet Tweet Retweet Tweet That's fine and all, except it appears that the original tweet is being included in the count of tweets requested per page. In the above example, this is considered 4 tweets being returned, not 3. If I request 25 tweets and there is one retweet, then I'm really only getting 24 tweets returned (plus the sub-tweet that is the original tweet that had been retweeted). So for now, I'm keeping a count of the number of retweets included in each page and showing a link to go to the next page if #tweets + #retweets count parameter. At least this let's users keep paging through the stream, but it still stinks that I can't get a full 25 tweets per page. What if a page was all retweets? Then the page would show NO records. On Oct 4, 1:28 pm, timrnicholson timrnichol...@gmail.com wrote: Further note that in testing, if I set the count parameter to 1 to return a single record and page through the friends_timeline, I actually get certain pages that return no data. i.e. I can page through a single tweet at a time and still get some responses that are empty. So the API is clearly first retrieving a record (or group of records) and then applying some other filter to it. Its that other filter that I need to figure out so that I can craft the request to ensure that I always get back the requested number of records (except when there are no more records). I don't see any way to retrieve the TOTAL number of records for a particular query either. If I could know for sure that a shortage of returned records on a particular page was due to some filter and that there truly are more records on subsequent pages, then I could at least use this as a workaround. On Oct 4, 11:48 am, timrnicholson timrnichol...@gmail.com wrote: Well, I thought i had this problem solved. I am using a library called twitteroauth and it was stripping off the include_rts=true. I finally figured out that include_rts needed to be placed into an arguments array instead of being in the request URL. So once I got the include_rts parm passed to Twitter everything wasworkingfine. Or at least it was in most cases. HOWEVER, I am seeing now that certain requests areNOTreturning the fullcountparameter worth of records. There must be SOME filtering that the Twitter API is doing AFTER it retrieves thecountnumber worth of records. I have this problem regardless of whether I use the home_timeline which is supposed to always include everything or whether I use the friends_timeline with the include_rtsparameter. Note that I am trying to requestcount= 25 records,notthe defaultcount= 20 records. I can see that retweets are being included and I'm still getting ust 24 records back in certain cases. On Sep 9, 10:06 am, Matt Harris thematthar...@twitter.com wrote: Hey Tim, When I run: curl http://api.twitter.com/1/statuses/user_timeline/RWW.xml?count=20page...; I get the expected result of 20 statuses one retweet (from @ConanOBrien). When you make the request are you running it like I am or are you using a library? To answer your query about thecountparameter. The behavior is this: we will try and return up to 'count' statuses in one request, wherecountis equal to all statuses in the timeline before any filtering of retweets. So, if you request 20 statuses without retweets, and 1 of the statuses is a retweet, you will get 19 statuses back. Hope that helps explain what is going on, Matt On Thu, Sep 9, 2010 at 7:30 AM, timrnicholson timrnichol...@gmail.com wrote: I'm properly calling api.twitter.com/1/statuses/user_timeline with include_rts as true and retweets arenotbeing included. The only stream that I can get to return retweets (because it doesn't even require the include_rtsparameter) is the home_timeline. For example, the following doesn't work: http://api.twitter.com/1/statuses/user_timeline/RWW.xml?count=20page... The worst part about this isnotjust that the include_rtsparameter doesn't work for including retweets, the returned timeline doesn't even have 20 records in it when there are retweets. In other words, the API isnotonly ignoring the include_rtsparameterbut itsnot even returning the right number of requested records when it thinks include_rts is false. This totally screws up my pagination methods because I'm getting less than the expected number of records back, so my app thinks there's no more timeline to be retrieved. I certainly don't want to just always include a next page link when there really aren't any more records left. Also, thecountparameteris being ignored in all of this as well, but I've
[twitter-dev] Read-only application cannot POST problem
Hello, I've created an app, it has read-write setting enabled, all twitter users can post through it, but I can't, getting Read-only application cannot POST problem. Is it because I'm a developer??? BR, Alexey -- 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
Re: [twitter-dev] Read-only application cannot POST problem
Hi Alexey, If your access token was issued while your application was still in read-only mode, you'll need to reissue it by first going to http://twitter.com/settings/connections and revoking your application permission, then re-negotiate your access token. It will then be a read/write access token. Taylor On Wed, Oct 6, 2010 at 6:58 AM, Skip ayla...@gmail.com wrote: Hello, I've created an app, it has read-write setting enabled, all twitter users can post through it, but I can't, getting Read-only application cannot POST problem. Is it because I'm a developer??? BR, Alexey -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Read-only application cannot POST problem
Thanks! It helped! On Oct 6, 6:06 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Alexey, If your access token was issued while your application was still in read-only mode, you'll need to reissue it by first going tohttp://twitter.com/settings/connectionsand revoking your application permission, then re-negotiate your access token. It will then be a read/write access token. Taylor On Wed, Oct 6, 2010 at 6:58 AM, Skip ayla...@gmail.com wrote: Hello, I've created an app, it has read-write setting enabled, all twitter users can post through it, but I can't, getting Read-only application cannot POST problem. Is it because I'm a developer??? BR, Alexey -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] just to know that, why I am not getting data for big user ?
Hi there, I just need to know that is there any problem in getting data from API? I am using rest API to get data from API, mainly accessing user's followers data. I have been able to search a user having 1L followers on my site but from last 2 - 3 days, I am not able to search user having 30k followers, neither get any error nor result. So just need to ask that is this from twitter side? because this is also happening when I run a code snippet in separate file. Thank you in advance. -- 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
Re: [twitter-dev] just to know that, why I am not getting data for big user ?
What are the specific API methods that you are calling? Can you share the specific user? When you say neither get any error nor result do you mean the HTTP response is completely empty or that within whatever library/implementation you are using the calls do not yield results nor exceptions? Taylor On Wed, Oct 6, 2010 at 7:12 AM, Rushikesh Bhanage rishibhan...@gmail.comwrote: Hi there, I just need to know that is there any problem in getting data from API? I am using rest API to get data from API, mainly accessing user's followers data. I have been able to search a user having 1L followers on my site but from last 2 - 3 days, I am not able to search user having 30k followers, neither get any error nor result. So just need to ask that is this from twitter side? because this is also happening when I run a code snippet in separate file. Thank you in advance. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: user details
Just a wild guess. Try this: import oauth.oauth as oauth On Oct 6, 2:22 pm, ashwin morey ashwinmo...@gmail.com wrote: Hi All, I have a python file and I am running it through command line. But it keeps giving error here CONSUMER = oauth.OAuthConsumer(CONSUMER_KEY, CONSUMER_SECRET) AttributeError: 'module' object has no attribute 'OAuthConsumer' whereas it works when trying to run it through web application. thanks ashy -- 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: Over the limit for this type of request, please wait a while and try again
Are any of the other POST methods now also similarly rate limited, or is it only destroy friendship? On Oct 5, 11:13 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi James, I'll re-post this in the group thread as well. Due to potential abuse, we've begun locking down bulk deletions that were previously unbound. These lack of limits lead to many application suspensions and blacklisting as the lack of a rate limit was often interpreted as give us all you've got, non stop, in addition to obvious system gaming. We're unfortunately not yet publishing the limits on these kinds of actions. Though this limit is trickle-down reflected in the API, it's actually a site-wide construct. It's an IP-based limit, and not a user-based limit. As you'll most likely be able to discover the limits yourself, I'll work on getting these numbers released and hopefully get an X-FeatureRateLimit set of HTTP headers attached to these requests also. I would recommend developing the following strategy when you run into this error: - Back off for 5-6 minutes (stop retrying this specific kind of request) - Try the request again. - If it succeeds, great, continue until you're limited again (or work on ways to never get limited, such as preventing bulk actions in your UI) - If it fails again, wait another 2 minutes, retry repeat. I think the current limits are pretty reasonable, and the time window refreshes often. The error will be a Error 420, Rate Limited. The error code embedded in either JSON or XML structures will be 33 and the accompanying message: Over the limit for this type of request, please wait a while and try again Taylor Singletary @episod On Tue, Oct 5, 2010 at 1:56 AM, James Peter zemaj@gmail.com wrote: Hi folks, Our service has been down for over 3 days now due to broken API calls. Still waiting on any information from Twitter about what's going on, but still in the dark. About 3 days ago we started receiving messages (incorrectly in the new error structure) saying Over the limit for this type of request, please wait a while and try again with error code 33 when calling friendships/destroy. According to the API docs, this call is not rate limitedhttp://dev.twitter.com/doc/post/friendships/destroyAll our API requests are authenticated with the requesting user. This happens after about 100 calls. It makes our app completely unusable. I'm guessing it's a bug, but after 3 days I'm wondering if anyone else is seeing this problem. As the errors are returned in the new error structure they didn't appear in our logs at first, so you might be experiencing this problem and not noticing. The new error structure returns a set of error messages under errors instead of just a string under error. James -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Miscellaneous #newtwitter glitches
1. As a result of the Who to follow field, I'm now gaining followers fairly rapidly. So rapidly, in fact, that I can't follow all or even most of them back without hitting some limit. I'm not sure how you'd adjust that, but there's a subtle bug in the way it's being handled. Suppose user J follows me. I go into the Followers list, see that J has followed me. I go look at J's profile. OK - J's cool, I want to follow him. So I press the big Follow button with the green plus sign. Twitter sez Could not follow user: You are unable to follow more people at this time. Learn more here. But guess what? The button changes to Blocked! I have to click the Undo link. It looks like there are three states, and the system is cycling through them: a. Not following b. Following c. Blocked It can't change from Not following to following because of the limit, so it cycles to the next state, which is Blocked. 2. There's some kind of Javascript / CSS issue with the left panel in Chrome / Chromium 7. Everything is cool in Firefox 3.6, and I haven't tried older versions of Chrome. I'm not quite sure how to reproduce this reliably yet, but sometimes, when I'm following a trail into the right panel, when I have the mouse in the right panel, the left panel goes completely black. If I move the mouse back into the left panel, it comes back, but slowly - like it's running some kind of intensive Javascript to repaint or making a bunch of API calls to refill a buffer. I'm a total Javascript / CSS / DOM ignoramus, so if someone has some clues as to how I can diagnose this in the Chrome / Chromium debugger, let me know. 3. A related phenomenon - I went to @scobleizer and opened up a tweet. When I moused back into the *left* panel, the left one went blank, exposing the background! But when I mouse back into the right panel, the left one came back rapidly. Again, this is on Chrome / Chromium. -- M. Edward (Ed) Borasky http://borasky-research.net http://twitter.com/znmeb A mathematician is a device for turning coffee into theorems. - Paul Erdos -- 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: URL parameters
Hi Tom, Thanx for the quick answer. I did as you said, took the GET parameters off the url and put them with the rest as I did with POST parameters. Now I just have to sort them all right? This made me discover that my POST parameters worked just by coincidence, as I was appending them at the end of the base string without sorting. (un)luckily, that was their sorted position!! So, got some work to do, thanx again! Miguel. On Oct 5, 5:26 pm, Tom van der Woerdt i...@tvdw.eu wrote: Just add the parameters to the Base String. Don't add the query to the URL part of the Base String though! The easiest way to check whether your base string is correct or not, is to use the OAuth Base String validation tool at http://quonos.nl/oauthTester Tom On 10/5/10 11:06 PM, MigueL D aZ wrote: Hi all, I'm developing a twitter client app and I'm trying to find out how do I navigate through the timeline. I've implemented oauth and have a lot of methods working, including retrieving the timeline. A call tohttp://api.twitter.com/1/statuses/home_timeline.jsongives me the first 20 tweets, but I want to know if it's possible to get, for instance, the next 20. I've tried with: http://api.twitter.com/1/statuses/home_timeline.json?count=40 http://api.twitter.com/1/statuses/home_timeline.json?max_id=26488109595 But I always receive 401 Unauthorized... So I guess I'm messing it up with my base string to sign... How should the base string look when the url has extra paramenters? Regards! Miguel. -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] [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
Re: [twitter-dev] [SiteStreams] can't follow more than one user
Hey, Ruben. That's the correct URL format. Are you sure your account was approved for Site Stream access? Ruben Fonseca wrote: 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! -- Thomas Mango tsma...@gmail.com -- 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
Re: [twitter-dev] Re: [SiteStreams] can't follow more than one user
It might be an OAuth encoding error with the ','. Which OAuth library are you using? -John On Wed, Oct 6, 2010 at 9:34 AM, Ruben Fonseca fons...@gmail.com wrote: 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 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
Re: [twitter-dev] Re: Over the limit for this type of request, please wait a while and try again
Hi Dewald, There are other methods which are similarly rate limited. They are documented on our help center: http://support.twitter.com/articles/15364 The overview of rate limits on the developer site provides some more background about rate limits in general and then goes onto link to the above document. The overview is published here: http://dev.twitter.com/pages/rate-limiting Hope that answers your question, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Oct 6, 2010 at 8:13 AM, Dewald Pretorius dpr...@gmail.com wrote: Are any of the other POST methods now also similarly rate limited, or is it only destroy friendship? On Oct 5, 11:13 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi James, I'll re-post this in the group thread as well. Due to potential abuse, we've begun locking down bulk deletions that were previously unbound. These lack of limits lead to many application suspensions and blacklisting as the lack of a rate limit was often interpreted as give us all you've got, non stop, in addition to obvious system gaming. We're unfortunately not yet publishing the limits on these kinds of actions. Though this limit is trickle-down reflected in the API, it's actually a site-wide construct. It's an IP-based limit, and not a user-based limit. As you'll most likely be able to discover the limits yourself, I'll work on getting these numbers released and hopefully get an X-FeatureRateLimit set of HTTP headers attached to these requests also. I would recommend developing the following strategy when you run into this error: - Back off for 5-6 minutes (stop retrying this specific kind of request) - Try the request again. - If it succeeds, great, continue until you're limited again (or work on ways to never get limited, such as preventing bulk actions in your UI) - If it fails again, wait another 2 minutes, retry repeat. I think the current limits are pretty reasonable, and the time window refreshes often. The error will be a Error 420, Rate Limited. The error code embedded in either JSON or XML structures will be 33 and the accompanying message: Over the limit for this type of request, please wait a while and try again Taylor Singletary @episod On Tue, Oct 5, 2010 at 1:56 AM, James Peter zemaj@gmail.com wrote: Hi folks, Our service has been down for over 3 days now due to broken API calls. Still waiting on any information from Twitter about what's going on, but still in the dark. About 3 days ago we started receiving messages (incorrectly in the new error structure) saying Over the limit for this type of request, please wait a while and try again with error code 33 when calling friendships/destroy. According to the API docs, this call is not rate limitedhttp://dev.twitter.com/doc/post/friendships/destroyAll our API requests are authenticated with the requesting user. This happens after about 100 calls. It makes our app completely unusable. I'm guessing it's a bug, but after 3 days I'm wondering if anyone else is seeing this problem. As the errors are returned in the new error structure they didn't appear in our logs at first, so you might be experiencing this problem and not noticing. The new error structure returns a set of error messages under errors instead of just a string under error. James -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter 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
Re: [twitter-dev] Re: Creating a list without description silently fails (on website as wel as using API
Thanks for filing this. The team has been notified and i'll update the ticket on the issue tracker with any progress. Best, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Tue, Oct 5, 2010 at 11:57 PM, Ken D. k...@cimas.ch wrote: In my app, the list names are quite descriptive, so until this gets fixed - and I think it will be - I send description=name which makes some sense as the originally input name is transformed (loss of capitals and special characters) and does not appear in the Twitter UI anyway. On Oct 6, 1:06 am, Bert Lagaisse bert.lagai...@virtual-remote.com wrote: Posted ;-) I hadn't run my unittests for my upcoming WP7 twitter client in two weeks. Just ran them again and discovered this feature ;-) I now force the user to enter a description ;-) greets Bert Lagaissewww.virtual-remote.com/twozaic -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Tweet button not working with a 'localhost' data-url?
Hi, I'm currently testing the tweet button for our website. When I test the button locally and want to share a link in the form of 'http://localhost:8080/somepath/image.jpg' its says that the 'url' param is invalid. But when I test it on a 'real' server (like example.com) the button does work. The data-url attribures are dynamically generated, which means if the file was on 'example.com' instead of 'localhost' the link would be 'http://example.com/somepath/image.jpg' Can anyone confirm that share does not work with 'localhost' as data- url? Thanks, Olivier. -- 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
Re: [twitter-dev] Tweet button not working with a 'localhost' data-url?
http://localhost is not a shareable URL so this error is expected. Instead, if you need to test things locally you might want to add a development domain name into your computers hosts file instead. Hope that helps, @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Oct 6, 2010 at 1:29 PM, Olivier K okite...@gmail.com wrote: Hi, I'm currently testing the tweet button for our website. When I test the button locally and want to share a link in the form of 'http://localhost:8080/somepath/image.jpg' its says that the 'url' param is invalid. But when I test it on a 'real' server (like example.com) the button does work. The data-url attribures are dynamically generated, which means if the file was on 'example.com' instead of 'localhost' the link would be 'http://example.com/somepath/image.jpg' Can anyone confirm that share does not work with 'localhost' as data- url? Thanks, Olivier. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Tweet button not working with a 'localhost' data-url?
Why would you want to generate a link that would only work for you? Just accept that it will not work and you'll be fine ;-) Tom On 10/6/10 10:29 PM, Olivier K wrote: Hi, I'm currently testing the tweet button for our website. When I test the button locally and want to share a link in the form of 'http://localhost:8080/somepath/image.jpg' its says that the 'url' param is invalid. But when I test it on a 'real' server (like example.com) the button does work. The data-url attribures are dynamically generated, which means if the file was on 'example.com' instead of 'localhost' the link would be 'http://example.com/somepath/image.jpg' Can anyone confirm that share does not work with 'localhost' as data- url? Thanks, Olivier. -- 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] User Streaming API and use of OAuth from web browser
Hi, We are building an application client that is browser based. We're very comfortable with using OAuth from our server side code and are using it fine with the REST API (users sign in, authenticate with Twitter, we store their access tokens and reuse as requested - at the moment we mimic the required Twitter API on our server and when a user does something like a POST, we call our stub, use their token to then make the call via OAuth to Twitter). So far so good, but we'd like to implement User Streaming directly into the client side application. I've been browsing the Twitter Development documentation and there's a couple of points I'd like clarification on: * http://dev.twitter.com/pages/auth_overview says Streaming supports Basic and OAuth. * http://dev.twitter.com/pages/user_streams says that the user streams supports OAuth only HTTPS, OAuth and JSON only. No problems here, I just raise it to point out the auth_overview doco is slightly out of date. * http://dev.twitter.com/pages/oauth_libraries talks about a JS library but says Javascript really shouldn't be used for OAuth 1.0A with respect to websites in web browsers. Ideally, you'll only use Javascript to perform OAuth operations when using server-side. The points I'd like some clarification on: 1. Given user_streams API is the intended way for clients to access Twitter going forwards, I presume it's intended not just for desktop, but also web clients too? 2. If 1 is correct, then is it OK to use JavaScript for the OAuth? If it's not, what is the recommended approach for a client side web application to connect and authenticate to the user_stream? Thanks, Tim -- 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
Re: [twitter-dev] User Streaming API and use of OAuth from web browser
OAuth 1.0a was made for server to server authentication. It uses secrets for the client, which would make your application vulnerable. So, no, you should not use JavaScript for OAuth. Not before Twitter starts using OAuth 2.0. About the document you are referring to: there are three types of streams: normal streams, user streams and site streams. In most cases when the documentation refers to Streaming, it refers to the Normal Streams (= filter, sample, firehose, etc). There would be one more issue which requires mentioning: JavaScript's Same-origin policy. You can't make a request directly to the Twitter API via JavaScript: you *will* need a proxy on your own server. Tom On 10/6/10 10:54 PM, Tim Bull wrote: Hi, We are building an application client that is browser based. We're very comfortable with using OAuth from our server side code and are using it fine with the REST API (users sign in, authenticate with Twitter, we store their access tokens and reuse as requested - at the moment we mimic the required Twitter API on our server and when a user does something like a POST, we call our stub, use their token to then make the call via OAuth to Twitter). So far so good, but we'd like to implement User Streaming directly into the client side application. I've been browsing the Twitter Development documentation and there's a couple of points I'd like clarification on: * http://dev.twitter.com/pages/auth_overview says Streaming supports Basic and OAuth. * http://dev.twitter.com/pages/user_streams says that the user streams supports OAuth only HTTPS, OAuth and JSON only. No problems here, I just raise it to point out the auth_overview doco is slightly out of date. * http://dev.twitter.com/pages/oauth_libraries talks about a JS library but says Javascript really shouldn't be used for OAuth 1.0A with respect to websites in web browsers. Ideally, you'll only use Javascript to perform OAuth operations when using server-side. The points I'd like some clarification on: 1. Given user_streams API is the intended way for clients to access Twitter going forwards, I presume it's intended not just for desktop, but also web clients too? 2. If 1 is correct, then is it OK to use JavaScript for the OAuth? If it's not, what is the recommended approach for a client side web application to connect and authenticate to the user_stream? Thanks, Tim -- 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] statuses/retweets_of_me returning statuses that haven't been retweeted
I'm seeing a lot of statuses coming back from statuses/retweets_of_me with retweet_count set to 0 or null and retweeted set to false. -- 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
Re: [twitter-dev] statuses/retweets_of_me returning statuses that haven't been retweeted
The retweet_count and retweeted fields are not yet 100% functional. Taylor On Wed, Oct 6, 2010 at 2:01 PM, Aaron Rankin aran...@sproutsocial.comwrote: I'm seeing a lot of statuses coming back from statuses/retweets_of_me with retweet_count set to 0 or null and retweeted set to false. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Over the limit for this type of request, please wait a while and try again
Matt, I'm aware of those rate limits. I was referring to methods that used to be, Give us all you got, such as destroy friendship. For example, create block, destroy block, etc. On Oct 6, 3:38 pm, Matt Harris thematthar...@twitter.com wrote: Hi Dewald, There are other methods which are similarly rate limited. They are documented on our help center: http://support.twitter.com/articles/15364 The overview of rate limits on the developer site provides some more background about rate limits in general and then goes onto link to the above document. The overview is published here: http://dev.twitter.com/pages/rate-limiting Hope that answers your question, @themattharris Developer Advocate, Twitterhttp://twitter.com/themattharris On Wed, Oct 6, 2010 at 8:13 AM, Dewald Pretorius dpr...@gmail.com wrote: Are any of the other POST methods now also similarly rate limited, or is it only destroy friendship? On Oct 5, 11:13 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi James, I'll re-post this in the group thread as well. Due to potential abuse, we've begun locking down bulk deletions that were previously unbound. These lack of limits lead to many application suspensions and blacklisting as the lack of a rate limit was often interpreted as give us all you've got, non stop, in addition to obvious system gaming. We're unfortunately not yet publishing the limits on these kinds of actions. Though this limit is trickle-down reflected in the API, it's actually a site-wide construct. It's an IP-based limit, and not a user-based limit. As you'll most likely be able to discover the limits yourself, I'll work on getting these numbers released and hopefully get an X-FeatureRateLimit set of HTTP headers attached to these requests also. I would recommend developing the following strategy when you run into this error: - Back off for 5-6 minutes (stop retrying this specific kind of request) - Try the request again. - If it succeeds, great, continue until you're limited again (or work on ways to never get limited, such as preventing bulk actions in your UI) - If it fails again, wait another 2 minutes, retry repeat. I think the current limits are pretty reasonable, and the time window refreshes often. The error will be a Error 420, Rate Limited. The error code embedded in either JSON or XML structures will be 33 and the accompanying message: Over the limit for this type of request, please wait a while and try again Taylor Singletary @episod On Tue, Oct 5, 2010 at 1:56 AM, James Peter zemaj@gmail.com wrote: Hi folks, Our service has been down for over 3 days now due to broken API calls. Still waiting on any information from Twitter about what's going on, but still in the dark. About 3 days ago we started receiving messages (incorrectly in the new error structure) saying Over the limit for this type of request, please wait a while and try again with error code 33 when calling friendships/destroy. According to the API docs, this call is not rate limitedhttp://dev.twitter.com/doc/post/friendships/destroyAllour API requests are authenticated with the requesting user. This happens after about 100 calls. It makes our app completely unusable. I'm guessing it's a bug, but after 3 days I'm wondering if anyone else is seeing this problem. As the errors are returned in the new error structure they didn't appear in our logs at first, so you might be experiencing this problem and not noticing. The new error structure returns a set of error messages under errors instead of just a string under error. James -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk -- Twitter 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
Re: [twitter-dev] User Streaming API and use of OAuth from web browser
There would be one more issue which requires mentioning: JavaScript's Same-origin policy. You can't make a request directly to the Twitter API via JavaScript: you *will* need a proxy on your own server. Which seems to put web developers at a sever disadvantage for search and streaming APIs since rate limits are based on IP addresses. Meaning all my web users count as one whereas the rate limiting is spread out among all the users a given desktop client. I asked a while back about this and didn't get a response. It just don't seem fair. Seems impossible to build a web app of anything more than a couple hundred users if those users want to use search and or streaming. Or correct me. -- 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: can't follow more than one user
Hi, The library in question is mine and not unreasonably Ruben has submitted a pull-request with his fix over on github. Unfortunately this fix seems to break existing (working) OAuth consumer relationships :( I'm actually at a bit of a loss how to progress it, I've read: http://dev.twitter.com/pages/auth (Signing Requests) a few times. I've cross-referenced against http://oauth.net/core/1.0a/ Sec. 9.1.1 and even double checked against http://tools.ietf.org/html/rfc5849#section-3.4.1 Sec. 3.4.1.3.2 The last two resources appear to agree with each other, that the '=' and the '' that join the parameter name-value pairs should appear in the 'plain' but then get encoded as a whole [which would re-encode any existing '%', hence a crucial difference in the twitter listed strategy] The important bit seems to be in the OAuth 1.0 RFC Section 3.4.1.1. String Construction, point 5: 5. The request parameters as normalized in Section 3.4.1.3.2, after being encoded (Section 3.6). Crucially this suggests to me that that the encoding is applied to the entire normalized string, which the documentation at http://dev.twitter.com/pages/auth seems to suggest isn't happening on the Twitter side :( It is (more than likely) entirely possible that I'm doing something incredibly stupid and obvious but is there anyone on the twitter side that can confirm that this deviation from the 'spec' is deliberate (or even better for consistency, a minor issue?) Many Thanks (and sorry if I'm wasting your time!) - Cj. On Oct 6, 6:31 pm, Ruben Fonseca fons...@gmail.com wrote: 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 herehttp://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
Re: [twitter-dev] User Streaming API and use of OAuth from web browser
I will indeed correct you: rate limits are based on account when using oauth. Tom On Oct 6, 2010, at 11:39 PM, Matthew Terenzio mteren...@gmail.com wrote: There would be one more issue which requires mentioning: JavaScript's Same-origin policy. You can't make a request directly to the Twitter API via JavaScript: you *will* need a proxy on your own server. Which seems to put web developers at a sever disadvantage for search and streaming APIs since rate limits are based on IP addresses. Meaning all my web users count as one whereas the rate limiting is spread out among all the users a given desktop client. I asked a while back about this and didn't get a response. It just don't seem fair. Seems impossible to build a web app of anything more than a couple hundred users if those users want to use search and or streaming. Or correct me. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] User Streaming API and use of OAuth from web browser
On Wed, Oct 6, 2010 at 5:48 PM, Tom van der Woerdt i...@tvdw.eu wrote: I will indeed correct you: rate limits are based on account when using oauth. Really? Can someone second that. I re-read the documentation and it doesn't look like it to me. Are the IP limits ignored when you log in as a user. I know that is the case for the REST api in most cases but I'm talking about streaming and search. Tom On Oct 6, 2010, at 11:39 PM, Matthew Terenzio mteren...@gmail.com wrote: There would be one more issue which requires mentioning: JavaScript's Same-origin policy. You can't make a request directly to the Twitter API via JavaScript: you *will* need a proxy on your own server. Which seems to put web developers at a sever disadvantage for search and streaming APIs since rate limits are based on IP addresses. Meaning all my web users count as one whereas the rate limiting is spread out among all the users a given desktop client. I asked a while back about this and didn't get a response. It just don't seem fair. Seems impossible to build a web app of anything more than a couple hundred users if those users want to use search and or streaming. Or correct me. -- Twitter developer documentation and resources: http://dev.twitter.com/dochttp://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter 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] Can I tell how many tweets have been made by users of my app?
Hi: Is there a way to tell how may tweets have been sent by my app? It uses Oath so people's tweets say from xxx app Also, is there a way to track the number of users who have made a tweet through my app? Thanks, Joseph -- 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] Unable to connect to the Streaming API over SSL
Hi all, For several months now, we've been connecting to the streaming api filter resource over SSL without issue. Today it suddenly disconnected us and wouldn't let us reconnect. We tried from multiple IPs to connect without success so it doesn't appear to be some sort of blacklist issue. Is this a temporary outage or something more permanent? If it's temporary, is there any ETA on a resolution? Please let me know if there's more information I can provide to help resolve this. Hayes -- 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
Re: [twitter-dev] Unable to connect to the Streaming API over SSL
Hi Hayes, The public streaming API endpoint at stream.twitter.com had SSL support turned off recently -- we hadn't, I believe, ever explicitly documented that it supported SSL. I wasn't aware of this change and have some issues with it -- I'll see what I can do. In the meantime, please use non-SSL. Taylor On Wed, Oct 6, 2010 at 3:35 PM, Hayes Davis ha...@appozite.com wrote: Hi all, For several months now, we've been connecting to the streaming api filter resource over SSL without issue. Today it suddenly disconnected us and wouldn't let us reconnect. We tried from multiple IPs to connect without success so it doesn't appear to be some sort of blacklist issue. Is this a temporary outage or something more permanent? If it's temporary, is there any ETA on a resolution? Please let me know if there's more information I can provide to help resolve this. Hayes -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] User Streaming API and use of OAuth from web browser
All the information about rate limits can be found on our developer site: http://dev.twitter.com/pages/rate-limiting When talking about rate limits it is important to be clear about the API being used, as each has their own. For the REST API (requests to api.twitter.com) the limit is 150 requests per hour unauthenticated and 350 request per hour for an authenticated user. When you make an authenticated request the users rate limit is affected, not the IPs. The Search API has it's own rate limit based on the IP the request comes from. There is no authenticating for Search so all requests are IP rate limited. The Streaming APIs do not have rate limits in the same way. For the Streaming API the rate limit is controlled by the predicate limits (5,000 user ids etc) and the allowed sampling rate (1% etc). I hope that clarifies how the rate limits apply. Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Oct 6, 2010 at 3:28 PM, Matthew Terenzio mteren...@gmail.com wrote: On Wed, Oct 6, 2010 at 5:48 PM, Tom van der Woerdt i...@tvdw.eu wrote: I will indeed correct you: rate limits are based on account when using oauth. Really? Can someone second that. I re-read the documentation and it doesn't look like it to me. Are the IP limits ignored when you log in as a user. I know that is the case for the REST api in most cases but I'm talking about streaming and search. Tom On Oct 6, 2010, at 11:39 PM, Matthew Terenzio mteren...@gmail.com wrote: There would be one more issue which requires mentioning: JavaScript's Same-origin policy. You can't make a request directly to the Twitter API via JavaScript: you *will* need a proxy on your own server. Which seems to put web developers at a sever disadvantage for search and streaming APIs since rate limits are based on IP addresses. Meaning all my web users count as one whereas the rate limiting is spread out among all the users a given desktop client. I asked a while back about this and didn't get a response. It just don't seem fair. Seems impossible to build a web app of anything more than a couple hundred users if those users want to use search and or streaming. Or correct me. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Converting to oAuth / xAuth from Progress Open Edge applications
We are converting our Twitter interfaces to oAuth and from the advise on http://twittervb.codeplex.com/wikipage?title=XAuth we are heading down the path of xAuth for our desk top applications that use Twitter. We opted not to use TwitterVB.dll for backward compatibility of older sites, so we are faced with a DIY situation. Even though we are intending to use xAuth, we have had to build libraries that will handle the authentication and signature of the messages, so as a first step we are attempting to replicate the request token as explained in http://dev/twitter.com/pages/auth . We have build libraries that correctly assemble the post parameters, we are using ChilKat Crypt to create the signature, and to prove they are working we copy / paste the POST parameters from the example on http://dev/twitter.com/pages/auth and pass it to our library methods, the returned signature and post is exactly the same as the examples on http://dev/twitter.com/pages/auth. Then using our consumber key etc we create the POST and is formatted exactly the same as the example on http://dev/twitter.com/pages/auth, except of course it uses our consumer_key, oauth_nonce/timetamp etc. So the package we are sending looks perfect, we dumped it to Notepad.exe and copy / pasted in dev.twitter.com example to compare character by character and confirmed the only difference being the oauth_consumer_key, signature etc. YET, regardless of if we send it through MS XMLHTTP or convert it to a URL and copy / paste into a Web browser we still get the message Failed to validate oauth signature and token. We have exausted all the on line web blogs and resources we can find. We have used sites like http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/ to try to reconstruct the post and compare the results against what our application produces, and we are at a loss. It looks like we have the wrong consumer keys or something stupid, but beleive me we have copy / pasted those in as well to make sure there was no error. Remember we have used the parameters in your example on http://dev.twitter.com/pages/auth and the signature and resulting posts our software produces are the same as the examples on dev.twitter.com, so it looks like our software using our libraries is working correctly. Here are the two posts, with the example from dev.Twitter.com followed by the one produced by our site : Sample 1 - From our software but using values from http://dev.twitter.com/pages/auth OAuth oauth_callback=http%3A%2F%2Flocalhost%3A3005%2Fthe_dance %2Fprocess_callback%3Fservice_provider_id%, oauth_consumer_key=GDdmIQH6jhtmLUypg82g , oauth_nonce=QP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk, oauth_signature=8wUi7m5HFQy76nowoCThusfgB%2BQ%3D, oauth_signature_method=HMAC-SHA1, oauth_timestamp=12723230, oauth_version=1.0 Sample 2 - From our software using our consumer keys etc OAuth oauth_callback=oob, oauth_consumer_key=TY0Js5vMc04HNqmqIkNEnQ, oauth_nonce=ZcVmkYA3KYlVwN0kRaNHcsxiPbl4m16KZSHeyZfGF1v, oauth_signature=0XXxEzENnco46hxIrgIG%2FvfK9Wk%3D, oauth_signiture_method=HMAC-SHA1, oauth_timestamp=53697279, oauth_version=1.0 ALSO: I noted if we use the URL https://api.twitter.com/oauth/request_token?bla_bla_bla it also returns the same message so the API needs a little more diagnostic capability or perhaps you can provide a diagnostic tool or sandbox environment to help developers know whats wrong with the posts. What can we do from here... -- 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] Fwd: Twitter Support: update on Favstar50celeb has been suspended.
Hi Developer Advocates, I received this message today after @favstar50celeb has been unsuspended. Can I ask for a little more insight as to why @favstar50celeb was suspended and others like @favstar50 haven't been? Cheers, Tim. -- Forwarded message -- From: JuneClippers notifications-supp...@twitter.zendesk.com Date: Thu, Oct 7, 2010 at 8:49 AM Subject: Twitter Support: update on Favstar50celeb has been suspended.. To: favstar50celeb favstar50ce...@favstar.fm ## Please do not write below this line ## Ticket #1251243: Favstar50celeb has been suspended. :-( This account is used... http://twitter.zendesk.com/tickets/1251243 -- *JuneClippers, Oct 06 04:49 pm (PDT):* Hello, This account was suspended for reply spam. The reply feature is intended to make communication between people on Twitter easier. Twitter monitors the use of the reply feature to make sure that it's used as intended and not used for abuse. Using the reply feature to post messages to a bunch of users' replies tabs is considered an abuse of the feature, which results in account suspension. I have now un-suspended your account. Be sure to review the Twitter Rules, as repeat violations may result in permanent suspension: http://twitter.com/rules Thank you, JuneClippers This email is a service from Twitter Support -- 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
Re: [twitter-dev] User Streaming API and use of OAuth from web browser
So yes, I was correct (at least with search) that a web based solution is severely limited compared to a desktop. It will share usage among all it's users while a desktop client can spread the load amongst its users IPs. That stinks in my opinion. (I'm a web developer.) On Wed, Oct 6, 2010 at 7:44 PM, Matt Harris thematthar...@twitter.comwrote: All the information about rate limits can be found on our developer site: http://dev.twitter.com/pages/rate-limiting When talking about rate limits it is important to be clear about the API being used, as each has their own. For the REST API (requests to api.twitter.com) the limit is 150 requests per hour unauthenticated and 350 request per hour for an authenticated user. When you make an authenticated request the users rate limit is affected, not the IPs. The Search API has it's own rate limit based on the IP the request comes from. There is no authenticating for Search so all requests are IP rate limited. The Streaming APIs do not have rate limits in the same way. For the Streaming API the rate limit is controlled by the predicate limits (5,000 user ids etc) and the allowed sampling rate (1% etc). I hope that clarifies how the rate limits apply. Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Oct 6, 2010 at 3:28 PM, Matthew Terenzio mteren...@gmail.com wrote: On Wed, Oct 6, 2010 at 5:48 PM, Tom van der Woerdt i...@tvdw.eu wrote: I will indeed correct you: rate limits are based on account when using oauth. Really? Can someone second that. I re-read the documentation and it doesn't look like it to me. Are the IP limits ignored when you log in as a user. I know that is the case for the REST api in most cases but I'm talking about streaming and search. Tom On Oct 6, 2010, at 11:39 PM, Matthew Terenzio mteren...@gmail.com wrote: There would be one more issue which requires mentioning: JavaScript's Same-origin policy. You can't make a request directly to the Twitter API via JavaScript: you *will* need a proxy on your own server. Which seems to put web developers at a sever disadvantage for search and streaming APIs since rate limits are based on IP addresses. Meaning all my web users count as one whereas the rate limiting is spread out among all the users a given desktop client. I asked a while back about this and didn't get a response. It just don't seem fair. Seems impossible to build a web app of anything more than a couple hundred users if those users want to use search and or streaming. Or correct me. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter 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
Re: [twitter-dev] Converting to oAuth / xAuth from Progress Open Edge applications
Hi Martin, In the example you give the timestamp you are using converts to one from the year 1971 so you want to check how you are creating that. The correct timestamp value is the current epoch time in seconds. Without seeing your basestring it is difficult to know what could be going wrong. One thing to check is that your signing key is correct. The signing key format is YOUR_CONSUMER_SECRETTHE_USER_SECRET. When requesting a token you don't have a user secret so the signing key becomes YOUR_CONSUMER_KEY. Also make sure you are not sending the OAuth parameters more than once. As the parameters are in the Authorization header they shouldn't be included in any GET or POST parameters. Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Oct 6, 2010 at 4:37 PM, Martin Hannah mhan...@coresoft.com.au wrote: We are converting our Twitter interfaces to oAuth and from the advise on http://twittervb.codeplex.com/wikipage?title=XAuth we are heading down the path of xAuth for our desk top applications that use Twitter. We opted not to use TwitterVB.dll for backward compatibility of older sites, so we are faced with a DIY situation. Even though we are intending to use xAuth, we have had to build libraries that will handle the authentication and signature of the messages, so as a first step we are attempting to replicate the request token as explained in http://dev/twitter.com/pages/auth . We have build libraries that correctly assemble the post parameters, we are using ChilKat Crypt to create the signature, and to prove they are working we copy / paste the POST parameters from the example on http://dev/twitter.com/pages/auth and pass it to our library methods, the returned signature and post is exactly the same as the examples on http://dev/twitter.com/pages/auth. Then using our consumber key etc we create the POST and is formatted exactly the same as the example on http://dev/twitter.com/pages/auth, except of course it uses our consumer_key, oauth_nonce/timetamp etc. So the package we are sending looks perfect, we dumped it to Notepad.exe and copy / pasted in dev.twitter.com example to compare character by character and confirmed the only difference being the oauth_consumer_key, signature etc. YET, regardless of if we send it through MS XMLHTTP or convert it to a URL and copy / paste into a Web browser we still get the message Failed to validate oauth signature and token. We have exausted all the on line web blogs and resources we can find. We have used sites like http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/ to try to reconstruct the post and compare the results against what our application produces, and we are at a loss. It looks like we have the wrong consumer keys or something stupid, but beleive me we have copy / pasted those in as well to make sure there was no error. Remember we have used the parameters in your example on http://dev.twitter.com/pages/auth and the signature and resulting posts our software produces are the same as the examples on dev.twitter.com, so it looks like our software using our libraries is working correctly. Here are the two posts, with the example from dev.Twitter.com followed by the one produced by our site : Sample 1 - From our software but using values from http://dev.twitter.com/pages/auth OAuth oauth_callback=http%3A%2F%2Flocalhost%3A3005%2Fthe_dance %2Fprocess_callback%3Fservice_provider_id%, oauth_consumer_key=GDdmIQH6jhtmLUypg82g , oauth_nonce=QP70eNmVz8jvdPevU3oJD2AfF7R7odC2XJcn4XlZJqk, oauth_signature=8wUi7m5HFQy76nowoCThusfgB%2BQ%3D, oauth_signature_method=HMAC-SHA1, oauth_timestamp=12723230, oauth_version=1.0 Sample 2 - From our software using our consumer keys etc OAuth oauth_callback=oob, oauth_consumer_key=TY0Js5vMc04HNqmqIkNEnQ, oauth_nonce=ZcVmkYA3KYlVwN0kRaNHcsxiPbl4m16KZSHeyZfGF1v, oauth_signature=0XXxEzENnco46hxIrgIG%2FvfK9Wk%3D, oauth_signiture_method=HMAC-SHA1, oauth_timestamp=53697279, oauth_version=1.0 ALSO: I noted if we use the URL https://api.twitter.com/oauth/request_token?bla_bla_bla it also returns the same message so the API needs a little more diagnostic capability or perhaps you can provide a diagnostic tool or sandbox environment to help developers know whats wrong with the posts. What can we do from here... -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group:
Re: [twitter-dev] User Streaming API and use of OAuth from web browser
Well remember with Search you don't need to proxy from your server - instead the Search API supports JSONP so you can run it directly from the website. Regarding Toms proxy comment. I think Tom was suggesting it for the userstreams functionality. As userstreams require a long poll connection there are various other obstacles to overcome if it were to be run from within the browser directly. In addition, userstreams are for single user use and not suitable for web applications where multiple users interact. Instead the something like the Site Streams service (currently in beta) could be better suited. On Wed, Oct 6, 2010 at 5:18 PM, Matthew Terenzio mteren...@gmail.com wrote: So yes, I was correct (at least with search) that a web based solution is severely limited compared to a desktop. It will share usage among all it's users while a desktop client can spread the load amongst its users IPs. That stinks in my opinion. (I'm a web developer.) On Wed, Oct 6, 2010 at 7:44 PM, Matt Harris thematthar...@twitter.com wrote: All the information about rate limits can be found on our developer site: http://dev.twitter.com/pages/rate-limiting When talking about rate limits it is important to be clear about the API being used, as each has their own. For the REST API (requests to api.twitter.com) the limit is 150 requests per hour unauthenticated and 350 request per hour for an authenticated user. When you make an authenticated request the users rate limit is affected, not the IPs. The Search API has it's own rate limit based on the IP the request comes from. There is no authenticating for Search so all requests are IP rate limited. The Streaming APIs do not have rate limits in the same way. For the Streaming API the rate limit is controlled by the predicate limits (5,000 user ids etc) and the allowed sampling rate (1% etc). I hope that clarifies how the rate limits apply. Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Oct 6, 2010 at 3:28 PM, Matthew Terenzio mteren...@gmail.com wrote: On Wed, Oct 6, 2010 at 5:48 PM, Tom van der Woerdt i...@tvdw.eu wrote: I will indeed correct you: rate limits are based on account when using oauth. Really? Can someone second that. I re-read the documentation and it doesn't look like it to me. Are the IP limits ignored when you log in as a user. I know that is the case for the REST api in most cases but I'm talking about streaming and search. Tom On Oct 6, 2010, at 11:39 PM, Matthew Terenzio mteren...@gmail.com wrote: There would be one more issue which requires mentioning: JavaScript's Same-origin policy. You can't make a request directly to the Twitter API via JavaScript: you *will* need a proxy on your own server. Which seems to put web developers at a sever disadvantage for search and streaming APIs since rate limits are based on IP addresses. Meaning all my web users count as one whereas the rate limiting is spread out among all the users a given desktop client. I asked a while back about this and didn't get a response. It just don't seem fair. Seems impossible to build a web app of anything more than a couple hundred users if those users want to use search and or streaming. Or correct me. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources:
Re: [twitter-dev] User Streaming API and use of OAuth from web browser
Fair enough. On Wed, Oct 6, 2010 at 8:39 PM, Matt Harris thematthar...@twitter.comwrote: Well remember with Search you don't need to proxy from your server - instead the Search API supports JSONP so you can run it directly from the website. Regarding Toms proxy comment. I think Tom was suggesting it for the userstreams functionality. As userstreams require a long poll connection there are various other obstacles to overcome if it were to be run from within the browser directly. In addition, userstreams are for single user use and not suitable for web applications where multiple users interact. Instead the something like the Site Streams service (currently in beta) could be better suited. On Wed, Oct 6, 2010 at 5:18 PM, Matthew Terenzio mteren...@gmail.com wrote: So yes, I was correct (at least with search) that a web based solution is severely limited compared to a desktop. It will share usage among all it's users while a desktop client can spread the load amongst its users IPs. That stinks in my opinion. (I'm a web developer.) On Wed, Oct 6, 2010 at 7:44 PM, Matt Harris thematthar...@twitter.com wrote: All the information about rate limits can be found on our developer site: http://dev.twitter.com/pages/rate-limiting When talking about rate limits it is important to be clear about the API being used, as each has their own. For the REST API (requests to api.twitter.com) the limit is 150 requests per hour unauthenticated and 350 request per hour for an authenticated user. When you make an authenticated request the users rate limit is affected, not the IPs. The Search API has it's own rate limit based on the IP the request comes from. There is no authenticating for Search so all requests are IP rate limited. The Streaming APIs do not have rate limits in the same way. For the Streaming API the rate limit is controlled by the predicate limits (5,000 user ids etc) and the allowed sampling rate (1% etc). I hope that clarifies how the rate limits apply. Best @themattharris Developer Advocate, Twitter http://twitter.com/themattharris On Wed, Oct 6, 2010 at 3:28 PM, Matthew Terenzio mteren...@gmail.com wrote: On Wed, Oct 6, 2010 at 5:48 PM, Tom van der Woerdt i...@tvdw.eu wrote: I will indeed correct you: rate limits are based on account when using oauth. Really? Can someone second that. I re-read the documentation and it doesn't look like it to me. Are the IP limits ignored when you log in as a user. I know that is the case for the REST api in most cases but I'm talking about streaming and search. Tom On Oct 6, 2010, at 11:39 PM, Matthew Terenzio mteren...@gmail.com wrote: There would be one more issue which requires mentioning: JavaScript's Same-origin policy. You can't make a request directly to the Twitter API via JavaScript: you *will* need a proxy on your own server. Which seems to put web developers at a sever disadvantage for search and streaming APIs since rate limits are based on IP addresses. Meaning all my web users count as one whereas the rate limiting is spread out among all the users a given desktop client. I asked a while back about this and didn't get a response. It just don't seem fair. Seems impossible to build a web app of anything more than a couple hundred users if those users want to use search and or streaming. Or correct me. -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi
