# 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/awruajq
{@https://lyse.isobeef.org/twtxt.txt>#s65rwca} @prologic @xuu (#ezmdswq) Cool, lextwt to the rescue! With retwt it looks like this: https://lyse.isobeef.org/retwt-broken-code-rendering.png My own twtxt parser handles subjects too freely and treats the first parentheses – no matter where in the twt the appear – as subjects which happens to be my example subject hash tag in markdown inline code. Since I hide the subject to save space, the code block is empty.