|
|
|
|
|
by DarylZero
1607 days ago
|
|
That's a massively more complex implementation for no benefit. Also it's definitely not enough to set a HTTP header. Need to use a different schema so that the restraints on content can be expressed in the URL of a link. A key feature of Gemini browsers is to visually distinguish between links to Gemini:// URLs and links to HTTP:// URLs. |
|
It’s barely complex. It’s a standard dispatch on the accept header, all major web servers handle this out of the box. Also it has the significant benefit of working with existing browsers. On what basis were you making that statement?
> Also it's definitely not enough to set a HTTP header. Need to use a different schema so that the restraints on content can be expressed in the URL of a link.
You can accomplish the same URL transparency by using a file extension convention. E.g. “https://foo.com/my log.gemini”