Gemini is an application-layer internet communication protocol for accessing remote documents, similarly to the Hypertext Transfer Protocol (HTTP) and Gopher. It is intended as a third alternative to those protocols. It comes with a special document format, commonly called “gemtext”, that allows linking to other documents. Started by a pseudonymous person known as Solderpunk, the protocol is now[when?] being finalized collaboratively and has currently[when?] not been submitted to the IETF organization for standardization.
What does the Gemini Protocol?
Gemini is designed within the framework of the Internet protocol suite. Like HTTP(S), Gemini functions as a request–response protocol in the client–server computing model. A Gemini browser (analogous to a web browser), for example, may be the client and an application running on a computer hosting a Gemini site may be the server. The client sends a Gemini request message to the server, and the server sends back a response message. Gemini uses a separate connection to the same server for every resource request.
Gemini mandates the use of TLS with privacy-related features and trust on first use (TOFU) verification being strongly suggested.
Gemini resources are identified and located on the network by Uniform Resource Locators (URLs), using the URI scheme gemini://. A Gemini request consists only of such a URL, terminated by
CRLF; the header of a Gemini response consists of a two-digit status code, a space, and a “meta” field, also terminated by
CRLF. If the server is successful in finding the requested file, the “meta” field is the MIME type of the returned file and after the header follows the file data.
20 text/gemini # Example Title Welcome to my Gemini capsule. * Example list item => gemini://link.to/another/resource Link text
There are no reviews yet.