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, neither is supporting people who actively want to kill those groups. 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
But doesn't the instance it is ~~delicious~~ (edit: FUCK AUTOCORRECT!) delivered to do that, and then if the image changes later, it wouldn't update? And then I thought further that people from other instances likewise pull from the host instance, rather than the original source.
Except maybe Lemmy.world, if the image caching was added in a more recent update, which I thought was the case?
Anyway, I'm not saying that any of this happens, only that I thought it might.
Just hot link the image to a host that you have control of instead of uploading it to lemmy. Then you can change the image anytime you like and it won't be affected by any caching on lemmy.
Oh, does image caching not apply to remotely hosted content? Well, then yeah, that sounds good.
That is what I have noticed. When I use Catbox, the exact Catbox URL appears on every instance. But when I upload directly to my instance, federated posts use their own cached image instead of the one from my instance.