Technology

1928 readers

7 users here now

Rumors, happenings, and innovations in the technology sphere. If it's technological news, it probably belongs here.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 3 years ago

MODERATORS

[email protected]

Hypothetical: What would happen if every user in the fediverse hosted their own server? (beehaw.org)

submitted 2 years ago by [email protected] to c/[email protected]

31 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

[–] [email protected] 2 points 2 years ago* (last edited 2 years ago) (1 children)

I'm also running my own instance, very few users and everything is really fast. Because I'm not on the same instance as all those users.

I guess with time, people will understand what I'm talking about. There are no downsides to using an instance with a low amount of users when you have federated technology.

I would love to get more users actually, just to help spread the load and to provide a good experience.

[–] [email protected] 0 points 2 years 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.