@bender@twtxt.net This is basically the problem. Even if you wanted to there generally isn’t any state for feeds stored on behalf of the user, in other words, a read status.

I don’t know how we will handle the resetting of it, after reading…

I thought about it a few times, but I’ve never really been able to figure out a way of coming up with a viable solution to that.

@prologic@twtxt.net In tt, I have to press r to toggle the read status for each and every message. The disadvantage is that I have to mark all messages read explicitly, the advantage is that I have to mark all read explicitly, and hence no silly automation messes with me and causes wild surprises. But in theory it would be possible to automatically mark a message read when it is selected for three seconds or something like that. Not sure, though, how well any of that would work with a web UI.

@lyse@lyse.isobeef.org tracking read/unread is something that Yarn could benefit from. It has been thought before, just never gotten anywhere. Yarn just don’t keep track of those, it will be something that @prologic@twtxt.net will need to implement. Maybe if I keep poking him he will! 😂

@lyse@lyse.isobeef.org Yeah this is why I haven’t done it yet because I don’t know how to build it 🤣