this post was submitted on 12 Jun 2023
23 points (100.0% liked)

Technology

37716 readers
323 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
alyaza@beehaw.org
TheRtRevKaiser@beehaw.org
gyrfalcon@beehaw.org
rs5th@beehaw.org
coldredlight@beehaw.org
Los@beehaw.org
SemioticStandard@beehaw.org
TheRtRevKaiser@kbin.social
remington@beehaw.org
23
Hypothetical: What would happen if every user in the fediverse hosted their own server? (beehaw.org)
submitted 1 year ago by lucien@beehaw.org to c/technology@beehaw.org
23 comments fedilink hide all child comments
 

What would happen if instead of users swarming existing servers when a fediverse service was put in the spotlight, each user spun up their own micro-instance and tried to federate with existing servers?

There's always the odd person who decides to host a personal fediverse service in their homelab for themselves, but would the fediverse work if that was actually the primary mode of interaction? Or would it fail in a similar way to now where the servers which receive the most federation requests need to scale up?

Presumably the failure modes for federation are easier to scale than browser requests since it's an async process.

you are viewing a single comment's thread
view the rest of the comments
[–] nii236@lemmy.jtmn.dev 1 points 1 year ago

Same, but the communities will always congregate around one or two big instances because there’s no point building a tiny community with only a few people on your own instance.

What ends up happening is these micro deployments end up just being an identity server and caching layer.