💾 Archived View for rawtext.club › ~sloum › geminilist › 001188.gmi captured on 2020-09-24 at 02:03:40. Gemini links have been rewritten to link to archived content

View Raw

More Information

-=-=-=-=-=-=-

<-- back to the mailing list

More silly text/gemini spec proposals

Thomas Karpiniec tkarpiniec at icloud.com

Fri May 29 22:26:15 BST 2020

- - - - - - - - - - - - - - - - - - - 

On Fri, May 29, 2020 at 01:15:33PM +0000, solderpunk wrote:

Who thought it was a good idea to turn a harmless way to indicate
*where* some data can be found into a way to shoehorn in the data
itself? What are we supposed to use in a context where we don't
want that to be a possibility? Bah!

I think it is completely reasonable to specify a set of allowedschemes whose use aligns with gemini's goals. For the sake of aconcrete example, perhaps:

Every programmatic interface I've worked with for URLs will parse thescheme so you can easily inspect it, and a content container such awebview or an NSTextView will let you filter requests before passingthem through to the operating system for action.

Making such a rule in the specification is not going to limit anyone'sability to use regular libraries. It would probably only become anissue in the sort of client where the developer has decided to rendertext/gemini inside a webview, in which case sanitisation is a hugeproblem anyway.

Cheers,

Tom