2 ms·

OK, so 10 light-hours apart 120h on the wall at starbase A starbase B looks at starbase A, sees it's 110h, but the distance is 10h, so sets their clock to 120

OK, so 10 light-hours apart 120h on the wall at starbase A starbase B looks at starbase A, sees it's 110h, but the distance is 10h, so sets their clock to 120h starbase C sees starbase B's clock as 110h but knows it's 10 light hours away and A as 100h and 20lh away, so sets their clock to 100+20h or 120h starbase D also sets their clock at 120h event occurs at 200h wall clock in starbase B event is seen at 210h wall clock in starbase A, 210h in C, 220h in D OK, your spaceship could tell starbase D the event has occured when it pops out at t=201h, but so what. How does starbase D get a message back to starbase B back before to get them to prevent the event from occuring?

Dylan16807 6y ago
Where did you get 201h? And you completely changed the layout?? I didn't want you to change the distance between A and B. But I can make something work with the new numbers. Here: At 120h according to the starbases, everyone sets their clocks, just like you said. Event occurs at 200h in starbase B. A near-light-speed wormhole is passing by B and D in its own reference frame. As far as it can tell, the starbases have their clocks synced really badly. In this wormhole's reference frame, it's simultaneously "200h" at starbase B and "182h" at starbase D. A messenger ship launches from B right after the event, goes through the wormhole, and lands on starbase D at 183h. So far, we're paradox-free. We can tell D the results of the event before the light reaches them, but that's not new. People do that all the time with the normal wormhole. And since we're 20 light-hours away from B, any signal we send from here would arrive too late to affect anything. But then the ship takes the normal wormhole, the one that's always connecting A and D. That wormhole always agrees with the clocks onboard the starbases. The ship enters at 183h, and exits at 183h, now at starbase A. Then the ship sends a signal toward B. The signal arrives at B at 193h. This is the same location as the event, 7 hours before it happens.

Dylan16807 6y ago

Where did you get 201h? And you completely changed the layout?? I didn't want you to change the distance between A and B. But I can make something work with the new numbers. Here: At 120h according to the starbases, everyone sets their clocks, just like you said. Event occurs at 200h in starbase B. A near-light-speed wormhole is passing by B and D in its own reference frame. As far as it can tell, the starbases have their clocks synced really badly. In this wormhole's reference frame, it's simultaneously "200h" at starbase B and "182h" at starbase D. A messenger ship launches from B right after the event, goes through the wormhole, and lands on starbase D at 183h. So far, we're paradox-free. We can tell D the results of the event before the light reaches them, but that's not new. People do that all the time with the normal wormhole. And since we're 20 light-hours away from B, any signal we send from here would arrive too late to affect anything. But then the ship takes the normal wormhole, the one that's always connecting A and D. That wormhole always agrees with the clocks onboard the starbases. The ship enters at 183h, and exits at 183h, now at starbase A. Then the ship sends a signal toward B. The signal arrives at B at 193h. This is the same location as the event, 7 hours before it happens.