# 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/kewa2aa
{@https://twtxt.net/user/prologic/twtxt.txt>#s534mfa} (#lttsrtq) @jlj Yup. Any HTTP reverse proxy will do just fine! Do bare in mind however that twtd (_for now we call them Twt.social pods_) is designed to be memory optimized and as efficient as possible. You _could_ run it off a Raspberry Pi for example. I wanted to keep per-Pod running costs as low as possible, because one day (_when I have the time_) a monetization plan was to offer fully managed and hosted pods over at Twt.social for ~$1.99 USD/month per Pod (_only pod owner/operator pays, users join free_).~