# 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/qt7bxsq
@antonio (re API keys / limits) Ahh yes I see what you mean. This is more compliated, but doable. I _believe_ what you are referring to is what we fall Application/Device tokens. I _think_ OAuth does this by design if I'm not mistaken. I _would_ just implement OAuth if I was actually familiar enough in "implemtnation detail" (_I understand the flows_); but anyway, maybe someone can come along and refactor API auth and/or add OAuth. Can you write up an issue re App tokens? I _think_ we'd need them to be "Pod Operator" managed? 🤔