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

Technology

37720 readers
280 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
3
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
5 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
[–] lucien@beehaw.org 0 points 1 year ago (1 children)

Maybe I should clarify with "each user successfully spun up..." I'm mostly curious if the 5000 microservers trying to federate is a more sustainable access pattern than 5000 users hitting the website.

Since federation is an async process, it can be optimized on both ends in a way that user browser requests cannot.

At the same time, federation would overall result in more bandwidth being used because not every user wants to view every post in the frontend.

[–] rysiek@szmer.info 1 points 1 year ago

Maybe I should clarify with “each user successfully spun up…” I’m mostly curious if the 5000 microservers trying to federate is a more sustainable access pattern than 5000 users hitting the website.

Sustainable in what sense?

It's way more sustainable in the sense of "one website is not controlling the entirety of the experience of a given type of service for 5000 users", for example. I think it's important to talk about specific kinds of sustainability, and specific threats to it.

Things to consider (apart from bandwidth-related considerations):

  • technical knowledge necessary to safely and securely run and maintain a service
  • space, time, and resources (including financial) to do so
  • ability, willingness, and energy to moderate a service (this is where Big Tech platforms are falling flat on their faces, for example, and where smaller fedi communities work pretty damn well)