💾 Archived View for rawtext.club › ~sloum › geminilist › 007701.gmi captured on 2024-03-21 at 15:39:42. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-09-08)
-=-=-=-=-=-=-
Krixano krixano at protonmail.com
Tue Dec 14 00:21:52 GMT 2021
- - - - - - - - - - - - - - - - - - -
Let me just be clear here, in response to this:
I can instead treat it as a weird
mutation of the protocol, and generally not worry about the whims of
a few implementors that ignore the spec in various ways. In this way, I
avoid the tyranny of a multitude of "loud minorities" that would have
been much more disruptive without a canonical specification of the
protocol.
1.) I agree with what is your most important argument, Clients and Servers should only be *expected* to adhere to the literalness of the spec2.) The intended protocol design is necessary for pointing out needed clarifications to the specification, and for people who want to adhere to the intended design of the spec.3.) Clients and Servers should therefore not be derided for adhering to the intended design even if it goes against the literalness of the spec, as the spec is possibly flawed or unclarified while still n development.4.) Clients and Servers that adhere to the literalness of the official spec are just as valid as clients that adhere to the intentions behind the spec when it comes to an unfinalized spec. *Both* are valid.
Christian Seibold