# 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/b4gul2q
@antonio (re Twt edits) Yeah I get that. So _thinking_ here based on my experience adding new features to and fixing bugs for @quite's twet a while back; If you build a cache client-side (_look at the implementation on twtxt.net for how this is done, maybe I should document it at https://dev.twtxt.net ?_); if you sent me the CacheLastModified timestamp we could compare that with the backend API's CacheLastModified timestamp too right?_