💾 Archived View for rawtext.club › ~sloum › geminilist › 006112.gmi captured on 2021-12-03 at 14:04:38. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Mansfield mansfield at ondollo.com
Mon Mar 15 03:55:00 GMT 2021
- - - - - - - - - - - - - - - - - - -
On Sun, Mar 14, 2021 at 8:10 PM Sean Conner <sean at conman.org> wrote:
It was thus said that the Great Mansfield once stated:
I *think* I implemented/tested/tried the IRI thing and I'm thinking that
I'm not in the group-size-two that you referred to.
First off, I want to thank you if you have implemented IDNs (no matter
how
good or bad---just the fact that you did is wonderful). Second, you are
right, you are the third (if I recall correctly, not many people mentioned
it) to do so.
You're welcome!
I kinda wish we or I could be more organized around what experimentseveryone is running so that we could swarm several implementations on anythat others liked or disliked. IMO that could be an advantage of somethinglike gitlab - label issues as 'experiments' and look forimplementations/tests/urls/etc on the issues. Maybe I'll throw up some ofmy experiments as issues in gitlab...
FWIW - I *really* like the "implement your idea in code and then let'stalk" approach, since Gemini is soo stinking simple to get a foot in thedoor on.
The sentence I just wrote is *not* my point - I'm totally cool with the
above (what I and you and others wrote/expressed) - my point is... I was
thinking...
If I *thought* I tried out the IRI thing, but wanted to check, where
would
I go? What would I test? How would I 'certify'?
If I wanted to be a part of the discussion in a
trying-to-implement-this-new-experiment way, what should I do?
A great question, and fortunately, there is an answer, at least for
clients: try fetching the following IRI:
gemini://café.mozz.us/files/ <http://xn--caf-dma.mozz.us/files/>
𝒻𝒶𝓃𝒸𝓎.txt
Seemed to work fine. I ran my client from the CLI with that host/path asthe destination and it seemed to work. Then I used the in-client method ofediting/setting the destination and pasted that host/path and it returnedthe same result - not that *going* there would have been any different, butthat I wanted to make sure that editing the location in the clientsupported what the CLI had supported.
Thanks to mozz.us for providing that - it felt good to run a test thatwasn't something I had contrived!
Not my site, but the size of the other person who bothered to experiment
with this stuff. And as for details, it would be nice to know:
operating system
implementation language
possible libraries in use
and if it works, what you had to do in order to get it to work.
Again, there could be more in the code that I'm not pulling out in thequick glance back over what I wrote a while ago.
... you know... I'm starting to remember that there was some reallyannoying corner in the implementation... but my fuzzy memory says that itwas with how I had organized my code - not with the key implementationdetails.
I'm guessing that maybe an email to the list or a comment on a gitlab
issue
to the effect of: "I think this is what it means to test out the IRI
thing.
I think I did it, you can try out my implementation like this..."
That feels... good to me...
There is an issue with how I think it should work:
https://gitlab.com/gemini-specification/protocol/-/issues/1
Ahh... cool. The URL from above is in that ticket.
Humm... so I'm not sure I'm following the discussion. Maybe some of itreferences the fact that I used the idna lib on the hostname instead ofsomething in the golang std lib?
Interesting points about the certs. I'll have to go check what happened inmy server cert setup with the emoji subdomain I used in some testing...
Also - for the list of should's and should not's that that issueprovides... now I'm curious to find out if I'm fully compliant. I'mthinking that my server and client *are*, but... maybe there's some sharpcorner I'm not great with. My thoughts are drawn back to wondering whattest methods could be used to 'certify compliance' with the spec. Seemslike that URL is a great start... maybe the only other test is "that aserver correctly respond when the domain and some part of the path containsunicode"... is that really all this boils down to?? I feel like I'm missingsomething. Maybe I'll add some specific questions in that gitlab issue sothat I can make sure I'm on the right page.
but I've been told that no, what I wrote is *wrong*, but as of yet, no one
has given a concrete approach for clients to follow to get this to work.
That's what pisses me off about this---I wrote what worked for me, but it's
wrong [1], but no one has told me how to go about doing it right, and I'm
very close to closing the ticket with prejudice [2], with the only way to
get IRIs back on the table is to convince Solderpunk, the BDFL (I'm only
the
BDFLA, the Benevolent Dictator For Life's Assistant). So the more concrete
information I get for OR against it, the better.
-spc
[1] Mostly about resolving IDNs.
Well... specifically for resolving IDNs... my memory (again, fuzzy as itis) is that I wasn't able to Dial a tcp conn without punycoding thehostname. Again, the implementation detail for that is that it's a singlecall to a library in golang. (Now, some might want to point out that the'x' in the above URL for the idna library means 'experimental'... but..that moniker, IMO, doesn't hold across all the golang libs in 'x'... andthe code is there to look at if any feel it's lacking.)
As for setting up DNS using the emoji subdomain in my testing... myregistrar converted it to punycode without consulting me ;-) ... and I tookthat to mean that that was the way it had to be done.
[2] An American legal term meaning---when a legal case is dismissed with
prejudice, the case is closed, and there is NO means of appeal.
It's not used often, and when it does happen, it means the judge
was
royally pissed off.-------------- next part --------------An HTML attachment was scrubbed...URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20210314/83aae93f/attachment-0001.htm>