# 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/fffxlua
@prologic (re API keys / limits) Yeah that is more complicated especially with other instances / pods now that you mentioned and I think about. An app that supports multiple instance will need to register itself with every Pod operator? That is ugly and complicated and defeats the purpose of an app support multi-pods. I need to understand it better too. Is there another way to do rate limits that you know of?