# 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/kdq5apa
(#4h6nt7a) In other words, there isn't anything _specifically_ wrong with the Twtxt spec (+extensions), but if you for example use a client and ...
In other words, there isn’t anything _specifically_ wrong with the Twtxt spec (+extensions), but if you for example use a client and server combination that never considered the User-Agent header and check logs or intercept requests for your feed, than you end up missing an important part of the whole flow (unless you are of course deliberating ignoring that, e.g: 1-way feeds, news feeds, ... ⌘ Read more