Hi @prologic@twtxt.net I tried to understand the point of @lucidiot, and what he actually doesn’t like is not the extensions on itself (even if he prefers #hashtag instead of # < hashtag url> (that I understand)), because he also uses some extension.

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 https://brainshit.fr/read/242)

⤋ Read More

@tkanos@twtxt.net 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 https://brainshit.fr/read/242)

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@tilde.town fears (worries) about in the first place.

⤋ Read More

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.

⤋ Read More

Participate

Login to join in on this yarn.