# 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/4n4ppya
@tkanos No problems mate! Just be aware that it's not actually possible to "remove one" anyway when you have little to no control over who follows you. In other words, once published and pulled, consider your Twt published 😂 That's how content addressing works 😅
@tkanos No problems mate! Just be aware that it's not actually possible to "remove one" anyway when you have little to no control over who follows you. In other words, once published and pulled, consider your Twt published 😂 That's how content addressing works 😅
@prologic I'm curious about this. Surely the implication of a twtxt file being self-hosted (unless you're using someone else's pod...) is that I control its content; I can delete/edit what I want. Sure, someone else might have saved/cached it, but the same would apply to any web page: if it's on my server, I can delete the canonical version. Doesn't mean every trace is immediately/permanently gone from the web, but any remaining cached versions are just outdated cache artifacts. Am I wrong?