# 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/enscsqa
@prologic (re API keys / limits) Yeah some sort of limit. But how would you do that? I think one way to do it is to use a API key, no? And what I mean by bad / buggy clients is in case I release an app that has a bug that it is DDOSing twtxt.net you could suspend the app until a fix is out.