Comment by CupCakeArmy on 05/07/2020 at 09:37 UTC

2 upvotes, 2 direct replies (showing 2)

View submission: A look at the Gemini protocol: a brutally simple alternative to the web

How is this solving stuff? The reason why websites are huge these days is a choice made by developers, not http.

Gemini actively does not recover from network instability??? Ever heard of smartphones? Those things that make you the majority of web traffic.

Also.. only plain text files. Cool, love that Wikipedia diagram that explains it better to me. O wait.. now it's a ASCII picture. Yeah fuck this.

It's a cool thought experiment, but it's so naive to think this would solve the problem or even be a suitable protocol.

Replies

Comment by Shaper_pmp at 05/07/2020 at 10:24 UTC*

2 upvotes, 1 direct replies

My current theory is that this is a complicated parody.

It adds literally nothing that you can't already do with HTML/HTTP, only nobody's doing it because *nobody wants it*.

Seriously - everyone hates CSS popups, but are they prepared to trade them for no inline images? Fuck no.

Everyone hates ad-scripts, but is anyone prepared to trade them for *no client-side JS at all*? Fuck no.

Targeting a protocol "inbetween gopher and the web" seems a lot like "explor[ing] the space inbetween" napped flint shards and modern scalpels. It's fundamentally pointless because now we have surgical steel scalpels *nobody wants* to do surgery with bits of broken flint any more.

Comment by RedditAlready19 at 20/12/2021 at 09:56 UTC

1 upvotes, 0 direct replies

Here is the thing - images are a thing on Gemini, but they are often pointed to as links. Fortunately, some clients do render images inside the page. Also, the text isn't plain text (that's gopher). Its a markdown like format called Gemtext.