@cadence Gemini is a new collaboratively designed internet protocol that is like the web but serving up text/gemini as the native format instead of HTML, CSS, and JS. Imagine a www made of simple Markdown-like files connected by links. It's fully encrypted, private, fast, non-commercial, and fairly malware-proof. Go to https://gemini.circumlunar.space to learn more and download a client. #gemini
Well you kinda fucked yourself with a lack of extensibility there.
GET /some/shit GEMINI/1 is pretty straitforward and has a forward path to it (can read GEMINI/1.1 or such later.)
Request headers are much the same boat. They can be used to request specific languages, or cache control, or weird internal stuff the end user doesn’t see because its between the frontend and the app servers.
why not just use HTTP 1 with the weird chunking/multipart stuff removed?
@icedquinn @cadence @purple The best answer to your question is in the Gemini FAQ, which covers questions like this in detail. Gemini has many different goals than HTTP, including mandatory encryption and a focus on simplicity. Its spec is concise enough that anyone can write their own server or client in a few hundred lines of code. This gives control of the protocol to individuals rather than forcing us to use huge corporate built servers and browsers.
@icedquinn @purple You are entitled to your opinion, of course. I didn't create the protocol. I'm just a happy user of it. Based on the huge number of favorites and boosts that I received from my post explaining what Gemini was, it appears that there are a lot of people who are quite happy about it. Now I'm going to get back to something productive, like finishing my Gemini server and surfing Geminispace.