• 0 Posts
  • 33 Comments
Joined 9 months ago
cake
Cake day: November 11th, 2023

help-circle











  • i’m like way, way late on this, but i just stumbled on this thread and have to say your analysis is well thought out and you explained time travel narrative structures very succinctly.

    but your analysis completely falls apart because, and i’m not sure how, but you missed the entire fucking point of Terminator 1. In the extended edition of T2 there’s a scene in the first 15 minutes where Kyle explains it again for those in the back.

    "The future is not set.”

    added in T2,

    “The future is not set. There is no fate but what we make for ourselves.”

    That’s what Kyle comes back to explain to Sarah. Until she understands that message and acts on it, Kyle is acting in a “ST” structure. Once the terminator is destroyed by Sarah, the MT is opened up. We can speculate that Kyle was supposed to kill the terminator with his last pipe bomb, but really any moment could have caused that schism. What’s important is that Sarah is now self-reliant in terms of killing machines. Fate is what Sarah was fighting, almost a meta-antagonist. That is her struggle through the entire Terminator franchise.

    Terminator 1 is a time travel story that starts as a ST narrative, and by Sarah’s actions in the final act, becomes a MT narrative. T2 just further explores the opened-up MT narrative. There’s no inconsistency between the final moment of T1 and the opening of T2. Your gripe seems to be entirely with the first movie based on a limited understanding of the larger themes and philosophies explored in the narrative.

    Terminator 2 is a damn fine sequel and a hell of a film on its own merit.









  • not that it would ever happen at critical mass, but i think there’s a valid criticism here.

    when i first heard about federated platforms my initial impression was that it was more of a “hub and spoke” system than the free-for-all it currently is. i still think there’s some merit to having a few larger “parent” instances that handle the federation between each other, while individual instances pull federation via their “parent” instance. seems like this approach would help reduce some of that overhead, but that does jeopardize the open nature of the protocol.

    it’s a tough thing to balance.