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. 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. 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:
@[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
What about the Rikers?
Riker was split during the process, since the person doing the teleporter thing did an ill-advised/unprecedented thing and basically tried to transport them twice simultaneously, using two transport beams, and reintegrate the patterns later, so that the interference didn't cause them to lose too much of him, and they had enough to use the pattern repair mechanisms to patch any gaps (more than 50% lost is generally considered unrecoverable).
Part of the interference resulted in one of the transport beams being echoed down to the planet surface, and the transporter presumably did its best to fill in the gaps so that they didn't just get half a Riker, and they ended up with two whole Rikers instead.
If it was a simple clone -> store -> kill/replicate, Scotty wouldn't have needed some whole convoluted song and dance to keep someone in the buffer for decades, and Franklin'd not have died.
It does beg the question of whether you could intentionally do it. Scotty was very limited by the technology available to him, but the later versions of the Enterprise might have been able. It's interesting to think about. All of that said, I think you support your position very well and I appreciate the thoughtful response!
Hm, in theory, possibly, but not by doing Scotty's method, since that was basically constantly redoing the transport over, and over internally, without actually materialising the pattern. DS9 has transport patterns moved into regular computer storage, but the requirements were considerable. 5 people required the combined computer storage capacity of the entire station.
If you can do that, it doesn't seem impossible to copy the pattern itself using the computer, feed the copy right into the transporter, then materialise the copied pattern. As far as the transporter is concerned, you're just transporting the same thing a whole bunch, loading the patterns into the buffer from a different device.
You would need more than just a transporter to achieve that, though.