[ryukafalz]

I don't often use Gemini, but here's the thing that I think this misses and that Gemini does well:

If I click a link in a Gemini browser, I know for sure that it will not start loading and running a ton of resource-intensive scripts. I know that it will not start autoplaying audio or video. I know that it will display fine in plain text, every single time - so it works in my terminal, in Emacs, on my phone, etc. And I know it will be fast.

Yes, I can use NoScript, uBlock Origin with comprehensive lists, etc. and start to approach that level of simplicity... but every other link I click will likely be broken in weird and wonderful ways. In Gemini, they all work (provided the page still exists, of course). I think there's some value in that.

[tlamponi]

> If I click a link in a Gemini browser, I know for sure that it will not start loading and running a ton of resource-intensive scripts. I know that it will not start autoplaying audio or video. I know that it will display fine in plain text, every single time - so it works in my terminal, in Emacs, on my phone, etc. And I know it will be fast.

With a `text/gemini` content type over HTTP/1.1 you could just use cURL, wget or fancier stuff like w3m/lynx and get the exact same benefits but would not need to install yet another internet facing tool that may even get things wrong security wise (even with simple stuff a possibility).

[lmm]

How would a text/gemini content type guarantee that links did not go to pages with those issues?

And given that HTTP has content negotiation, how could you ever be assured that a given link goes to a text/gemini page?

[boring_twenties]

Tag the link with a flag, then have the user agent refuse to load the links if it comes back with any other content type.