Comment 9 for bug 709865

Sorry, I have not noticed your answer until now.

I don’t know a way to reproduce this with any version of gwibber, due to the fact that gwibber fetches only the messages of the last few days/hours. If you can tell me how to configure gwibber to fetch tweets from a specific period of time instead of the most recent ones I will try it out. Otherwise this bug is hard to reproduce as I stated in the description because it’s connected to something in one specific tweet.

Perhaps there is a way to reproduce this tweet (http://twitter.com/#!/urbanrivals/status/30986263850913792) so that it recreates the error. But unfortunately I don’t have the time to look into the twitter API and test this out.