# 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 8
# self = https://watcher.sour.is/conv/wdmf56a
What say you @movq @lyse @eapl.mx / @darch @andros (_new client author_)? 🤔 Shall I PR this up?
What say you @movq @lyse @eapl.mx / @darch @andros (_new client author_)? 🤔 Shall I PR this up?
although I agree that it helps, I don't see completely correct to leave the nick definition to the source .txt. It could be wrong from the start or outdated with the time.

I'd rather prefer to get it from the mentioned .txt nick metadata (could be cached for performance).
So my vote would to make it mandatory to follow @<name url> but only using that name/nick if the URL doesn't contain another nick.
A main advantage is that when the destination URL changes the nick, it'll be automagically updated in the thread view (as happens with some other microblogging platforms, following the Jakob's Law)
although I agree that it helps, I don't see completely correct to leave the nick definition to the source .txt. It could be wrong from the start or outdated with the time.

I'd rather prefer to get it from the mentioned .txt nick metadata (could be cached for performance).
So my vote would to make it mandatory to follow @<name url> but only using that name/nick if the URL doesn't contain another nick.
A main advantage is that when the destination URL changes the nick, it'll be automagically updated in the thread view (as happens with some other microblogging platforms, following the Jakob's Law)
@probiotic I see nicks as a label, but otherwise superfluous. I can give whatever nick I want to anyone, as long as the feed exists (at least on Yarn).

So, if nick exist on feed, great, use it! if it doesn't, assign a random hash derived from whole URL as nick. Done. :-D
Or using the same twt hash method, but only for the URL, to generate the nick, if it doesn't exist, like so, @5vxo4ia
@bender That could work aactually...
@bender That could work aactually...