# 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 9
# self = https://watcher.sour.is/conv/ybid3lq
@zags i guess not, since the hash is calculated from the content of the post
@logout Probably not. Clients will probably not pick up your change, I guess. 🫤
@logout Probably not. Clients will probably not pick up your change, I guess. 🫤
@logout Probably not. Clients will probably not pick up your change, I guess. 🫤
@logout Probably not. Clients will probably not pick up your change, I guess. 🫤
@logout Yea we use content addressable hashing so editing after the fact -- especially with replies in the wild -- will cause forks 😅
@logout Yea we use content addressable hashing so editing after the fact -- especially with replies in the wild -- will cause forks 😅
@logout Yea we use content addressable hashing so editing after the fact -- especially with replies in the wild -- will cause forks 😅
@logout Yea we use content addressable hashing so editing after the fact -- especially with replies in the wild -- will cause forks 😅