If you hear the word Gemini now, you probably think of Google’s AI product. That is understandable, but it is not what this post is about. This Gemini is an Internet protocol: a small, deliberately limited way to publish and read documents online.
It sits somewhere between Gopher and the web. That is not a perfect description, but it gets the basic idea across. Gopher was simple and menu-driven. The web became flexible enough to carry documents, applications, video, commerce, tracking, advertising, and half the software industry. Gemini tries to recover the part where a person publishes something and another person reads it, without bringing along the rest of that machinery.
A Gemini site is usually called a capsule. You do not visit it with a normal web browser. You use a Gemini client. The addresses begin with `gemini://` instead of `https://`. The pages are usually written in Gemtext, a plain markup format with headings, links, lists, block quotes, and preformatted text. It is intentionally sparse. There are no inline images, no client-side scripts, no cookies, no autoplaying video, no tracking pixels, and no layout system pretending every page needs to be a magazine spread. That is the reason some people use it.
Gemini is not trying to beat the web at being the web. It is not a replacement for online banking, maps, shopping, video calls, documentation portals, or web applications. It is bad at all sorts of things the web is good at. That is part of the point. Gemini draws a hard boundary around what it will do, and by doing that, it creates a quiet space for reading and publishing.
The modern web has a habit of turning every page into an application delivery system. Even a short essay may come with JavaScript frameworks, analytics, cookie notices, embedded media, social buttons, font downloads, newsletter popups, and requests to domains the reader has never heard of. Some of that is useful in the right context. A lot of it is just baggage.
Gemini takes the opposite approach. A Gemini document is mostly text and links. The client decides how to display it. The author does not get pixel-level control over the reader’s screen. That sounds like a limitation because it is one, but it is also what keeps the format honest. The writer supplies the words. The reader’s software handles presentation.
There is something familiar in that if you remember older parts of the Internet. Mailing lists, Usenet posts, Gopher menus, plain HTML pages, README files, and man pages all assumed that text was enough much of the time. Not always. Not for every job. But often enough that people built serious communities and useful archives with very little decoration.
Gemini also appeals to people who care about control. Running a Gemini capsule is not usually a large operation. You can host one on a small server. The files are simple. The protocol is understandable. There is no advertising network to satisfy and no dominant platform deciding how your page should behave. A reader can pick a client that suits them, just as older Internet protocols allowed different clients for the same underlying service.
That does not mean Gemini is free of problems. Discoverability is limited. Search is weaker than on the web. The audience is small. Normal people are not going to install a separate client just to read one post. Publishing in Gemini can feel like talking to a side room off the Internet, not to the main public square. Anyone pretending otherwise is selling romance.
There are also fair accessibility questions. A simple text protocol can be excellent for accessibility when clients are well made, but the smaller ecosystem means fewer assumptions should be made. Good plain text helps, but good software still matters. Simplicity is not a substitute for care.
The best case for Gemini is that the limits are useful. Gemini gives writers a place where the default unit is still a document, not a product surface. It gives readers a way to browse without being followed by half the advertising business. It gives technically curious people a protocol small enough to understand, run, and modify. It gives the independent web another reminder that publishing does not have to mean accepting every habit of the commercial web.
For most people, Gemini will remain a curiosity. That is fine. Not every useful technology needs mass adoption. Some tools matter because they preserve an idea. In Gemini’s case, the idea is that reading online can be quiet, portable, and low-demand. A page can be just a page. That is not enough for everything. It may be enough for more than we admit.