# 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 4
# self = https://watcher.sour.is/conv/w4ws3uq
I suspect the problem is that the content is updated. It looks like a design problem.
I suspect the problem is that the content is updated. It looks like a design problem.
@andros yes, that usually happens when twts get edited and we just made a _gentlemen agreement_ to avoid edits as much as possible (at least for the time being). But the thing is, *That* is not what's happening with my broken twts' hashes. Since I've bee mostly replaying to my own twts as a test and I know for sure that I haven't edited any. (I usually fork-replay instead of edit a twt when needed)
@andros yes, that usually happens when twts get edited and we just made a _gentlemen agreement_ to avoid edits as much as possible (at least for the time being). But the thing is, *That* is not what's happening with my broken twts' hashes. Since I've bee mostly replaying to my own twts as a test and I know for sure that I haven't edited any. (I usually fork-replay instead of edit a twt when needed)