# 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 10
# self = https://watcher.sour.is/conv/sbg7p7a
(replyto http://darch.dk/twtxt.txt 2024-09-15T12:50:17Z) Hmm, but yarnd also isn't showing these twts as being part of a thread. @prologic you said yarnd respects customs subjects. Shouldn't these twts count as having a custom subject, and get threaded together?
@falsifian based on Twt Subject Extension, your subject is invalid. You can have custom subjects, that is, not a valid hash, but you simply can't put anything, and expect it to be treated as a TwtSubject, me thinks.
@falsifian based on Twt Subject Extension, your subject is invalid. You can have custom subjects, that is, not a valid hash, but you simply can't put anything, and expect it to be treated as a TwtSubject, me thinks.
It _actually_ has treated this as a thread, but it gets a bit weird, because we thread based on the content address of a root twt.
It _actually_ has treated this as a thread, but it gets a bit weird, because we thread based on the content address of a root twt.
So yeah no, whilst it _technically_ works, neither jenny nor yarnd support it very well. Only at a very basic level.
So yeah no, whilst it _technically_ works, neither jenny nor yarnd support it very well. Only at a very basic level.