(#jxnfaoa) @tkanos > even if he prefers #hashtag instead of # < hashtag url> (that I understand)) We changed this long ago. The spec has even been updated since.

(#jxnfaoa) @tkanos > even if he prefers #hashtag instead of # < hashtag url> (that I understand)) We changed this long ago. The spec has even been updated since.

(#jxnfaoa) @tkanos I have to ask... > Actually what he doesn’t like, is the fear that you may extend the protocol and once it’s adopted by everybody, make it proprietary and oblige everybody to only uses your platform. (here ) How?! 🤦‍♂️ How in the hell do you turn an open spec (Twtxt and Extensions) into something "proprietary". They are already open sourced and licensed under the terms of the MIT License. They ar archived by the Internet Archive. There is no way to go back on this. Many clients are also MIT licensed or similar as well (`yarnd` specifically is AGPLv3 but for a reason). The simple fact is this... (And the nice thing), Twtxt clients of any kind are really just that, a client. There is no protocol (never has been), only a specification and extensions. You just host a feed using any HTTP, Gopher or Gemini server. So therefore Twtxt / Yarn is 100% **decentralised** -- in the truest sense. It is _not_ possible to do what @lucidiot fears (worries) about in the first place.

(#jxnfaoa) Or rather that is to say... How the hell do you make a truely decentralised ecosystem "proprietary" in the first place?! 🤦‍♂️ I cannot think of any example of this -- This is why _most_ (if not all?) profitable "social media"(s) are all "centralised" systems or "distributed networks", so they retain control. Yarn.social / Twtxt (the ecosystem) has very little to no control over anything. In fact the extensions themselves were a formalisation of what the community was (as you clearly point out) doing and still is doing.

(#jxnfaoa) @prologic Don't ask me, I just translated what he said, and what was his thinking, because you wanted to know.