# 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/sezl6va
@screem I'm afraid, we'd have to build it 😅 Unless someone can point to me a viable solution that meets the requirements of Self Hosted, Decentralised, Operationally mature and Ease of use -- I haven't found one! 😂-- The _closest_ thing would be Signal, if it's backend weren't written in Java™ 😂
@screem I'm afraid, we'd have to build it 😅 Unless someone can point to me a viable solution that meets the requirements of Self Hosted, Decentralised, Operationally mature and Ease of use -- I haven't found one! 😂-- The _closest_ thing would be Signal, if it's backend weren't written in Java™ 😂
One possible way to use twtxt for private messages would be using http authentication, then it's private to anyone who's allowed to see the twtxt.txt file, otherwise the it returns 401 Unauthorized. That's not exactly an easy solution since both parties need to agree on authentication, and no client is set up for that, but it at least is self-hosted and decentralised :D