cross-posted from: https://feddit.org/post/24735701
See also:
https://en.wikipedia.org/wiki/Gemini_(protocol)
It is similar to the old gopher: text files, links, and images form a hypertext optimized for reading. Text is formatted like Markdown - but even simpler.
Clients display text, like an eBook, or images / media.
Servers can run on a PC or Raspberry Pi which needs half a Watt of power. No FAANG companies needed. No expert knowledge needed - not more difficult than running a file sharing client.
I think it is the right thing for defense of democracy and sharing your voice in the digital realm.


What’s wrong with http?
There’s varying takes on why folks prefer Gemini:
w3m,linksandlynxto view simplistic webpages, but anyone, who actually wants to use the web with these, will quickly run into webpages they cannot view.With Gemini, you can use tons of clients, some of them even written in Bash, because it’s so simple, and you will not run into pages you cannot view.
Well, and through survivorship bias, folks on Gemini tend to be nerds who care about permacomputing and the like, so that also helps with finding folks that have similar interests, even if you might end up reading their gardening blog, due to the aforementioned point.
I think the better comparison (whether that’s technically accurate or not) is to HTML + CSS + JS. Which is overly complicated for just small blogs and personal webpages etc. I think that’s the “issue” Gemini is trying to solve.
Still not an issue. Just throw out all modern web frameworks and stick to content-focused HTML. You can even do plaintext with unclickable links.
Have you ever seen HTML without CSS? It’s ugly as hell
Or if you like a more readable markup with a very thin markdown layer on either the client or server side.
I think TeX is the right way.