TenForward: Where Every Vulcan Knows Your Name
/c/TenFoward: Your home-away-from-home for all things Star Trek!
Re-route power to the shields, emit a tachyon pulse through the deflector, and post all the nonsense you want. Within reason of course.
~ 1. No bigotry. This is a Star Trek community. Hating someone off of their race, culture, creed, sexuality, or identity is not remotely acceptable. Mistakes can happen but do your best to respect others.
~ 2. Keep it civil. Disagreements will happen both on lore and preferences. That's okay! Just don't let it make you forget that the person you are talking to is also a person.
~ 3. Use spoiler tags. This applies to any episodes that have dropped within 3 months prior of your posting. After that it's free game.
~ 4. Keep it Trek related. This one is kind of a gimme but keep as on topic as possible.
~ 5. Keep posts to a limit. We all love Star Trek stuff but 3-4 posts in an hour is plenty enough.
~ 6. Try to not repost. Mistakes happen, we get it! But try to not repost anything from within the past 1-2 months.
~ 7. No General AI Art. Posts of simple AI art do not 'inspire jamaharon' and fuck over our artist friends.
Fun will now commence.
Sister Communities:
Want your community to be added to the sidebar? Just ask one of our mods!
Honorary Badbitch:
@[email protected] for realizing that the line used to be "want to be added to the sidebar?" and capitalized on it. Congratulations and welcome to the sidebar. Stamets is both ashamed and proud.
Creator Resources:
Looking for a Star Trek screencap? (TrekCore)
Looking for the right Star Trek typeface/font for your meme? (Thank you @kellyaster for putting this together!)
view the rest of the comments
On the other hand, the advantage of using markdown platforms (like Docsify) is that they can be hosted directly from the repo without having to be deployed on a host; yeah, hosting, I forgot to mention, can be a bear to maintain and is not something I'd like to take on or pay for. That shit can get expensive. There are wiki service providers like Nuclino that have a free tier of hosting, but they all look like they're closed source. One of my requirements is it be open source so anyone can fork it and do what they want with it (also addresses the "what if I get hit by a bus" question). The same goes for other collaborative CMS packages, I don't wanna deal with hosting.
So something like Docsify would have a higher barrier to entry, but it's also something I am comfortable with/capable of managing. Even if we had someone volunteer to take on a DevOps role and set up & manage a deployment pipeline, there's still the issue of the hosting costs. Yeah lol, it sorta comes down to money, and I unfortunately I think I gotta draw a hard line in favor of free open source over free proprietary. omg I don't know if that sentence makes sense. I'm so baked, what time is it? Is it tomorrow yet?
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.
Lol jawa21 you missed a great "I use Arch BTW" opportunity. Hmmm, Miraheze, I didn't know it existed! I think technically it might count as a FOSS implementation, as it is free and uses Mediawiki. Since they manage the hosting, there wouldn't be any direct access to the instance's code, but there's still the option to do a data export in the event of a necessary migration.
This does look good on paper, lemme look at this some more. I'm trying to picture how this would work for this use case, and I don't see any red flags just yet. Yeah, solid so far.
Omg I feel called out. Haha, the context of accessibility is slightly different here, but I'm actually the resident web accessibility expert at work. Yeah, I use a screen reader to test functional WCAG compliance for some of our products and have to make recommendations for fixes, if not fix it myself, amongst other things. I'm actually working on a presentation about it. Yeah, this thing would serve others best if it is inclusive. Aight I gotta jet, lemme get back to you on this.
Any other thoughts that come to mind, don't hesitate to post it here.
I created an account at Miraheze and put in a request for a wiki, which has to be manually approved. The queue has a three day backlog at the moment, so it might be a hot minute before I can give it a test spin. That is, if it's approved.
I'm probably showing my age, but I really miss Geocities, you know? You had all kinds of cool niche special interest sites about all kinds of things, and this would've fit right in there.
Cool. I'd like to see how things turn out. And NeoCities is there if you really want to hand code a wiki lol.
omg I didn't know that was a thing