# 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 6
# self = https://watcher.sour.is/conv/mfygfma
prologic
twtxt.net
View Thread
@andros Q: Why would you publish the private key? Hmmm 🧐
eapl.me
eapl.me
View Thread
well, I suggested that in https://eapl.me/timeline/conv/k2ob6bq

The idea was to help those following the spec in https://twtxt.dev/exts/directmessage.Html, to replicate the steps and validate whether your implementation gives the same result.

BTW, you could add a link to the spec in the echo web.
eapl.me
eapl.me
View Thread
I'm also thinking that some kind of tag might be needed to automatically hide twts from unknown extensions. For example our client doesn't support DMs and always shows the !<nick url><encrypted_message> syntax which is meaningless.
eapl.me
eapl.me
View Thread
not a big deal as I can skip those messages, but again, it's an extension, so older clients shouldn't be affected by a new feature.
prologic
twtxt.net
View Thread
@andros doesn't this defeat the point of public cryptography?
xuu
txt.sour.is
View Thread
@prologic twtxt DM is not a serious DM protocol.