💾 Archived View for rawtext.club › ~sloum › geminilist › 002797.gmi captured on 2020-11-07 at 03:09:09. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-10-31)
-=-=-=-=-=-=-
Sandra Snan sandra.snan at idiomdrottning.org
Mon Sep 28 09:45:29 BST 2020
- - - - - - - - - - - - - - - - - - -
In which case please reapply my rant to _that_ Rubicon
Sean Conner <sean at conman.org> writes:
It was thus said that the Great Sandra Snan once stated:
We'll look back years from now when gemspace collective standards have a
complexity that overshadows that of the W3C specifications, and maybe
we'll recognize that this moment, this post was the Rubicon. Maybe we'll
think that the Pandora lid was already peeked through to the point of no
salvation, since an arbitrary sequence of GET requests could become a
protocol.
Nope. The Rubicon was passed earlier this year with talk of the titan:
protocol which allowed people to upload content to a Gemini server and has
already been implemented by at least one Gemini server. Just go to this
link:
https://lists.orbitalfox.eu/archives/gemini/2020/thread.html
and search for "titan". You'll find the threads. Also search for the
thread "Uploading Gemini Content". Again, you'll find the threads.
What I find sad is that this appears to be separate approach from the
titan: proposal, which either means the designers of this were not aware of
of the previous work, or have rejected the previous work for some unstated
reason---I'm hoping it's the former.
The question raised by this isn't just "why Dioscuri?" It's "why should
we not use sftp, https, JSON, XML, sexp, IRC, SMTP, foo bar baz frotz
for this problem?" That isn't rhetorical. There could be good answers. I
just can't think of them.
Again, check the history of this list. It has been discussed before.
-spc (Who fears that no one realizes that links to the mailing list
archives are sent in the headers to every message ... )