# 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 10
# self = https://watcher.sour.is/conv/755ufoq
@bender Haha, no worries. I do like that you enjoyed your real life and not wasted it online. :-)

But I'm wondering how you discovered it a week later. Are you somehow regularly checking complete recent feed histories?
@lyse Probably used one of the filters? 🤔
@lyse Probably used one of the filters? 🤔
@lyse when come around, I normally check, and get busy just reading, under "Discover", and often forget to even check mentions. Since there is nothing on "Mentions" telling me there are some pending to be read (at the very least, a tiny dot, or something), if often gets ignored. 😅
@lyse when I come around, I normally check, and get busy just reading, under "Discover", and often forget to even check mentions. Since there is nothing on "Mentions" telling me there are some pending to be read (at the very least, a tiny dot, or something), if often gets ignored. 😅
@bender A tiny dot you say eh? 🤣
@bender A tiny dot you say eh? 🤣
On the "Mentions" topic, maybe @prologic can do something about it? What exactly is up to him, and the capabilities present. Perhaps simply bolding Mentions if there if are unread ones? I don't know how we will handle the resetting of it, after reading...
@bender 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.
@bender 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.