# 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/elfggna
@antonio (re API keys / limits) Yeah that's kind of my point. I _think_ we can easily limit API reqest rates at an individual pod level, an operator is also free to put further measures in place of course at their network level, and our own hosted offering will also have similar infra. The other thing to think about is to make req/res as cheap as possible to limit the impact of an attack. All important factors. Of course having it behind Cloudflare also helps :D