Gemini Digest, Vol 23, Issue 40

[Jonathan McHugh]

Hi Omar,

Yes, I agree with what you are saying.

Of course, in addition to an (appropriately named) header location, having a
special /gemini.html page. This could give an individual/collective
justification and more visible signposting to the uninitiated/distracted (to provide
some escape velocity).


JM 

> Jonathan McHugh <indieterminacy@libre.brussels> writes:
>
>> Is there a (dictionary) repo covering sites which operate for both Gemini
>> and HTML?
>

Omar Polo <op@omarpolo.com> writes:

> I don't think it's worth the effort to keep a directory of sites that
> are available on both Gemini and the Web.  It's hard to keep it
> up-to-date, to inform geminauts about it and more importantly it's not
> like a Gemini capsule and a website on the same will have the same
> content.  Furthermore, there are people (like me) that have the web site
> and the gemini capsule on different subdomains (www and gemini
> respectively).
>
> (it hurts to speak about HTTP on a gemini mailing list)
>
> 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
>
>> If so, it would be great for browsers to then be whipped into visiting/providing
>> the Gemini one each time a URI is considered.