So… Here’s a thought…

If [Matrix] is built on a decentralised/distributed event syncing and a basic model of “Room”

And:

IRC is a centralised text based protocols with client to server and server to server networking and a basic model of “Channels” and “Users”

Then:

Yarn.social can build a “Chat” system based on the already existing and established decentralised/distributed syncing of feeds with a model of well umm feeds

🤔 🤣

@caesar@twtxt.net That is true (public), that’s by design, we’re very open about that. Transparency. microBlogging and sharing your thoughts and opinions is the same as full blogging on your website. It should be open and transparent.

However if we get get Encrypted Feeds off the ground (needs people to help contribute to the spec!) who knows? 🤷‍♂️ Maybe it’ll open other other interesting possibilities? 🤔

@prologic@twtxt.net I think it would be nice to have p2p entangled yarn would be nice. And with entangled I mean encrypted. “Entangled Yarns” how does that sound?

@carsten@yarn.zn80.net It’s certainly a possibility. Folks like @xuu@txt.sour.is @david@netbros.com and I are in support of this. It requires more eyes on the spec though to make sure we don’t royally fuck it up security-wise. Once we complete the spec, someone will have to build implementations for it 👌

Why do we need to build chat into yarn? Can’t you just run a matrix server and yarn pod on the same domain and be done with it?

@darch@twtxt.net I understand where you’re coming from, but we’re not doing anything drastic, but we should remain open to ideas and improvements, especially encrypted feeds. The only problem that can arise is that messaging can open up a can of worms and consume the project. That’s the risk, and we have to weight up the risks/benefits to the project and community overall 🤗