More silly text/gemini spec proposals

[Thomas Karpiniec]

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 allowed
schemes whose use aligns with gemini's goals. For the sake of a
concrete example, perhaps:

* gemini
* http
* https
* gopher
* gophers
* mailto
* tel

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

Making such a rule in the specification is not going to limit anyone's
ability to use regular libraries. It would probably only become an
issue in the sort of client where the developer has decided to render
text/gemini inside a webview, in which case sanitisation is a huge
problem anyway.

Cheers,

Tom