# 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 8
# self = https://watcher.sour.is/conv/qi25fna
@prologic I have thought about this because even though it doesnβt happen often, when it does it bothers me greatly. I havenβt found a solution. How about you? What could be done to avoid this from happening?
I know we have been over this in more than one occasion. Ideas about editing timeouts, or not allowing to edit/delete came up, but were quicky discarded as absurd.
@fastidious That's easy! Peer review each twt before actually publishing. :-D
@lyse I kid you not, I try to be so careful when I write, or reply to, a twt!
I propose we use a blockchain, and permanently write twts to it, so no changes are possible. When a twt gets a reply, the parent (spelling mistakes, typos, etc.) will always be there. To post a twt to such blockchain one needs to first mine "yarnnero", the chosen, and forked, err, created from scratch cryptocurrency.
@fastidious +1 ...Now just a way to come up with the $20 per twt to store the data.
@fastidious +1 ...Now just a way to come up with the $20 per twt to store the data.
ROFL ππ€£ππ€£ππ€£ Bahahahahaha πππ€£
ROFL ππ€£ππ€£ππ€£ Bahahahahaha πππ€£