# 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 6
# self = https://watcher.sour.is/conv/bpyurza
@prologic what's up with the twt order on your pod? see the timestamps 
here
@<~duriny https://envs.net/~duriny/twtxt.txt> I don't believe there is any "order" problem here. People make mistakes. This is why using a client is so important. This is _very likely_ (and I can probably prove it) a case of "Posted something too quick, ooops", "delete from feed", "let's re-post that again proeprly".
Problem is, by the time you do that, it's too late. A client (whether it be twtr, tt, jenny or yarnd) would have seen it already, hashed it, cached it and archived it.
@<~duriny https://envs.net/~duriny/twtxt.txt> I don't believe there is any "order" problem here. People make mistakes. This is why using a client is so important. This is _very likely_ (and I can probably prove it) a case of "Posted something too quick, ooops", "delete from feed", "let's re-post that again proeprly".
Problem is, by the time you do that, it's too late. A client (whether it be twtr, tt, jenny or yarnd) would have seen it already, hashed it, cached it and archived it.
does yarn display twts in the order they are cached? or does it assume that the order in the cache is correct and just run with it? looks like when @tkanos deleted their twt yarn cached it as being timestamped after my reply, so shouldn't the display still be ordered correctly?