# 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/dg2yhga
{@https://twtxt.net/user/prologic/twtxt.txt>#jcglc7a} @lazarus (#saz2moa) \n\n> Is twtxt.net setup to hash user’s passwords and emails? You have the ability for users to retrieve passwords but you mention you don’t keep emails. I’m curious as I have just realized that the ejabberd server I setup stores passwords as plain text and I need to research this more.\n\nPasswords are encrypted with scrypt.\n\nEmails are not stored, only a hash is. If you need to recover your account for any reason (_password reset_) you must supply the same email used on signup, if the hash matches the backend will happily send a reset token.