Lucas

Wasn’t Soylent Green algae based at first?

Love that idea. Servers could distinguish if they want to be a general ‘home instance’ for users, and those that opt in could communicate with each other and push accounts around as necessary. Servers could calculate their likelihood to accept a new incoming account based on some heuristics the admin could set, with sensible defaults. That way the system would self-balance itself as new instances appear and as mature ones reach capacity. Of course for that to work there would have to be some central authority keeping track of account locations for login purposes.

Spreading out is definitely the way to make this thing work. I’m sure there is more that can be implemented to help with federation speed, making sure you have all comments, etc. Those are solved with a monolith instance, but as we see you need a monster server to do it. I think instances averaging less than a few thousand users each will be the way to move forward.

This is the main issue I see right now as well. I created my own instance for my account to live on, just so I know it will be there as long as I want it to. But that doesn’t do anything for communities I’m subscribed to that could, potentially, be on an instance that later goes down.

I think communities of similar topics are going to need to coordinate in the long run, and perhaps run their own instance to house their communities. This way the folks running the community and the folks hosting it are one in the same. You’d have instances that mainly house users, and perhaps a community or two. That’s where most folks would have their main account. Then you’d have instances that mainly house content, with few users besides the moderation/admin team(s).