Gemini is dead in the water due to a double failure: being essentially Gopher in the form of a brutalist buttplug and being intrinsicably unimprovable. Gemini is less capable than CSS 0.1 for content presentation. It's like trying to publish your blog on EDIT.COM.
What we need is re-HTML+CSS 1.0. Yes: without Javascript.
Hurd. There is nothing in the protocol that can or will prevent somebody from coming along and serving ads. It's like saying this river cannot be used to transport this cargo of the same shape and size. Somebody will make a port that will accept it.
To add to that, Gemini doesn't solve any technical problems that HTTP hasn't. It is of no benefit. Unless of course you want a small spec, but HTTP 1.1 is small too. I wrote a HTTP server in uni for fun to practice implementing an application layer protocol.
Question: does the basic http spec already predict/expect/explain cookies? Or is that only in later versions?
You can add any header to http that you like. Cookies are an RFC and not part of the http spec.