# 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 10
# self = https://watcher.sour.is/conv/pne2f3a
no wonder he cut off API access and added rate limit.
@stigatle Oh boi. This just keeps getting worse and worse. I _think_ we're going to have to seriously considering going fully e2e encrypted Twtxt here 😅
@stigatle Oh boi. This just keeps getting worse and worse. I _think_ we're going to have to seriously considering going fully e2e encrypted Twtxt here 😅
@stigatle Oh boi. This just keeps getting worse and worse. I _think_ we're going to have to seriously considering going fully e2e encrypted Twtxt here 😅
Yeah, that would be nice! At least when you think about the way things are going these days..
@abucci @xuu and I have already experimented with doing something like this a while back, part of that experimentation helped actually build out what is Salty IM today. The original RFC for Encrypted Feeds and Signatures
@abucci @xuu and I have already experimented with doing something like this a while back, part of that experimentation helped actually build out what is Salty IM today. The original RFC for Encrypted Feeds and Signatures
@abucci @xuu and I have already experimented with doing something like this a while back, part of that experimentation helped actually build out what is Salty IM today. The original RFC for Encrypted Feeds and Signatures