Le lundi 7 d?cembre 2020, 10:29:34 CET bie a ?crit : > > I get that we need to encode spaces and other special delimiter characters, but other than that, what's the rationnal in limiting to ascii? > > MCMic > > There is one really good reason - it won't work well with existing > servers and clients. > > Most servers (and especially servers that follow the spec) currently > only accept requests that provide a valid URI - so a request that > contains something outside the set of valid 84 characters should not be > accepted. Asking for servers to start accepting IRIs is a big change, > and a breaking change in my opinion, one that adds a lot of complexity > for very little value added. I have to disagree that using my own language to name files and pages on my own server is of ?very little value?. Servers already have to output utf-8, why not accept utf-8 in the input? > Allowing such links in text/gemini, but asking clients to handle the > percent-encoding in the background has a similar problem - it goes > against what every single client is doing now. I am not asking clients to handle percent-encoding, I expect my server to receive the utf-8 I put in the link. I just tried, my server handles gemini://gemlog.lanterne.chilliet.eu/fran?ais-test.gmi with no problem. (I coded the server myself, but I did not put any effort into supporting this, I never tried it before). Most clients will percent encode the request, but with lagrange if I enter it like this in the adress bar my server does receive the request not percent encoded and reacts well. (It also reacts well if percent encoded of course since it decodes to the same name). > The best solution, in my opinion, is to stick to URIs. If someone really > wants to be able to type links like your example into their text/gemini > files, there's even a solution for that - create as server that processes > the .gmi files on the fly and sends punycode/percent-encoded links to > the client. Gemini has taken steps in the right direction by defaulting to uft-8 and specifying that there is no default value for lang. It would make a lot of sense to accept utf-8 in request as well and not arbitrarly limit to ascii, just because of web history. I understand that punycode will have to be used for the DNS lookup, but that?s on DNS specification, not Gemini?s reponsibility. But I fail to see why the Gemini request should be punycoded, or percent encoded except for special delimiter characters. MCMic
---
Previous in thread (17 of 68): 🗣️ bie (bie (a) 202x.moe)
Next in thread (19 of 68): 🗣️ Stephane Bortzmeyer (stephane (a) sources.org)