<-- back to the mailing list

Should Gemini clients alert users upon redirect?

Stephane Bortzmeyer stephane at sources.org

Wed Feb 17 12:17:09 GMT 2021

On Wed, Feb 17, 2021 at 11:37:52AM +0000, Luke Emmet <luke at marmaladefoo.com> wrote a message of 40 lines which said:

A lot of URLs expose the innards of the site (cgi-bin, *.php)
implementation

This is widely recognized as a very bad practice since, should youchange implementation (moving from PHP to Node…), the URL wouldchange, which is bad <https://www.w3.org/Provider/Style/URI>

Having a link end *.pdf gives readers a very good hint as to the
content at the end of the URL and it helps me make a choice

Sure, but this is a very different case. The extension is about thecontent, not about how it was generated/served.

As a visitor, we cannot expect URLs to implement any sort of tree
structure, but in practice they usually do and we can traverse up
and down the URL architecture as well as by following the authored
links. For me this is the pragmatics of URLs.

I agree that, for the visitor, it is better. I certainly prefer siteswhere you visit <gemini://guide.example/france/paris> and can edit theURL in the address bar to go to <gemini://guide.example/france/>,expecting something more general about France.

As you know (but it may be worth repeating), RFC 3986 does not mandatethat this works. Paths are mostly opaque. You cannot rely on it, but Ifind it cool, and a Good Practice.

Proxied content from gemini://rawtext.club/~sloum/geminilist/005318.gmi (external content)

Gemini request details:

Original URL
gemini://rawtext.club/~sloum/geminilist/005318.gmi
Status code
Success
Meta
text/gemini
Proxied by
kineto

Be advised that no attempt was made to verify the remote SSL certificate.