# 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 12
# self = https://watcher.sour.is/conv/5t4ggxq
@prologic No worries! And that makes sense regarding the angle brackets, force of habit for me just using them wily nily in WYSIWYG editors. But anyway, it helped expose a bug 😎
@eldersnake You _actually_ helped uncovered two bugs, but the later is a bit hard to explain. Essentially around supporting "forked" conversation. Say you write an OP, then I reply to it. Then you go change your OP. This _should_ fork the already-in-play conversation. But _before_ the "Conversation" button would show up on the already-in-play conversation because the backend wasn't checking the Archive for the OP Hash's validity (_which it is because the pod archives everything it sees_). You _basically_ have ~5mins to change your mind cross-pod.~
@eldersnake You _actually_ helped uncovered two bugs, but the later is a bit hard to explain. Essentially around supporting "forked" conversation. Say you write an OP, then I reply to it. Then you go change your OP. This _should_ fork the already-in-play conversation. But _before_ the "Conversation" button would show up on the already-in-play conversation because the backend wasn't checking the Archive for the OP Hash's validity (_which it is because the pod archives everything it sees_). You _basically_ have ~5mins to change your mind cross-pod.~
@eldersnake You _actually_ helped uncovered two bugs, but the later is a bit hard to explain. Essentially around supporting "forked" conversation. Say you write an OP, then I reply to it. Then you go change your OP. This _should_ fork the already-in-play conversation. But _before_ the "Conversation" button would show up on the already-in-play conversation because the backend wasn't checking the Archive for the OP Hash's validity (_which it is because the pod archives everything it sees_). You _basically_ have ~5mins to change your mind cross-pod.~