💾 Archived View for rawtext.club › ~sloum › geminilist › 001359.gmi captured on 2020-10-31 at 15:04:20. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
Sean Conner sean at conman.org
Thu Jun 4 23:19:14 BST 2020
- - - - - - - - - - - - - - - - - - -
It was thus said that the Great Alex Schroeder once stated:
Regarding wikis: yes! But I don’t want to know whether the first and the
second edit was made by the same person, and I don’t want to issue any
client certificates to users, so they seem to be the wrong tool for me.
I’m thinking auth. tokens, or passwords without usernames if you will. On
my wiki, that would be the security question I ask first time editors (and
often my questions are simply “please say hello”).
I was wondering if you might do this.
More info here:
https://alexschroeder.ch/wiki/2020-06-04_Gemini_Upload
=
gemini://alexschroeder.ch/2020-06-04_Gemini_Upload Gemini Upload
Thankfully, you used a new URL scheme for this, thus keeping this squarelyout of the Gemini protocol itself. And the proposal make sense to me. Asto the open questions you have, unless you think you would be using thequery portion of the URL for something else, why not indicate metainformation there?
gemini+write://alexschroeder.ch/Test?size=5612&mime=text/markdown&authtoken=foo
Or even better (as it too, is part of the spec)---use the ';' to desginatethe information on the last part of the path (the ';' is classified as asub-delimeter and in the earlier URL RFCs was specifically called out assuch for the path portion):
gemini+write://alexschroeder.ch/Test;size=5612;mime=text/markdown;authtoken=foo
That way, you still have the query portion for other uses.
-spc