# 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 1
# self = https://watcher.sour.is/conv/fx5p2oa
{@https://twtxt.net/user/prologic/twtxt.txt>#eufevfq} (#52smrra) Good question. Mostly because they form normal #hashtag(s) anyway. THe only _special_ thing about them is they also address a specific Twt -- i.e: Content Addressing. We _could_ make them link to the "Conversation" view, but then you' dloose the ability to search by that tag, say if a client screwed up, or twts dropped of the active cache, etc. Both the web app and mobile app know how to recognise a "reply to" and show the "Conversation" button and link to the right things. 🤷♂️