# 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/mgmm7nq
{@https://twtxt.net/user/prologic/twtxt.txt>#qzlkxia} (#zcqwdaq) @vain This is true. Although since fetching a text/plain resource over web protocols is pretty damn "lightweight" as it gets, I don't have a problem with that per se. I'm still running all of twtxt.net twt.social jointwt.org (_amongst other proejcts_) all on my home infra. But the technical scale aspects are not the problem for me, it's the human social scale. I don't believe the later is "scalable" at all. Social Media _should_ remain small and controllable. That's not to say however that there can't be a global decentralised and distributed network of Twtxt feeds.