Loading Profile...
Previously read tweets not dimmed after relaunching Tweetie
Previously read tweets are not dim after quitting and relaunching Tweetie... or am I missing something?
41
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company thinks this is not a problem.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Has tweetie ever done this? I'm pretty sure it hasn't.... might be TwitterFon you're thinking of. -
Inappropriate?Yes - check the preferences. It's an option that defaults to off. -
Inappropriate?I think Tim means that, once you quit Tweetie, when you re-launch it, all tweets are undimmed, treated as if new, even if you read them in the *previous* session. And the preference option has no effect on this - relaunching Tweetie means all messages in the timeline are not dimmed, even though the "Blue Dot" doesn't appear.
For example, here's a screenshot of my timeline, where I've read everything.
And here's a screenshot of my timeline after quitting and relaunching - note that nothing is dimmed, even though Tweetie knows these aren't "new", because there is no badge.
Ideally, the "dimmed" state of a message would link directly to the "new" state of a message, so that "new" and "unread" were the same. Thus, a message would be new until you read it, and once read, would stay dimmed.
-
Inappropriate?There's a whole lot of data to serialize between sessions if you want to keep track of a dimmed/undimmed bit per tweet.
I chose the efficient route. Faster this way, at the expense of tossing some session data between launches.
On the plus side, Tweetie is so efficient that there really is never any reason to quit it. I made sure to use a few system resources as possible.5 Comments
Add a comment
This solves the problem
-
That's really funny. Perhaps it speaks to your technical skills, since virtually every other Twitter application handles this without problem and without the devs making excuses.
Your attitude is truly amazing. Thanks for making my decision. I'll be buying EventBox. -
I'm oddly OK with that answer. But in the absence of that, we need a way to mark everything as read. When I launch Twitterrific, it doesn't necessarily remember what I've read, but a quick command-k gives me a clean slate.
-
It wouldn't be that much data to store the last 24 or even 12 hours worth of 'read' statuses - a simple array of tweet_id=>true/false shouldn't be that slow. Also why not just make it an option (to store statuses) - then who cares if its slow?
Also perhaps Tweetie is that efficient, but the OS is not - and occasionally computers need restarting. -
A (possibly dirty) shortcut would be to store only the timestamp of the last read tweet. That way, you can dim that tweet and all older tweets on startup.
-
As a paid supporter of both iPhone and Mac versions, this is disappointing. This is one of those absolute-must-have features, and one of the main reasons I stopped using Twitterific.
-
Inappropriate?Yeah, I'm coming from Eventbox and this feature makes it loads easier to skim tweets.
I don't use the keyboard to navigate tweets in Tweetie so I can't actually get tweets to dim which is weird to me -- is the dev's expectation that everyone uses keyboard to navigate? I'm a scroll-wheel junkie. With the support for scrolling to the last unread tweet I'd expect/love some sort of Google Reader-style mark-as-scrolled-by option that dims entries as I go past them.
Couple that with read/unread tweet tracking between sessions and Tweetie becomes way friendlier.
I’m thinking about brushing my teeth but it's a lot of work.
-
-
Inappropriate?I'm not entirely sure I understand why a reasonably-limited number or tweet IDs (say, 300) couldn't be cached locally with a flag that denotes whether they've been read or not. Of course, you're the programmer and I'm not...I don't want to diminish your expertise. But the whole "mark all as read," as implemented in Tweetie, has extremely little value and comes off as "buggy" to non-developers.
For what it's worth, this is a much more interesting problem since the advent of Prowl. It seems like a bug when, every time I launch Tweetie, I get notified of 20 new Mentions and DMs. Keeping Tweetie running constantly, while no doubt "efficient," is also "sweeping the issue under the rug." I, for one, would like to minimize non-work distraction during my workday.
Hence, I'm posting to GS on 11:44am on a Thursday.
