# 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/rqg47uq
{@https://twtxt.net/user/prologic/twtxt.txt>#3i74uvq} @lyxal (#pdlvy3q) Yeah they are using their own "client" -- Or client here is a rather loose term, since Twtxt itself is just _really_ a twtxt.txt file hosted somewhere. What you you use here is a multi-user backend with API and a nice Mobile App (Goryon) to go along with. But under the hood it still manages a set of twtxt.txt files in /data/feeds/<username>. But no, you're right it would not be possible for any user to artificially go and post something in the future here, that would be silly, since you don't have _direct_ access to the file per se. Although...