# 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/44ujn7a
@lyxal @petstorm Nope! Its not a problem, just unexpected! As long as it wasn't "malicious"; We just have to _think_ about how to handle this, for starters rate limiting _may_ help a bit, but also the @twtxt bot spits out FOLLOW, FEED, MENTION and WEBMENTION events, it _could_ learn how to "bundle" them, some kind of queue and debouncing. cc @dooven