Hacker News new | ask | show | jobs
by Apreche 1119 days ago
I agree. I think a lot of the problem can be solved with discipline rather than a new spec entirely. If HTTP offers features that are offensive or unwanted, simply don't use those features. Make an HTTP server and client that only implement a subset of HTTP. Then use a subset of HTML, or another content type entirely.

This means anyone still using a popular browser like Chrome can visit your sites, but people using a more limited client can as well. It also means you still get to lean on the 30 years of technical refinement rather than reinventing many wheels.

4 comments

Some people hate what has become of the current thing so much that they want to throw all of it away. This is that.

The goal would be entirely achievable using your suggestion, but then you can't make something "simple" and "elegant".

Of course don't take my cynicism to mean that people shouldn't invent new things - they totally should, that's how we move forward. Mess around all you like. I just don't see it catching on. But I think that's not really the goal anyway.

Gemini makes sense when you realize it's the protocol equivalent of running off to join an anarcho-primitivist commune or ascetic monastery, a technical solution to an emotional problem (disgust with the web and modern capitalist society.)

It being too basic and rigid to the point of hostility towards anything but pure text is the entire point.

> anarcho-primitivist commune or ascetic monastery

Even monks liked some illustrations (illumination) in their manuscripts. Gemini is closer to babylonian clay tablets delivered over TCP.

> This means anyone still using a popular browser like Chrome can visit your sites

I think this would be seen as more of a drawback than a feature. If you're trying to build a tight-knit little hobbyist community, random people popping in and complaining that "these pages are boring, where are all the images?!" isn't helpful.

Gemini doesn't support POST so no one can possibly pop in to say anything.
Given that there are microblogging (gemini://station.martinrue.com/), reddit with optional git connection to allow for issue tracking (gemini://geminispace.org/), it seems you're wrong.
Well...exactly. Working as designed.
> If HTTP offers features that are offensive or unwanted, simply don't use those features. Make an HTTP server and client that only implement a subset of HTTP.

Just make sure it never ends up in a security critical context. Various larger companies already got screwed over when their front end code did not detect the size of a http message the exact same way their backed code did.

>Make an HTTP server and client that only implement a subset of HTTP. Then use a subset of HTML

which subset?

the older html/http versions are older versions, not a subset of the modern html/http. afaik modern html/http doesn't have subsets.

>using a popular browser like Chrome

Gemini is created so that anyone would be able to write a Gemini browser in a couple of days. Or server.

I don't want "popular HTML browser" because I won't be able to write something like it in whole life.