> If they are not flexible and open to change where it is legitimate and makes a positive impact, but instead act as some sort of holier-than-thou cabal where o

> If they are not flexible and open to change where it is legitimate and makes a positive impact, but instead act as some sort of holier-than-thou cabal where outsiders are shunned as they "don't get" Gemini One of the main goals of Gemini is to have an immutable spec. The goal is to never add features. So yeah, the Gemini community is a little tired of people proposing changes and features to add to the spec. And I think it’s fair to say at some point that you “don’t get Gemini” if your first message to the mailing list is a request to add features. To address the favicon point—the spec explicitly disallows making more than one request to open a page. Favicons require a second request, and therefore are not compatible with Gemini. The Gemini community has had the conversation about favicons and decided they didn’t want them. AFAIK no browser supports them by default. Now what? To the TLS point, someone in Geminispace very recently proposed removing TLS citing the same arguments you did. There were dozens of Gemini posts made going back and forth, but on the whole the demand wasn’t there and we’re going to continue to use TLS. Gemini’s simplicity makes it super easy to criticize aspects of the design or suggest new features. So it gets boring. I could go find thousands of words on why Gemini doesn’t have TLS. But it wouldn’t be a better explanation that the one on the Gemini home page, which I assume that you’ve read and are unhappy with.