can this be private
@dendiz@yarn.dendiz.xyz Yes technically.
@dendiz@twtxt.net 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…
One use case is I would like to use yarn as a substitute for location checkins (i have a telegram bot which I share a location with that gets an image from google maps and posts the venue name with it). I use this to track places I’ve visited and rather have it private. I get the limitations of the protocol would prevent this.
@prologic@twtxt.net 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@twtxt.net 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@twtxt.net Actually that could work quite well. We could try that model to see how feasible it might be?
@eaplmx@twtxt.net 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@twtxt.net I agree just putting a pod behind a firewall and auth is simple enough 👌