Closed GoogleCodeExporter closed 8 years ago
GFeedLine does not get Twitter rate limits correctly.
This is a problem of the twitter-twisty with the introduction of the API 1.1
I opened the new issue #43.
> User should have an option to set the timeline refresh interval to a slower
value.
Why?
Original comment by yendo0206
on 14 Jun 2013 at 1:14
Ignore this issue. For large lists/feeds, Twitter updates were coming in so
fast that it was making it difficult to read the current tweet because
GFeedLine kept scrolling up to the top. Slowing down the update rate would
have been one solution, but if an explicit scroll lock will be implemented,
then this issue should be ignored.
Original comment by NerdySys...@gmail.com
on 14 Jun 2013 at 4:21
Thanks for your comment. I close this issue.
Original comment by yendo0206
on 14 Jun 2013 at 7:44
Original issue reported on code.google.com by
NerdySys...@gmail.com
on 12 Jun 2013 at 9:57