# 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/i2ce66a
@prologic I *hate* IPFS. Once or twice I've posted to github issues for that project, and they seem to be very dismissive of ideas they don't like. Mostly--it's impossible to delete anything from IPFS once you put it in there, and they have been hostile to any suggestion that they should fix that issue. I find it deeply irresponsible, since you can mount IPFS as if it were a filesystem, which makes it nearly 100% likely that someday, someone is going to put something very sensitive into IPFS by accident and then never be able to get it out again. It's almost certainly happened a bunch of times already. That feels much worse than Facebook-style centralization!
@abucci Kinds of weird they don't support deletions really, given that its effectively a distributed system.
@abucci Kinds of weird they don't support deletions really, given that its effectively a distributed system.
@prologic I think there's some kind of ideology at play there. The responses to suggesting things be deleteable tend to be "well, if you don't want it shared, don't put it in there" and "once you put something on the internet, it's there forever so 🤷". Which is BS obviously.
@abucci Yeah, I agree. The _only_ part of that statement that is true is in "decentralised" systems. For example, it is practically quite hard to delete Twts from a feed noce cached, fetched, archived, whatever across numerous clients in the Yarn/Twtt ecosystem. Why? Well because there is no one single point of control 😅
@abucci Yeah, I agree. The _only_ part of that statement that is true is in "decentralised" systems. For example, it is practically quite hard to delete Twts from a feed noce cached, fetched, archived, whatever across numerous clients in the Yarn/Twtt ecosystem. Why? Well because there is no one single point of control 😅