this post was submitted on 05 May 2024
14 points (100.0% liked)
Science
13023 readers
130 users here now
Studies, research findings, and interesting tidbits from the ever-expanding scientific world.
Subcommunities on Beehaw:
Be sure to also check out these other Fediverse science communities:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
When I first heard the term "fediverse", it immediately made me think of some sort of vast interplanetary network. And let's face it: a fediverse-like model is really what you would need if you had settlements scattered throughout the solar system. A monolithic, centralized service would be awful, given the reality of communication lag and likely limited bandwidth.
So let's say lemmy (or more generally activitypub) were to go interplanetary. How would that work out? You set up your first instance on Mars. Any content that's posted there will be immediately available to your fellow Martians. Earthlings who subscribe may also be able to view it as their instances cache the content, albeit after some delay.
But the trouble starts when Earthlings want to start contributing to the discussion. If they have to wait the better part of an hour to get a single comment lodged, it's going to get old fast.
So you would need to allow the Earth side to branch off to some extent from what's happening on Mars. Then eventually, something like a git merge would try to bring it all back together? I wonder if that would work?
Isn’t it currently also cached on the instance where the user is registered?
An earthling should not register on the mars instance or vice versa because of latency.
But commenting from the point of view of the earthlings should be smooth
So you're saying the comments themselves get cached on the local instance where the user is registered before being synced with the remote community-hosting instance?
I honestly don't know how these things work internally, but had assumed the comments needed to go straight to the remote instance given the way you can't comment once said instance goes down? You can still read the cached content though.