Some reading on IRIs and IDNs

[Stephane Bortzmeyer]

On Thu, Dec 10, 2020 at 04:54:52PM +0100,
 cage <cage-dev at twistfold.it> wrote 
 a message of 44 lines which said:

> Adding more complexity and more responsibility to software authors
> will shrink diversity in the gemini software landscape.

The idea is that it will not be done by the programmer (Unicode is
complicated) of the Gemini client but mostly by the libraries she or
he uses. It is the same with TLS: TLS is very complicated but most
people do not program it by themselves (and rightly so).

> Internationalized  hostname  has  advantages  but  how  this  adding
> complexity impact software author? Is this complexity needed?

Since I write Gemini clients, I have sympathy for this point of
view. However, let me quote RFC 8890

=> gemini://gemini.bortzmeyer.org/rfc-mirror/rfc8890.txt

4.5.  Deprioritizing Internal Needs

   There are several needs that are very visible to us as specification
   authors but should explicitly not be prioritized over the needs of
   end users.

   These include convenience for document editors, IETF process matters,
   and "architectural purity" for its own sake.


=> https://www.w3.org/TR/html-design-principles/#priority-of-constituencies See aso this statement by W3C