Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> 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).



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?


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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: