This probably sounds ridiculous, but I gotta say it out loud anyway because it’s been driving me bananas for the past few days. I want to create an information resource specifically for Star Trek meme creators. I haven’t been able to get it out of my head, so I think I gotta just build it already.
What would this site even have on it, you ask? Off the top of my head, I’m thinking the contents would consist of: the list of official Trek fonts for all shows (already in progress), links to screencap sites, links to the few Trek meme generators that are out there, software recommendations by platform, maybe a few guides here and there. Basically, all the stuff that would make it possible or easier to make your own Trek memes. Most of us here already have our own workflow set up just the way we want it, but not everybody does, and I’m also thinking a resource like this could help lower the barrier to entry a little.
I write code and documentation for a living, so it’s kinda in my wheelhouse. It would be a fun thing to do on the side, and I’d be lying if I said I didn’t have a platform and host already in mind.
But I’m wondering if this would actually be used? And would anyone here be interested in contributing?
It’s always tomorrow somewhere :p As for proprietary vs FOSS (typing this from Arch, btw) - I really get it. However, with things like hosting in general which I’ve struggled with finding good solutions for my edits a lot I’m not sure there really is a good solution here. I’d argue that since this is meant to potentially be a resource for all Trek meme editors and/or content creators, then odds are that pure accessibility and low maintenance/hosting costs are going to have to be considered first and foremost. The point I’m trying to make is that IMO this should be able to benefit everyone that could use such a thing, which will unfortunately (IMO) require something proprietary - especially if it actually takes off and eats up a good amount of bandwidth per month. If someone hosted it on their bare metal at home, there could be a lot of a) security risks and b) down time.
Also, this looks promising at a glance. Take a look: https://meta.miraheze.org/wiki/Miraheze Admittedly not FOSS, but it is opensource.