I very briefly fell in love with the idea of a Gemini interface for our instance, but unfortunately it’d be read-only:

you can’t use Gemini itself to put content into Geminispace. You need to use something else, such as (S)FTP, SSH, rsync, git, a web interface, an email interface, etc.

(from geminiprotocol.net)

I’m actually kind of pissed off that that’s where the line is. sessions aren’t what enshittified the web; cookies as an enabling technology for sessions are ridiculously awful and prone to abuse, but they aren’t required for sessions. there’s absolutely a way to do modernized sessions and forms in a privacy-preserving way that’s still incredibly simple. like fuck, the features I’m hoping for are BBS staples that predate the web. why are we fetishizing the brief period before the web was useful?

e:

This freedom from the threat of tracking comes with downsides: Gemini has no support for caching, compression, or resumption of interrupted downloads, and as such it’s not very well suited to distributing large files, for values of “large” which depend upon the speed and reliability of your network connection.

imagine being so allergic to success that you decide your special protocol shouldn’t even be good for piracy due to the fantastic tracking risk of supporting gzip or a seek header