# 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 8
# self = https://watcher.sour.is/conv/zhvhd5a
Just that yarnd (_at least_) doesn't support creating such a custom TwtSubject, but it will reply and respect and thread one if one was constructed.
Just that yarnd (_at least_) doesn't support creating such a custom TwtSubject, but it will reply and respect and thread one if one was constructed.
@prologic based on @falsifian's findings, I don't believe this is quite accurate.
> "yarnd (_at least_) doesn't support creating such a custom TwtSubject, but it will reply and respect and thread one if one was constructed."
@prologic based on @falsifian's findings, I don't believe this is quite accurate.
> "yarnd (_at least_) doesn't support creating such a custom TwtSubject, but it will reply and respect and thread one if one was constructed."
Oh, and you can't imagine the level of control I am commandeering by restraining me from editing that previous "missing-one-backtick" twtxt. LOL!
Oh, and you can't imagine the level of control I am commandeering by restraining me from editing that previous "missing-one-backtick" twtxt. LOL!
@quark You are right, whilst it _technically_ works, its not well supported. Too much of the code would have to change to support that, and it's not worth the value.
@quark You are right, whilst it _technically_ works, its not well supported. Too much of the code would have to change to support that, and it's not worth the value.