A look at the Gemini protocol: a brutally simple alternative to the web
It feels like the main feature of this project is incompatibility with HTTP.  The protocol is new and primitive, it's easy to write tools around it, write texts about it, etc.  A small community forms, and you're part of it.  You can advertise it to others, or rant against the mainstream, or whatever.  But now what?  You lose interest and abandon it, and eventually it dies.<p>We already have a transport protocol that "everybody" agrees on: HTTP.  We can define a specification for a subset of it, and a subset of HTML/browser features we want, create tools around them, and form a small community.<p>The advantage here is that the community is not an island.  Users of Big Browser can still read your latest rants.  They can even learn about this project and, while perhaps not using Mom-and-Pop browser, may support it in their sites, since it wouldn't require another server; mostly just having their site work without JavaScript would be a huge step forward.  Right, you don't have Google filtering based on Accessibility.  The community can create a search engine that does.  Now what? You just get on with your life, producing and consuming AccessibleWeb content without the gratuitous incompatibility.