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)
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)
> even if he prefers #hashtag instead of # < hashtag url> (that I understand))
We changed this long ago. The spec has even been updated since.
> even if he prefers #hashtag instead of # < hashtag url> (that I understand))
We changed this long ago. The spec has even been updated since.
> even if he prefers #hashtag instead of # < hashtag url> (that I understand))
We changed this long ago. The spec has even been updated since.
> even if he prefers #hashtag instead of # < hashtag url> (that I understand))
We changed this long ago. The spec has even been updated since.
> even if he prefers #hashtag instead of # < hashtag url> (that I understand))
We changed this long ago. The spec has even been updated since.
> 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 fears (worries) about in the first place.
> 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 fears (worries) about in the first place.
> 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 fears (worries) about in the first place.
> 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 fears (worries) about in the first place.
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.
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.
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.
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.