# 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 3
# self = https://watcher.sour.is/conv/v3jjcqq
@asquare This is absolutely true! 💯 However the natural behavior of editing a post is the same as forking. So from a community perspective, we're _actaully_ okay with how that works in reality. I _think_ we're all getting a bit too hung up on "exactness". One of the things I think we're finding hard to reconcile is the fine line between a decentralised ecosystem and distributed system.
I want it very much to remain decentralised. That means Content-based addressing makes sense, because you can have integrity about what a Twt Hash means. I don't really mind if a thread gets forked because the OP was edited, that's actually how forking works anyway 😅
@asquare This is absolutely true! 💯 However the natural behavior of editing a post is the same as forking. So from a community perspective, we're _actaully_ okay with how that works in reality. I _think_ we're all getting a bit too hung up on "exactness". One of the things I think we're finding hard to reconcile is the fine line between a decentralised ecosystem and distributed system.
I want it very much to remain decentralised. That means Content-based addressing makes sense, because you can have integrity about what a Twt Hash means. I don't really mind if a thread gets forked because the OP was edited, that's actually how forking works anyway 😅
@prologic right, but "regular" forks have parents. An edited twt---currently---has none. Edits just create a new branch-less leaf.