Re: [spec] Will Gemini ever become a standardized protocol?



On 3/25/2021 1:59 AM, Stephane Bortzmeyer wrote:
> On Thu, Mar 25, 2021 at 08:26:03AM +0100,
>  almaember <almaember@disroot.org> wrote 
>  a message of 34 lines which said:
> 
>> And Gemini might also get into projects like cURL.
> 
> Indeed, many projects may hesitate to include Gemini patches if the
> scheme is not a registered one.

I think that's pretty much a non-issue, already, TLS support for gopher
is included in curl, so the notion that Gemini needs some special hat
tip from a large body is a weak argument IMO:

https://github.com/curl/curl/commit/a1f06f32b8603427535fc21183a84ce92a9b96f7

These "projects", weigh the intrinsic value of a protocol being included
on meritious points, rather than being favored by a kingship. Does it
add value to Unices? Does it merit support on its own... etc. And, of
course, do you have any friends with commit privleges or influence? That
always helps lol.

Critical mass, which Gemini is closely approaching, is a much stronger
use case anyway.

Even the IRC RFC's are decrepit and outdated, and IRCv3 is a standards
body unto itself, with nothing having been suffered. Other popular
communications protocols aren't bothering with approvals from
snail-paced bureaucracies either, because it's a generally considered by
many of them as a hindrance to innovation, although at some point this
is definitely something we should have on the roadmap - just not
something to fret over now.

And I think we're getting a little ahead of ourselves by looking at a
draft RFC at this point too. When the Spec is finalized, then it will be
a good time to address those issues, having worked in that area in the
past at length.

I should have said something sooner on the gitlab issue tracker but got
sidetracked. I'll get around to it in a few days.

The matter of Tivoli was raised here a few weeks back. It's basically a
dead horse, and the domain itself for the registration now belongs to
CSC - I don't think that's actually part of IBM's properties ("yet", he
says sardonically). I could be mistaken there, of course. I haven't
checked that far.

We're certainly not dealing with, or looking at having to contend with
WIPO on the whole port registration issue.

So yes, it's certainly a roadmap item, but at this juncture it's more
like putting the cart before the horse. We're building great things
here, and there's an invigorated community focused on that, which is the
most pertinent measure of success by any means.


-- 
Bradley D. Thornton
Manager Network Services
http://NorthTech.US
TEL: +1.310.421.8268

---

Previous in thread (19 of 26): 🗣️ almaember (almaember (a) disroot.org)

Next in thread (21 of 26): 🗣️ Stephane Bortzmeyer (stephane (a) sources.org)

View entire thread.