Gwibber is exceeding the Twitter rate limit (HTTP Error 400: Bad request)

"HTTPError: HTTP Error 400: Bad Request" - I see this too for Twitter. Gwibber had been working fine until a few days ago. Breakage in a recent update, perhaps?

Having said that, my current version is Gwibber 0.9.1 which is different to the version for the reporter above - perhaps breakage in a related library?

I have

   deb http://ppa.launchpad.net/gwibber-team/ppa/ubuntu intrepid main

in my sources and keep up to date.

I note that other Twitter clients (e.g. Twitux) are working OK.

I can confirm that, I think there's two day I can't recive updates from twitter and check log error a got Bad Request 400 error too.
I'm using intrepid.
I think the error, it's because of recent twitter update.

testing on gTwitter does not work too.

The problem is that Twitter changed their API and it broke Gwibber. A fix was released a few days ago and it should make its way into jaunty soon.

@davee: The gwibber-team PPA hasn't been updated yet since this fix was released.

Olá davee e a todos.

On Sunday 12 April 2009 10:15:20 davee wrote:
> I note that other Twitter clients (e.g. Twitux) are working OK.

I'm using daily and I see this too.
But another twit client is affected in exactly the same way and duration. when gwibber is 400 µblog-purple is also.
When one comes back, so does the other. This sounds more like a twitter prob then gwibber.

$ apt-cache policy gwibber
gwibber:
  Installed: 1.0.1~bzr286-0ubuntu1~daily1
  Candidate: 1.0.1~bzr286-0ubuntu1~daily1
  Version table:
 *** 1.0.1~bzr286-0ubuntu1~daily1 0
        500 http://ppa.launchpad.net jaunty/main Packages
        100 /var/lib/dpkg/status
     0.9.1~bzr255-0ubuntu1~fta1 0
        500 http://ppa.launchpad.net jaunty/main Packages
     0.8-0ubuntu3 0
        500 ftp://darkstar.ist.utl.pt jaunty/universe Packages
        500 ftp://archive.ubuntu.com jaunty/universe Packages

--
Hi, I'm BUGabundo, and I am Ubuntu (whyubuntu.com)
(``-_-´´) http://LinuxNoDEI.BUGabundo.net && Ubuntu LoCoTeam Portugal http://ubuntu-pt.org
Linux user #443786 GPG key 1024D/A1784EBB

this bug was incorrectly marked as a duplicate.

however, it is a result of the fix imposed on us by bug 358341

basically Gwibber was (one of many) clients cheating the system by using POST requests for the timeline(s). Twitter were only measuring GET requests against the rate limit so Gwibber was able to get away with whatever it wanted.

currently you are allocated 100 requests an hour and you can query your current remaining number of hits from the API yourself and when your count was last reset to 100:
{{{
$ curl -u username http://twitter.com/account/rate_limit_status.json
{"hourly_limit":100,"reset_time":"Sun Apr 12 23:32:59 +0000 2009","reset_time_in_seconds":1239579179,"remaining_hits":57}
}}}

so if you have your refresh time set to 1 minute, then just Messages & Replies will trigger your count in 50 minutes

if you have any gwibber:user profile tabs, hash tags or search tabs open these will also count towards your limit so you'll run out even quicker

unfortunately have to mark this as invalid as its not a Gwibber problem but a Twitter API problem upstream

p.s. the rate limit is per authenticating user credentials, so if you are running any other Twitter apps elsewhere (e.g., running Gwibber on two machines at once) they will be sharing the same count

on second thoughts, re-opening this bug, perhaps we need to consider adding some better user feedback when the rate is exceeded (as it is likely to happen quite often)

For people's reference, this is the API change that causes us (and all other apps) to be rate limited now, when we weren't before

"From Twitter API Changelog (http://apiwiki.twitter.com/REST%20API%20Changelog)

# Fixed (REST): Methods documented as requiring GET were allowing POST and not counting the rate limit correctly. These methods now require GET and return an error message if POST is used."

@ Dominic: The bug reporter is using Gwibber 0.8 from the jaunty repo which is still using POST requests.

Tengo el mismo mensaje de error, estoy usando ubuntu 9.04 y gwibber del repositorio lp:wgibber.

Twitter has been broken four days for me.

I don't believe 'rate limiting' because I logged in (gwibber 0.8 I believe) for the first time in three days and immediately started getting "400: Bad Request" errors from twitter. Immediately as in 'right away, on the very first request in three days'

I've just upgraded to gwibber 1.0.2 and now I'm getting 401: bad authentication" from both twitter and identica.

Any suggestions?

Are you sure you've got your authentication details correct? Bad authentication is only likely to come up if the details are incorrect. Re-entering them into the relevant configuration boxes should fix this.

@ zcat: Gwibber 0.8 had Gnome keyring support and in version 1.0.2 it is removed and because of this, your password isn't stored in gconf anymore. Edit your password in the manage account dialog and all should be fine. You might have to wait a while to be able to login to twitter again as they temporally block logins after a number of unsuccessful login attempts.

Appears fixed in Gwibber 0.9.2 from the Intrepid PPA, downloaded/installed this morning. Thanks chaps :-)

I'm new to gwibber + twitter and just installed gwibber 0.9.2 from the intrepid ppa but I'm getting this "HTTP Error 400: Bad Request" for my twitter account. Since it seems I have the latest gwibber version, why would I still be getting this problem?

gnomefreak@Development:~/mozilla-builds/jaunty/2.0/work/ubuntu-2.x/debian/patche
s$ gwibber
/usr/lib/python2.6/dist-packages/gwibber/microblog/support/facelib.py:47: DeprecationWarning: the md5 module is deprecated; use hashlib instead
  import md5
console message: @1: ReferenceError: Can't find variable: addMessages
console message: @22: ReferenceError: Can't find variable: setGtkConfig
console message: @1: ReferenceError: Can't find variable: setAccountConfig
console message: @1: ReferenceError: Can't find variable: addMessages
console message: @22: ReferenceError: Can't find variable: setGtkConfig
console message: file:///usr/share/gwibber/ui/themes/default/jquery.js @22: SyntaxError: Parse error
console message: file:///usr/share/gwibber/ui/themes/default/theme.html @150: ReferenceError: Can't find variable: $
console message: file:///usr/share/gwibber/ui/themes/default/jquery.js @1: SyntaxError: Parse error
/usr/lib/python2.6/dist-packages/gwibber/client.py:774: GtkWarning: gtk_tree_model_filter_get_value: assertion `GTK_TREE_MODEL_FILTER (model)->priv->stamp == iter->stamp' failed
  errorwin.show_all()
/usr/lib/python2.6/dist-packages/gwibber/client.py:774: Warning: g_object_set_property: assertion `G_IS_VALUE (value)' failed
  errorwin.show_all()
/usr/lib/python2.6/dist-packages/gwibber/client.py:774: Warning: g_value_unset: assertion `G_IS_VALUE (value)' failed
  errorwin.show_all()
/usr/lib/python2.6/dist-packages/gwibber/table.py:35: GtkWarning: gtk_tree_model_filter_convert_iter_to_child_iter: assertion `filter_iter->stamp == filter->priv->stamp' failed
  i = tree.filter.convert_iter_to_child_iter(iter)
/usr/lib/python2.6/dist-packages/gwibber/table.py:17: GtkWarning: gtk_list_store_get_value: assertion `VALID_ITER (iter, list_store)' failed
  return self[iter][0]
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/table.py", line 36, in custom_handler
    o = tree.filter.get_model().get_obj(i)
  File "/usr/lib/python2.6/dist-packages/gwibber/table.py", line 17, in get_obj
    return self[iter][0]
TypeError: unknown type (null)
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/apport_python_hook.py", line 93, in apport_excepthook
    os.O_WRONLY|os.O_CREAT|os.O_EXCL), 'w')
OSError: [Errno 13] Permission denied: '/var/crash/_usr_bin_gwibber.1000.crash'

Original exception was:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/table.py", line 36, in custom_handler
    o = tree.filter.get_model().get_obj(i)
  File "/usr/lib/python2.6/dist-packages/gwibber/table.py", line 17, in get_obj
    return self[iter][0]
TypeError: unknown type (null)
/usr/lib/python2.6/dist-packages/gwibber/client.py:774: GtkWarning: gtk_tree_model_filter_iter_next: assertion `GTK_TREE_MODEL_FILTER (model)->priv->stamp == iter->stamp' failed
  errorwin.show_all()
/usr/lib/python2.6/dist-packages/gwibber/client.py:774: GtkWarning: file /build/buildd/gtk+2.0-2.16.0/gtk/gtktreeview.c: line 6142 (do_validate_rows): assertion `gtk_tree_model_iter_next (tree_view->priv->model, &iter)' failed.
There is a disparity between the internal view of the G...

Does anyone else see the following using the command given?

gnomefreak@Development:~/mozilla-builds/jaunty/2.0/work/ubuntu-2.x/debian/patche
s$ curl -u USER http://twitter.com/account/rate_limit_status.json
Enter host password for user 'USER':
{"remaining_hits":100,"hourly_limit":100,"reset_time":"Tue Apr 14 14:08:09 +0000 2009","reset_time_in_seconds":1239718089

Dominic, do "searches" count as hits too?

@markb Did you do this: https://bugs.launchpad.net/gwibber/+bug/359885/comments/14

@jonathan Well no matter what I did yesterday it stayed broke. Today I fired up gwibber after getting your comment and it seems to be working fine? I didn't change anything other than wait for 16 hours. Didn't re-enter my password anywhere either. Thanks for caring ... ;)

@gnomefreak replace USER with your username

Same problem:
Ubuntu Jaunty
gwibber:
  Instalados: 0.9.2~bzr263-0ubuntu1~jaunty
  Candidato: 0.9.2~bzr263-0ubuntu1~jaunty
  Tabla de versión:
 *** 0.9.2~bzr263-0ubuntu1~jaunty 0
        500 http://ppa.launchpad.net jaunty/main Packages
        100 /var/lib/dpkg/status
     0.8-0ubuntu5 0
        500 http://es.archive.ubuntu.com jaunty/universe Packages

Is this still an issue with gwibber 2.29.94?

for me now it's working, I think this is outdated bug.