# 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/ujnrfma
@prologic as a fan of encryption and privacy, I think signing and encrypting messages are not only desirable but needed, I'd like to see it in action. The downside, as some have discussed is the UX pains for those clients not supporting the extension.
On the other hand, Saltpack or PGP are great for messaging/email, I understand twtxt is not for that. In a similar way, Twitter allows private messaging in the same App, but in a different section. Same with most Social Services.
So I actually believe the UX can be quite simple here. And for your 2nd point of clients that don't support the extension, you could use different feeds for different purposes and separate out your "encrypted social" activities.
So I actually believe the UX can be quite simple here. And for your 2nd point of clients that don't support the extension, you could use different feeds for different purposes and separate out your "encrypted social" activities.