# 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 4
# self = https://watcher.sour.is/conv/kutrrnq
@lyse I _think_ we should make recommendations for client implementations to adopt this behaviour as a recommended default for a good "UX" (_User Experience_) with the usual normal "I want to follow this feed and give it this alias" (_which is what most older clients did anyway_). This _may_ not apply to jenny/tt anyway as you guys; @movq and @lyse both probably handle following someone with multiple feed sources already 🤗
@lyse I _think_ we should make recommendations for client implementations to adopt this behaviour as a recommended default for a good "UX" (_User Experience_) with the usual normal "I want to follow this feed and give it this alias" (_which is what most older clients did anyway_). This _may_ not apply to jenny/tt anyway as you guys; @movq and @lyse both probably handle following someone with multiple feed sources already 🤗
@prologic Currently I just have to come up with a free nick. Usually I just suffix the second, third and so on feed with an underscore and a shortend domain. I reckon it would make sense to render mentions in the user's preferred nick. That of the viewing user that is. The mention of @<foo https://example.com/twtxt.txt> might for one user be shown as "@foo", but "@foo_expl" for the other and "@foo@example.com" for the next. So mentions would always be "rewritten" by what's configured. That sounds great. I have to implement that in tt, at the moment it just renders the original nick from the mention itself.
@prologic Currently I just have to come up with a free nick. Usually I just suffix the second, third and so on feed with an underscore and a shortend domain. I reckon it would make sense to render mentions in the user's preferred nick. That of the viewing user that is. The mention of @<foo https://example.com/twtxt.txt> ̀ might for one user be shown as "@foo", but "@foo_expl" for the other and "@foo@example.com" for the next. So mentions would always be "rewritten" by what's configured. That sounds great. I have to implement that in tt, at the moment it just renders the original nick from the mention itself.