-- Leo's gemini proxy

-- Connecting to gemini.bunburya.eu:1965...

-- Connected

-- Sending request

-- Meta line: 20 text/gemini

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

2 upvotes, 1 direct replies (showing 1)

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

View parent comment


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.



Replies


Comment by GavinMcG at 03/01/2022 at 04:11 UTC

2 upvotes, 0 direct replies


The point isn't the *serving* of the format, it's the *consumption*. Obviously you can do whatever gopher and Gemini do but with HTML. The point is that when you *the consumer* navigate to a Gemini resource you know you're getting only what the Gemini protocol offers, and you won't be subjected to the rest of the junk that can come along on an HTML request.


-- Response ended

-- Page fetched on Fri May 17 01:42:18 2024