gwibber-bugs team mailing list archive
-
gwibber-bugs team
-
Mailing list archive
-
Message #01154
[Bug 625863] Re: Gwibber puts the newest tweets at the top and oldest at bottom
** Changed in: gwibber
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/625863
Title:
Gwibber puts the newest tweets at the top and oldest at bottom
Status in Gwibber:
Fix Committed
Status in One Hundred Paper Cuts:
Triaged
Status in “gwibber” package in Ubuntu:
Triaged
Bug description:
Generally when I catch up on my Tweets either online or on Gwibber, I first must scroll down to find the place where I read the last tweet, look up to the next tweet, read down through that tweet, look up for the next tweet, read down through that one, look up, read down, look up, read down, up, down, up, down, up, down. As many as 20-30 times in a single session.
This is incredibly irritating, it essentially orders tweets in the opposite direction to which we really read. The only alternative is reading them out of order.
My proposal is that Gwibber records the last tweet you read when you
close it. Next time you open Gwibber, it loads at the top a tweet
maybe 5 tweets earlier to the one you last read, then loads all the
tweets after it sequentially downwards.
With this, you open Gwibber, start reading at the top, remind yourself
of the context of the last few tweets, and by reading downward you
update yourself on what has happened since without eye strain. If a
new tweet pops up, it'll be added to the bottom of the list, letting
you scroll down more, maybe sending an alert or changing the titlebar
to alert the user that there are new messages.
This will make reading tweets a far more natural process.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gwibber/+bug/625863/+subscriptions