There's things that I like about #gemini (simple, text based, retro feel) but I'm not completely sold on it and haven't published anything on a gemini server yet.
This post ( https://マリウス.com/gemini-is-solutionism-at-its-worst/ ) was thought provoking, especially the quote below:
> The question here shouldn’t be why not to use a subset of HTTP and HTML, but rather, why not build on top of HTTP with a different markup layer other than HTML. We have APIs using HTTP with JSON instead of HTML, for example.
@retroedgetech
"why not use HTTP with another media-type"
1. One of Gemini's primary points is that user privacy is extremely important. Simply just adding gemini support to browsers gets us nowhere. Even recently, some people have tried to add favicon support to gemini browsers, which has been shut down, because we take privacy that seriously.
2. Gemini is supposed to be minimalist in nature, in all aspects. Gemini comes from permacomouting culture. While it's easy for people in wealthy countries to enjoy the latest tech and high speed Internet, others have to struggle to keep up. Running a high RAM/CPU browser is a luxury.
3. Gemini comes from the free culture community. We have high regards for our software. A new modern fully compliant Web browser would take hundreds of hours and people to make. A gemini browser can be made in one afternoon. That simplicity matters, and is why we have dozens of available gemini browsers, and only ~3 usable Web browsers which aren't reskins.
@torresjrjr I think that I strongly agree with your points and am very interested in #permacomputing.
Still not totally convinced that #gemini is the best solution... but I am open to it being something that I use and publish with.