# 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 11
# self = https://watcher.sour.is/conv/rwoptaa
@dendiz So this is a bit tricky. Yarn.social is based on Twtxt. Therefore feeds are expected to be published and hosted on public servers of some kind (supported are Gopher, Gemini and HTTP).
The only way to be private / invisible is blacklist the world and be dark or password protect feeds.
I have to ask though... What is your use-case here? What are you trying to solve? 🤔
We have toyed with the idea of encrypted feeds but it hasn't taken off so far...
@dendiz So this is a bit tricky. Yarn.social is based on Twtxt. Therefore feeds are expected to be published and hosted on public servers of some kind (supported are Gopher, Gemini and HTTP).
The only way to be private / invisible is blacklist the world and be dark or password protect feeds.
I have to ask though... What is your use-case here? What are you trying to solve? 🤔
We have toyed with the idea of encrypted feeds but it hasn't taken off so far...
@prologic a place I can see it works could be a private feed, only visible to other via invite or something, it could open the possibility of allowing more "privacy" on the way you publish or if someone wants to share sensible informations only with a select few, maybe using a line by line encryption?
But, personally, I see it as a possible way for bigger companies to get their eyes on yarn/twtxt but not in a good way. 🤔
@justamoment hmmm, perhaps the twtxt URL could be a UUID, like an unlisted link and you share that link with people you want to share access.
I do that a lot with Google Docs to share access to non critical documents.
Obviously if someone makes the URL public, anyone can see or edit the content.
@eaplmx Actually that _could_ work quite well. We _could_ try that model to see how feasible it _might_ be?
@eaplmx Actually that _could_ work quite well. We _could_ try that model to see how feasible it _might_ be?
@eaplmx another way could be to password protect the post and have it decrypted on access if privacy is too much of a concern, but I think it's an overkill, in that case having a password protected pod would be a better choice.
@justamoment I agree just putting a pod behind a firewall and auth is simple enough 👌
@justamoment I agree just putting a pod behind a firewall and auth is simple enough 👌