# 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 2
# self = https://watcher.sour.is/conv/yn7uonq
@prologic Exactly, I was thinking either "poisoned" cache or OSI level 8 issue. Have you already written a tool in the meantime to look into the cache? That would certainly help to pinpoint the exact issue. However, in case of a cache thing, I'm not sure what to do about that, to prevented it from happening again in the future. I don't think that can really be solved. Poisoned cache seems likely, I'd say.
Very nice, that's cool! I have to check it out now.