94
TNG S5E6 The Game
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 24 Oct 2024
94 points (99.0% liked)
TenForward: Where Every Vulcan Knows Your Name
3895 readers
1284 users here now
/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. Remember that diversity and coexistence are Star Trek values. Any post/comments that are racist, anti-LGBT, or generally "othering" of a group will result in removal/ban.
~ 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'
~ 8. No Political Upheaval. Political commentary is allowed, but please keep discussions civil. Read here for our community's expectations.
Fun will now commence.
Sister Communities:
Want your community to be added to the sidebar? Just ask one of our mods!
Honorary Badbitch:
@jawa21@startrek.website 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!)
founded 11 months ago
MODERATORS
Are we so sure about that ordering?
Depends. Is there enough coffee to accomplish the latter, or must the second be carried out to fulfill the first?
Okay fr fr, but...
Twovix (dammit! now I'm stuck with that spelling!?) isn't even the only pair of beings that she murdered this week:-).
I think you announce your intentions before the coffee, then you get the coffee so you can enjoy it more.
It doesn't hurt watching him run around the ship pleading for help, and while making eye contact nobody steps forward to really break his spirit.
So dark. Love it.
We should do it in a different order each time
Randomization subroutine...
At a technical level it is totally possible. You just make the URL resolve to a different image each time.
I'm not sure it would be appreciated by the mods
(Wouldn't work anyway, due to Lemmy's caching approach iirc)
It should as Lemmy will pull any image that is linked in the markdown.
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.
Interesting... thank you for sharing!
It seems caching doesn't do much, even while also being a big pain for instance admins - so much so that it is explicitly made voluntary.
Perhaps that is why PieFed is going so hard on integration with PixelFed and now Loops.