# 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 5
# self = https://watcher.sour.is/conv/zllu75a
@bender Nothing that isn't already a known side effect. Really it is up to clients to figure this out and have storage or caching mechanisms that can cope with diverging threads.
@bender Nothing that isn't already a known side effect. Really it is up to clients to figure this out and have storage or caching mechanisms that can cope with diverging threads.
@prologic but the problem is with Yarn too (the front end)! You know it has happened before a few times. Now the chances increase.
@bender This is true! (_as we spoke!_) It's okay though, I _think_ we'll eventually solve this as it becomes a thing that annoys us too much 🤣 I like your idea of having some optional, but recommended of handling edits. Like having something like (#d4acmcq was:zllu75a) just for an example. Extending the Subject Extension to support (#hash [was:<hash>])? 🤔
@bender This is true! (_as we spoke!_) It's okay though, I _think_ we'll eventually solve this as it becomes a thing that annoys us too much 🤣 I like your idea of having some optional, but recommended of handling edits. Like having something like (#d4acmcq was:zllu75a) just for an example. Extending the Subject Extension to support (#hash [was:<hash>])? 🤔