Username not working, anything to do with Twitter deprecating all kinds of requests?

[pipkoli]

Hi there,

I'm using this script for some of my websites. It works fine and has al lot of options. However, since a couple of days, the scripts where I want to publish a user timeline are not displaying tweets anymore. The queries are still working.
Does this have anything to do with the fact that Twitter is not supporting some kinds of requests anymore? https://dev.twitter.com/docs/deprecations/spring-2012
I think so, but my knowloedge of the matter is too small te be sure. And if so, will you be changing this script to be compatible whit Twitters new requirements or should I find another?

Thank you very much.
Martine

[purcell]

You may be experiencing rate limiting issues, or a fault on the Twitter end. To help me figure out which, please provide an example of the options you're passing to tweet() to fill your twitter widget.

There are indeed upcoming changes to the twitter API which may or may not mean that jquery.tweet.js will have to be abandoned (see #264), but the examples provided with Tweet (and at http://tweet.seaofclouds.com/) still all work fine for me, so there's no vital API which has recently been removed.

[purcell]

Also, if you'd like to track this down further yourself, you can use Firebug or the Chrome Developer Tools to examine the http response sent by Twitter; find the response in the Network tab, and the headers/body of the response will tell you if you've been rate-limited.

[bodrovis]

Actually, some examples on the http://tweet.seaofclouds.com/ are not working anymore :(

[bodrovis]

But wait, it is fine again. For about 20 minutes i couldn't retrieve tweets by username and some examples were not working either. Maybe some problems on Twitter's side.

[purcell]

@bodrovis Sounds like rate limiting. It's common to experience this if you're a web developer, because every time you reload the page, your tweet widget will make another request. The rate limit is 150 req/hr per client.

(Closing this issue because no more feedback has been received from the submitter.)