Not sure I'm a fan of mandatory TLS in gemini, what about mercury? gemini://

looks like a lot of replies to this post on the geminiverse were against this proposal. I guess I'll be sticking with gopher for now.

Show thread

gemini wastes time by adding a non-trivial amount of TLS latency to each request, most of the time this is completely unnecessary.

Show thread

Not to mention that the noise-protocol would be a strictly better choice here (less roundtrips), but unfortunately TLS is baked into the core protocol so you're stuck with it. I doubt Mercury will catch on but it would be my ideal "markdown gopher" protocol.

Show thread

@jb55 there's been discussion of signal and other protocols for Gemini on the mailing list

@tomasino astrobiology, client certs, various encryption protocols, identity, etc are neat but I fear that it's super overkill to force encryption latency/complexity on the entire geminiverse of mostly static markdown-like files. I guess gopher is just more my jam, maybe I'll just write a client that renders markdown when it detects it 😅

@tomasino I definitely like the idea of choice of protocol depending on complexity levels of taste, although it's a shame that content gets fragmented.

@tomasino probably not a big deal though since there will be clients that handle both at the same time...

Sign in to participate in the conversation
Bitcoin Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!