[spec] Limit valid encodings of text/gemini to UTF-8

[Philip Linde]

On Mon, 28 Dec 2020 14:25:29 +0100
Côme Chilliet <come at chilliet.eu> wrote:

> The main reason I see for authorizing other encodings is to be future proof.
> 
> When people designed old protocols they thought ASCII was here to stay.

On the other hand, when people adopted Unicode 5.0, they did so fully
aware that there would likely be a Unicode 6.0, 7.0, 8.0 etc. Unicode
is future proof in the sense that it includes a process for updating
itself. The comparison to ASCII in that sense does not consider the
entirely different approaches these standards take. Where ASCII is
fixed and limited to a relatively tiny set of characters, Unicode is
deliberately open to amendment.

> So, I think we should learn from the past and not set in stone that all files must use utf-8, maybe something else will arise and be better for some unsuspected reason, and people will want to use that.

In such an event we can under the current spec either expect an
effective split of geminispace around which clients support what
encodings, or widespread client updates. This is not a very different
situation from a change to the fixed spec.

-- 
Philip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201228/fbca2a56/attachment.sig>