this post was submitted on 17 Jun 2023
184 points (100.0% liked)
Technology
37739 readers
500 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
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
Yep, on regular intervals your instance asks for the latest data from the remote community and that's what it serves to its users. So it doesn't matter if 1 person or 100 are subbed on asingle remote, it's the same number of calls.
Is there a reason for working like this and not simply be a portal to the other instance's community?
I'm not a lemmy dev but my understanding is that doing it that way would end up exponentially increasing latency once you start getting nested links to communities - accessing a post on lemmy.world that was linked to lemmy.nz and then finally read through a beehaw account, for example, might have to jump through at three servers on opposite sides of the world before getting to me rather than just being served directly across the pacific from beehaw's server to me!
Probably for reliability and stability — otherwise, every view from every federated instance would create a new request to the hosting instance. The protocol itself would basically DDoS smaller instances. Also you can still read the cached version on your home instance if the remote instance is temporarily down.