We just pushed an update tonight that makes read/unread in messages list view 100% accurate across browsers and sessions.

The only downside is that everything will be marked as unread starting now. But moving forward Basecamp will remember what’s been read and unread. Because the new way (stored on our server) is completely different from the old way (history stored on your browser) there was no way to keep the data from the old way.

We hope you like the improved accuracy.

Good move. Thanks.

awesome.. thanks.

Thanks Jason. It personally didn’t bother me, but people in the other thread about this were just…hostile…

“There was no way to keep the data from the old way.”

How about reading in my cookies and updating the database the first time I log in?

That probably would NOT have worked, as you never used cookies. And I’m a jackass.

Id like to suggest a mark-all-messages-read function/link, if its possible.

“How about reading in my cookies and updating the database the first time I log in?

That probably would have worked.”

It never used cookies.

Oooh, that’s right. They were just using the visited link stuffs. Fixed.

Thanks for the efforts 37S—makes the feature a lot more useful. edit: What’s up with the blue, no-icon items? Is that on purpose (is it bad that I have to ask?)

I was having a similar issue, and cache clear fixed it up.

Yeah, clear your cache. Looks like a little stylesheet corruption.

Cleared several times, quit Safari, rebooted. Still there. Oh well. Manageable.

Yep, this is happening to me too in FF2.0.0.4:

Browser cache cleared and all the usual things done.

Can’t replicate it in Camino or Safari though, very strange.

Happens to me in FF 2.0.0.4 when I click the back arrow but sorts itself out if I click refresh or clear the cache.

Looks like it was a CSS corruption/conflict after all. Working fine now!

Melvin wrote in the other thread:

I wonder how you’re able to do it on your forums so well and not the messages area? Is it just the volume of messages?

I didn’t get a chance to reply before the thread was locked but I wanted to. The forums are using Beast software, which Rick Olson and I co-wrote… and 37s is right that’s it’s a royal pain to track read flags on messages in the database individually. Beast “cheats” by using a combination of your last login time and your browser session to store what you’ve “read” since your last login… anything prior to your last login is already considered read. And while your browse your last login time is updated in the database but your session continues to remember what was new when you first logged in… I’m probably not explaining it the best, but it’s pretty slick.

A little more complex than 37s first implementation but falling far short of their final solution… which I assume is an actual read flag of some sort in the database for every user for every post…