💾 Archived View for rawtext.club › ~sloum › geminilist › 006792.gmi captured on 2023-11-14 at 09:05:46. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2021-11-30)

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

<-- back to the mailing list

Gemini Digest, Vol 23, Issue 40

Rohan Kumar seirdy at seirdy.one

Thu Jun 24 17:27:46 BST 2021

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

On Thu, Jun 24, 2021 at 12:02:32PM +0200, Omar Polo wrote:

What could be done is use a HTTP header to inform the web browser that
that site is available also over Gemini. This way, the effort wouldn't
be on a bunch of people running a directory, but rather on the server
administrator. Something like a `Gemini-location: <url>'. From my
understanding it's something that the tor project is doing:
% curl --head https://www.torproject.org | grep -i location
Onion-Location: http://2gzyxa5ihm7nsggfxnu52rck2vv4rvmdlkiu3zzui5du4xyclen53wid.onion/index.html

Something that could work is an Alt-Svc header:

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Alt-Svc

These were sometimes used to advertise Onion sites before the Onion-Location header spec was released and supported by the Tor Browser.

This is unlikely to give any major benefit for Gemini though, esp. if gemini:// isn't IANA-registered; browsers don't know what Gemini is and will ignore it. Perhaps a browser addon could sniff out an Alt-Svc header advertising a Gemini capsule?

I'm generally against adding HTTP headers if they don't make a significant difference, especially if they're ignored by all the existing user agents. If information needs to reach a user and is ignored by the user agent, it should be included in the response body rather than the header.

-- /Seirdy (seirdy.one)-------------- next part --------------A non-text attachment was scrubbed...Name: signature.ascType: application/pgp-signatureSize: 898 bytesDesc: not availableURL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20210624/f2153395/attachment.sig>