💾 Archived View for station.martinrue.com › breakfast_champion › ef2c9cedf47a4de9b3b0ccd162b1f36f captured on 2024-05-26 at 16:04:22. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-05-12)
-=-=-=-=-=-=-
In your experience what differentiates Gemini most from Gopher? And what protocol features led to this difference?
1. Gemtext vs Plaintext * wrappable lines -> mobile users * unified document format -> weblike experience, rather than a link map + linkless text experience * inexpensive visual appeal vs expensive ASCII formatting 2. TOFU encryption vs nothing -> inband ID -> services like Station and BBS
I'm not very well versed in Gopher, only reading a few glogs from time to time, so I'd apprecate the input of experienced users.
Has there ever been anything as interesting as Station on it? If so, were the signups in-band?
2 weeks ago · 👍 jsreed5, jo
Gophermaps. They're just needlessly complex. Why do I need to have a file in that odd format when I can just have another regular gemtext file, or even just another regular plaintext file like Nex? · 1 week ago
Proper mediatype support · 2 weeks ago
Unicode support is a big one. · 2 weeks ago
pretty good summary. tls user certs were the draw for me. one reason I don't really use Spartan... · 2 weeks ago
I came to Gemini from Gopher, though my time on Gopher was admittedly short-lived. In my view, the biggest difference between the two--and what drew me to the protocol--was user authentication. Gemini in fact provides the bare minimum of tools I'd like to have when hosting a public service of my own. · 2 weeks ago