this post was submitted on 04 Jul 2023
13 points (100.0% liked)

Daystrom Institute

3448 readers
15 users here now

Welcome to Daystrom Institute!

Serious, in-depth discussion about Star Trek from both in-universe and real world perspectives.

Read more about how to comment at Daystrom.

Rules

1. Explain your reasoning

All threads and comments submitted to the Daystrom Institute must contain an explanation of the reasoning put forth.

2. No whinging, jokes, memes, and other shallow content.

This entire community has a “serious tag” on it. Shitposts are encouraged in Risa.

3. Be diplomatic.

Participate in a courteous, objective, and open-minded fashion. Be nice to other posters and the people who make Star Trek. Disagree respectfully and don’t gatekeep.

4. Assume good faith.

Assume good faith. Give other posters the benefit of the doubt, but report them if you genuinely believe they are trolling. Don’t whine about “politics.”

5. Tag spoilers.

Historically Daystrom has not had a spoiler policy, so you may encounter untagged spoilers here. Ultimately, avoiding online discussion until you are caught up is the only certain way to avoid spoilers.

6. Stay on-topic.

Threads must discuss Star Trek. Comments must discuss the topic raised in the original post.

Episode Guides

The /r/DaystromInstitute wiki held a number of popular Star Trek watch guides. We have rehosted them here:

founded 1 year ago
MODERATORS
 

SNW S2E02 introduce a new quirk of the canon: The time "push back", such that there will be some events (let's just call it Canon Event) that will always come about in Prime Timeline, albeit in different actual time. Aside from the aforementioned Eugenic War, I can think of a few other so-called "inconsistency", such as how there are already Cloaking technology for both Romulans and Klingons before Kirk's mission, despite TOS dialogue implies that Romulan first got cloak during Kirk's mission, and then transfer technology to Klingon. (I think the current explaination is different cloaking technology, which have various quirks.)

So here's the question: Under what situation would you consider "Time Pushback" being an acceptable explaination for discrepancy??

you are viewing a single comment's thread
view the rest of the comments
[–] maplealmond@startrek.website 7 points 1 year ago (1 children)

As a general rule, unless given an explicit explanation for discontinuity on screen, it should be the explanation of last resort.

The problem is that as an explanation it can be used for everything. Consider any shot production error that might happen. Actually let's use one of my favorite TNG episodes for discontinuity: Parallels. In the final scene of Parallels, there is a continuity error, where a bow switches sides.

Does this mean we should perform an inception style deep dive and say perhaps Worf is still jumping universes? Could we use this to, in fact, explain ANY minor production error?

I mean we could. But that's probably not what's intended by the authors.

For example I am very much a fan of the idea that early in TNG's run the Ferengi still valued gold and later on they do not, and this matches up with better and better replicator technology eventually being able to create gold at scale. But also, maybe it's just temporal discontinuity.

Can we reconcile Picard's relationship with his mother with what little we see from TNG and what we see in ST: Picard? This can be a fun exercise. But we can also say "Eh not the same Picard."

The idea that Khan is destined to happen is a heads on explanation for the intractable problem of Star Trek is rerooting its history into our modern history. Star Trek is, after all, a vision of our future and that vision has changed from the 1960s. This is a change designed to add some meaning to the show.

On the other hand, if "time pushback" is used to explain anything and everything on the show, it runs the risk of becoming flat out meaningless.

So when would I consider it an acceptable explanation? Whenever it's given as the explicit explanation, or maybe if there's a very clear connection.