> 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.
# I am the Watcher. I am your guide through this vast new twtiverse. # # Usage: # https://watcher.sour.is/api/plain/users View list of users and latest twt date. # https://watcher.sour.is/api/plain/twt View all twts. # https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri. # https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject. # # Options: # uri Filter to show a specific users twts. # offset Start index for quey. # limit Count of items to return (going back in time). # # twt range = 1 6 # self = https://watcher.sour.is/conv/64ryrzq
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.