| > For example, I switched to Mastodon (...) and was able to see real forms of people I followed before, so I have updated my views on them. Isn't that strong evidence that it is possible to have a "human-scale" web built on HTTP, and consequently that there is not much benefit in restricting yourself to a protocol that is designed to be limited? > Personally, I see Gemini or other protocols as equals to HTTP/S Except they are not. Maybe it can do enough of the things that you care about, but Gemini is (by design!) meant to do less than HTTP. > publishing to Gemini is not different than having a RSS feed in my case. Again: if all you want is to be able to publish something in a simple format, then why should we care about the transport protocol? I get the whole "the medium is the message" idea, I really do. I get that people want a simpler web and I look forward to a time where we have applications developed at a more "human scale". But I really don't get why we would have to deliberately be stripping ourselves of so much power and potential. Talking about Gemini as the best solution to the problems of the modern web is like saying we should wear chastity belts to deal with teenage pregnancies. |
In that scenario W3C doesn't put any brakes, Mastodon puts brakes on development, organizational structure and scope, and Gemini puts brakes on the protocol. So, it's the most limited but hardest to abuse in a sense.
I probably worded my "I see them as equals" part of my comment wrong. I know Gemnini is a subset of HTTP, it's more Gopher than HTTP, and that's OK by me. Moreover, that leanness is something I prefer. See, the most used feature on my browser is Reader mode, and I amassed enormous amount of links in Pocket just because of the reading experience it offered.
> I really don't get why we would have to deliberately be stripping ourselves of so much power and potential.
Because power corrupts and gets abused. A friend of mine told me that they now use Kamal which makes deployment easy. How it's deployed? Build a container -> Push to registry -> pull the container on the remote system -> runs the container -> sets up and runs a proxy in front of that container to handle incoming connections.
That's for a simple web application...
I mean, I push files to a web server and restart its process. I'm not against power, I'm against corruption, and given human nature, restraint is something hard to practice, and that's if you want to learn and practice it.
> Talking about Gemini as the best solution to the problems of the modern web is like saying we should wear chastity belts to deal with teenage pregnancies.
I never said Gemini is the only and the best way forward. Again, for me It's another protocol, which offers a nice trade-off for some people sharing a particular set of values. It's like a parallel web like BBSes or public terminals (e.g.: SDF).
Being an absolutist benefits no one. We should learn, understand and improve. We can have multiple webs, and we shall be free to roam them in a way we like. I'd love to use my terminal to roam some text only web with my favorite monospace font and terminal theme, but I like to write comments here and think on the replies I get, too.
I find myself preferring a text-only, distraction-free web more and more, and naturally evolving my habits and personal infrastructure in that way, but I'm not carrying a flag, shouting about end-times and preaching stuff as savior. I'm not that person.