# 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 12
# self = https://watcher.sour.is/conv/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.)
@lyse yeah we had to do the same thing as well!
@lyse yeah we had to do the same thing as well!
@lyse yeah we had to do the same thing as well!
Well, sadly the code blocks are messed up by the hash tag expansion… And my own client has also a rendering issue: https://lyse.isobeef.org/tt-broken-code-rendering.png Above tt, my client, down below the raw twt in vim.
@lyse (#ezmdswq) Looks good for me!
@lyse (#ezmdswq) Looks good for me!
@lyse (#ezmdswq) Looks good for me!
@prologic @xuu 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.
@lyse @prologic I think lex will do that too currently. Should be able to lock that down.
@lyse @prologic I think lex will do that too currently. Should be able to lock that down.
@lyse @prologic I think lex will do that too currently. Should be able to lock that down.