@alexandra I think everything from HTML 2.0 (IETF WG) on was a mistake. We had basic tag soup and IMG. That's all you need.
@firstname.lastname@example.org @email@example.com @firstname.lastname@example.org I'm very conflicted about Gemini because it feels like partially a step in the right direction, but at the same time it feels like it cuts out too much from the current Web. I think forms and metadata and so forth have a lot of value and not too much opportunity for insane things to happen.
There are decent arguments to be made in that direction, but this just cuts off the nose to spite the face. Forms and metadata are how people *interact* on the web. I don't throw open a raw socket and sling bytes to hopefully chat with my friend, much as I'm sure Gemini's authors lament.
Gemini isn't meant to replace the web. It's better to look at it as an improvement on gopher (especially the page markup language), and a small place where monetization is nigh impossible.
Everyone thinks that gemini is just perfect, except this one missing feature. But that one missing feature is never the same and including them all would just be an exercise in re-inventing the web.
Yeah, forms would be good. And inline links. And auto-loading images. And chunked, resumable transmissions. And cursive text. And e-tags or similar. And referer headers. And tables. And LaTeX mathematical notation. And stylesheets.
All of these are suggestions (sometimes worded as demands or with arguments like "gemini is useless without this!") that have showed up on the mailing list. Must-have features that gopher has done fine without for decades.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.