Yea it’s one of those awkward things I suppose, where the instance (.world) is big enough that its operational concerns are kinda at odds with where lemmy as a project is up to.

With that many users, who also kinda expect a more reddit-style experience AFAICT, a certain amount of professionalism, stability and, in effect, slowness, is expected. And that’s great.

But meanwhile lemmy is a small essentially underfunded project doing its best with a small group (2 main and a few voluntary on the side), which means bugs and then bug fixes and tweaking until things work … all of which works well over a distributed array of smaller instances so that no single node is a major let alone fatal point of failure.

And so we’ve got this situation now where you could be critical of how lemmy.world relates to the bug fixing and testing load on the lemmy-verse. lemmy.world is likely the best funded instance (last I checked their donations exceed their infra needs) and yet the job of testing and working through bugs is offloaded onto all of the other smaller instances while they wait until it’s all been ironed out. I don’t know if it’s a fair critique in the end, but it certainly seems to be there and worth considering.