Any of you have thoughts on the gemini protocol (no not the google AI) #asknostr
A bit long and rambly, but had a section on and old blog post on the topic:
Gemini is often pushed as a good alternative to your standard web server in the indyweb/smolweb community, however, I’m actually going to trash on it a bit. Now, if it works for you that’s great, and I started this post off with an iambic-pantameter-meme-word-filled sonnet, so don’t take this post as anything more than me having fun rambling about things I like.
Anyway, Gemini’s claim to fame is that it’s intentionally bare bones; lacking javascript and modern web APIs. I get it, we’re all annoyed by javascript powered pop-ups, tracking, and ads; the goal of Gemini being to avoid all of that by hamstringing what a Gemini pod can be. However, I see it as the Luddite approach to things, thinking the problems of the present can be fixed by going from Web 2 back to Web 1. The problem with going backwards is you create a whole host of problems, problems that were solved by Web 2, and at the same time you can serve a Gemini pod style site over HTTP as well.
Some drawbacks in itself aren’t a deal breaker, but again, it doesn’t bring anything new to the table whatsoever. Of the above protocols, most have the capability of doing some or all of the following: using non-centralized identifiers, hosting content without a static IP or open port, and providing built in redundancy. But want a JavaScript free website? Serve it over Tor/I2P/IPFS/nsite and just don’t put JavaScript in it - or serve it over something like Nostr NIP-23 (markdown only) or AcitivityPub/AT-Proto (generally plain text).
I guess my philosophy here is that, if you’re looking to use something that differs from what the web is now, ideally look for the options that solve problems in novel ways, rather than just removing old solutions to already solved problems.
Gemini is often pushed as a good alternative to your standard web server in the indyweb/smolweb community, however, I’m actually going to trash on it a bit. Now, if it works for you that’s great, and I started this post off with an iambic-pantameter-meme-word-filled sonnet, so don’t take this post as anything more than me having fun rambling about things I like.
Anyway, Gemini’s claim to fame is that it’s intentionally bare bones; lacking javascript and modern web APIs. I get it, we’re all annoyed by javascript powered pop-ups, tracking, and ads; the goal of Gemini being to avoid all of that by hamstringing what a Gemini pod can be. However, I see it as the Luddite approach to things, thinking the problems of the present can be fixed by going from Web 2 back to Web 1. The problem with going backwards is you create a whole host of problems, problems that were solved by Web 2, and at the same time you can serve a Gemini pod style site over HTTP as well.
Some drawbacks in itself aren’t a deal breaker, but again, it doesn’t bring anything new to the table whatsoever. Of the above protocols, most have the capability of doing some or all of the following: using non-centralized identifiers, hosting content without a static IP or open port, and providing built in redundancy. But want a JavaScript free website? Serve it over Tor/I2P/IPFS/nsite and just don’t put JavaScript in it - or serve it over something like Nostr NIP-23 (markdown only) or AcitivityPub/AT-Proto (generally plain text).
I guess my philosophy here is that, if you’re looking to use something that differs from what the web is now, ideally look for the options that solve problems in novel ways, rather than just removing old solutions to already solved problems.
1💜1
