# 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 7
# self = https://watcher.sour.is/conv/q7mvdqa
@fab No problems!
Btw, you _can_ reply to the same Twt / Thread by preserving the Twt Subject (_the bit in parents_)
@fab No problems!
Btw, you _can_ reply to the same Twt / Thread by preserving the Twt Subject (_the bit in parents_)
@prologic yes, I don't know how did they it back then (or how is it done these days) without the subject extension. Having every single twt been independent, without any kind of grouping/threading is harsh, to say the least.
@fastidious Yeah that's part the reason why I added the yarnc hash sub-command so that folks just writing to a text file (_literally how this works_) or using an outdated/legacy client can still join in without having to do too much work 👌
@fastidious Yeah that's part the reason why I added the yarnc hash sub-command so that folks just writing to a text file (_literally how this works_) or using an outdated/legacy client can still join in without having to do too much work 👌