Real time tweets/dents

Bug #520238 reported by Arturo Torres Sánchez
This bug affects 16 people
Affects Status Importance Assigned to Milestone

Bug Description

In the option “Minutes between refresh”, there should be an option to have tweets/dents updated in real time, since sometimes in a minute many tweets can arrive, and you just get lost

Revision history for this message
Greg Grossmeier (greg.grossmeier) wrote :

I don't believe this is permitted by twitter. If you request updates too frequently it will block you. See:

Setting as incomplete for now until someone can think of a way to get real time updates from twitter/identica without those services blocking gwibber.

Changed in gwibber:
status: New → Incomplete
importance: Undecided → Wishlist
Revision history for this message
Arturo Torres Sánchez (r2d2.art2005) wrote :

Well, you have 150 requests per hour, so you can make a request every 24 seconds, which is shorter than a minute. You can make an option to refresh every 30 seconds, and that would work fine.

Revision history for this message
Ryan Paul (segphault) wrote :

@Arturo: it's not that simple. The message, reply, and private streams each use one request. That means Gwibber makes three requests on a Twitter account per refresh. If you did a refresh every single minute, you would exceed the rate limit.

Twitter is currently developing its own streaming APIs for real-time messaging, but it's not fully functional yet and it doesn't appear to support single-user use cases at this time. When Twitter's streaming API has matured to the point where it's practical to use in Gwibber, we will adopt it. has an XMPP bridge that might possibly be able to facilitate real-time communication, but it will require further investigation. My plan is to use XMPP to determine when new messages are available and then force a refresh of the account. That's something that I won't be able to experiment with until after Lucid/Gwibber 2.30.

Revision history for this message
Joshua Lückers (joshualuckers) wrote :

Twitter now has a streaming API:
Does this mean this feature will be implemented in Gwibber?

Changed in gwibber:
status: Incomplete → New
Revision history for this message
Omer Akram (om26er) wrote :

sounds like an interesting feature ;)

Changed in gwibber:
status: New → Confirmed
Revision history for this message
David Collins (davidapc) wrote :

PCPro recently switched to Ubuntu for a day as an experiment and part of it's feedback on Ubuntu as a whole included details directly relevant to this bug:

"A few minutes with Gwibber also revealed that, when compared to something like Tweetdeck, it’s horrendously limited. Twitter can only update once every minute – an eternity for someone used to Tweetdeck’s real-time updating – and there’s no sign of multiple accounts, timed tweets or picture attachments, which are the kinds of features that I take for granted even in mobile apps these days."

From: Live blog: running PC Pro on Ubuntu | PC Pro blog

Revision history for this message
Xavier Guillot (valeryan-24) wrote :

I agree, when we foloow many users, 5 minutes between each update is far too long. Some clients like Hotot support real timeline update without problem with Twitter, it would be great to have the option to reduce this time.

Revision history for this message
Stephen Morrish (stephen-morrish) wrote :

This is now quite old, has their been any progress on this issue. I like the way Gwibber integrates with Ubuntu 11.10 but I need more frequent updates. 5 mins is killing me here... I have over 1350 followers and I need a twitter client that can keep up!

Revision history for this message
Kai Mast (kai-mast) wrote :

Any news on this? this is the biggest issue for me with gwibber...

Revision history for this message
Greg A (etulfetulf) wrote :

Excitingly, Twitter now has a "User Streams" API. Some highlights:

 - User Streams provides real-time updates of all data needed to update a desktop application display
 - Rate limits and latency are practically eliminated
 - Desktop developers can stop managing rate limits and use this new data to create an entirely new user experience

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers