Some reading on IRIs and IDNs

[Sean Conner]

It was thus said that the Great colecmac at protonmail.com once stated:
> > > It's unfortunate they don't
> > > have an implementation, but as it stands right now, most Gemini clients
> > > will not handle Unicode domain names at all.
> >
> > And I'm not seeing anyone else trying to update clients to do this, even
> > if in an exploratory nature. What? Are they just waiting for a decree?
> >
> > [snip]
> >
> > So when are you going to update gemget and Amfora to support punycode?
> > I've heard it's easy to do. Or are you waiting for a spec change first?
> >
> > -spc (Seriously, I feel like I'm the only one doing anything here)
> 
> Yes, I am waiting for Solderpunk. On the subject of IDNs, it seems obvious
> to me that punycode will accepted as the thing to do for DNS,

  And why would Solderpunk choose this if no one has bothered to even look
into the possible issues wit respect to coding?  

> and that
> Unicode should be sent to the server, 

and that would be a breaking change on the protocol.  Just having the client
accept IRIs and send URIs wouldn't change the protocol.  But aside for me,
NO ONE bothered to even test this out!

> but some questions around certs
> and normalization still remain. I've outlined them here[1].
> 
> I suppose you're correct about being the only one doing anything, but I
> don't feel like it makes sense to do anything yet. The solution is simple
> code-wise (for IDNs), and so I don't feel the need to experiment, 

  And if it's so simple, why not do it? But I get it, you'd rather wait
until a yeah/nay decision is made.  I mean, who wouldn't like

	single digit resonse codes
	no client certificates
	a link line of [text|url]
	no virtual hosting
	a request format ala gopher (including TABs!)
	no rediection
	no indication of pages are actually gone vs not found
	no MIME parameters

  That's pretty much what the Gemini spec *would have been* had some people
*cough cough* not bothered with doing any implementations.  But i get it. 
Bikeshedding with talk is easy, bikeshedding with an implementation is
tedious.

  -spc