# 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/3nri5mq
{@https://lyse.isobeef.org/twtxt.txt>#ezmdswq} Since I lately see technically invalid twt subject hash tags for machine-parsable conversation grouping every now and then, I just taught the twtxt parser of my client to recover these (#1234567) subjects. Now they are grouped back into the proper conversations and do not form new root/single twts. Note, that the offending clients did not expand the hash tag in the subject to a proper (#<hash url>) form prior to publishing the twts. (Let's see whether my first markdown code will be expanded by twtd to a linked hash tag or not.)