Didn't forget debugging, diagnosing, and reprogramming Voyage which has left the solar system.

I'm gonna need you to tell me step 0. I followed your instructions to the letter and all I got out of it was a very confused lunch.

fun fact, that would make the transmission slower.

According to wikipedia cat5 cable has a propagation delay of 5.30 ns/m, which works out to about 62% of the speed of light. While radio waves propagate at the speed of light.

Come to think of it, who are the real aliens?

I'm obsessed with the idea of a slow-paced FPS game now. Imagine logging in once or twice a day, picking a shot and seeing if whoever it is is still there the next day.

With 30 ping

Yeah wtf, 100ms is great.

300ms is the average reaction time in humans. Less than 100ms reaction time would be insane and I'm pretty sure it's something no one has actually achieved.

For me these days my ping still jumps between 300 and 1k. 80ms is a good day

As far as we know so far..

This’ll be perfect when it’s about 19 hours after the original post.

I understand that Voyager is nearly one light day away, but I can't comprehend it.

It seeks the Creator.

Now THAT was the Voyager reboot we didn't know we all wanted until it dropped.

Haven't we all?

PvP - player vs ping

Lemmy.nz has had some serious problems with federation with World, and a few other instances, because the way federation works, or worked, is an item would be sent, the receiving server would acknowledge receipt, and the next thing would be sent.

We ended up four days behind at one point.

They don't use anything for their latency. I've looked into the space network they have, what protocols they use and what they do about the massive delays.... Just a little bit, I don't know it super well or anything, but from my understanding, the "network" they use is more about assurance than delivery speed.

The publicly available version of what they use is called delay tolerant networking, which essentially uses a mesh of nodes that may, or may not be able to communicate to other nodes at any given time. As messages are sent, they are relayed from node to node as connectivity allows until they get to a base station for final delivery. It's a bit like the mail system, but instead of large centralized sorting facilities, you only have local post offices. The message is sent from one office to another until it leapfrogs it's way to the destination. It can wait at one post office indefinitely until a path opens up to the next one.

In the case of delay tolerant networking, it basically sends it along to the next station in the mesh, and that station will confirm the delivery of the information, which is when the sender can remove the message from its buffer.

Ideally, the nodes should have some type of non-volatile memory (like nvram) to store pending deliveries, so nodes don't waste power trying to keep the information in their volatile memory (RAM).

Terrestrialy, we use DTN for tracking stuff like the movement of animals in large and unserviceable areas (where mobile networks like LTE, don't exist), such as deserts and undeveloped forests. As the trackers on the animals come within range of another tracked animal, updates occur, and when either gets near enough to a base station to upload the information, then the updates are sent out to the records systems.

Don't ask me how the logic works to figure out when to push data one way or another. I haven't gotten that deep into the protocol yet.

Anyways, for NASA, the information is sent to satellites, which relays to the rover eventually. In NASA's case, they can directly transmit, from Earth, using microwave arrays, to the satellites in orbit around Mars if we want.

I'm not sure on the specifics of how they have their version of DTN setup, so I'm only speculating at best.

They don't mitigate latency, they simply account for it, and work with that as part of the problem.