The author very much did allow others to give input. The original protocol had single digit status codes, I was arguing for three digit codes, he compromised with two digit codes. It was my idea to include the full URL for requests, and for redirections. It's just that it wasn't easy, but he could be reasoned with. The only two hard lines Solderpunk had for the protocol was TLS, and single level lists (why, I don't know).
Gopher user there from texto-plano (and seldomly, SDF).
Gopher often sucks for 40x25 devices or mobile ones.
Yes, word wrapping, but everyone uses the 72 char limit
or even doesn't give a heck and I have to set
my own $PAGER calling fmt, fold or par before less.
On TLS, you are right. But I've got to build BearSSL and some
libreSSL for for Damn Small Linux. The 2.4 kernel one,
were ALSA was a novely and DMIX was hard to set,
the one you got with Debian Woody... with the bf24 at
the LILO prompt.
So, if DSL can run some BearSSL based OpenSSL-lite
client, a gemini client for it should be totally doable.
That's not narcissism - it's just someone building something they enjoy and sharing it with the world. Do you have the same objections to fiction writers or songwriters?
It's totally fine to prefer gopher for its maturity (I'd vehemently disagree, but that's for another day) or compatibility with retro machines, but framing someone else's creative project as a character flaw is just rude.