# 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 1
# self = https://watcher.sour.is/conv/46kculq
{@https://twtxt.net/user/prologic/twtxt.txt>#eipfmcq} @xuu (#jmgdkdq) That's the tricky part, yeah. Most people don't have a clue when it comes to privacy let alone encryption. One idea I had was to use NaCL crypto and store an identity key pair server-side on Twt.social pods encrypted with PBKDF2 against the user's password. That way at least we can form some kind of cryptographic "identity" without having to involve the users that much, it just works™