The problem is that everyone has consolidated on one gargantuan server. The whole point of the fediverse is to spread out so no one server is carrying the entire load. I’m currently using lemm.ee and have experienced none of the issues being discussed here.
But yes, I agree that it could be a potential turn off for newcomers.
At the time of this writing, I have accounts on two servers. One on the big server, and one on a tiny server.
Obviously, the gargantuan server’s biggest issue is performance. That will probably improve with time, but with its size comes some noticeable benefits, which I will touch on shortly.
The tiny server, which I actually joined first, is blazing fast, but I’ve run into constant issues trying to find communities and posts that the bigger server can find no problem. Initiating a federation request is not intuitive at all, and your average user is going to wonder why the hell so much stuff isn’t showing up when they click All on a smaller server.
I tried manually copying my subscription list from the gargantuan server to the tiny one. It was quite a chore, even though it got better in 0.18. Most of the communities returned a “not found” error. Having to retry a search several times or manually input the URL and reload the page several times until the server can find the community on the remote server is not something the average user is going to want to deal with, so they’ll end up on the huge servers that already know about the communities on the other large servers, if they don’t give up.
Hopefully this gets better, but that’s my best guess as to why everybody ended up on the gargantuan servers.
Spreading out would help the performance of the servers but would still expose inefficiencies in the backend systems that they use to talk to each other. The page might load, but the content will be all kinds of fucked.
The problem is that everyone has consolidated on one gargantuan server. The whole point of the fediverse is to spread out so no one server is carrying the entire load. I’m currently using lemm.ee and have experienced none of the issues being discussed here.
But yes, I agree that it could be a potential turn off for newcomers.
At the time of this writing, I have accounts on two servers. One on the big server, and one on a tiny server.
Obviously, the gargantuan server’s biggest issue is performance. That will probably improve with time, but with its size comes some noticeable benefits, which I will touch on shortly.
The tiny server, which I actually joined first, is blazing fast, but I’ve run into constant issues trying to find communities and posts that the bigger server can find no problem. Initiating a federation request is not intuitive at all, and your average user is going to wonder why the hell so much stuff isn’t showing up when they click All on a smaller server.
I tried manually copying my subscription list from the gargantuan server to the tiny one. It was quite a chore, even though it got better in 0.18. Most of the communities returned a “not found” error. Having to retry a search several times or manually input the URL and reload the page several times until the server can find the community on the remote server is not something the average user is going to want to deal with, so they’ll end up on the huge servers that already know about the communities on the other large servers, if they don’t give up.
Hopefully this gets better, but that’s my best guess as to why everybody ended up on the gargantuan servers.
Spreading out would help the performance of the servers but would still expose inefficiencies in the backend systems that they use to talk to each other. The page might load, but the content will be all kinds of fucked.
It’s a huge turn off. And federation itself adds to the problem when the servers don’t match up properly.