Lemmy.world should close registrations and not allow new communities
Things have been incredibly unstable there. Until things stabilise, they should force the traffic elsewhere.
You are viewing a single comment
Things have been incredibly unstable there. Until things stabilise, they should force the traffic elsewhere.
Are you really trying to gatekeep the internet?
No, I'm trying to find a solution to a very real problem. World has had at least partial outages every day for a week now. It affects everyone when it gives the impression that things don't work and people aren't able to create content to attract new people to the wider platform. But have an upvote anyway.
What?
People can subscribe to other instances or even host their own. If the majority of users end up on the same instance then what's the point of decentralization? Even worse if the traffic it generates for that instance makes it unstable.
Should the admin do nothing until the instance is mostly down with windows of uptime throughout the day?
A big part of the problem is that a new instance starts with zero database content and PostgreSQL performs fine with the way Lemmy organizes the data. But then there isn't anything for people to read, and search is only going to pick up local stuff.
There's no perfect solution but I certainly didn't move to a decentralized platform only to see it be intentionally centralized through inaction.
The quantity of users on Lemmy I still consider to be pretty low, the performance bugs need to be addressed on a big server. Bugs like not having a WHERE clause on an UPDATE hitting 1500 rows in a table (one row per server) instead of 1 single row... these need to be shaken out.
The errors of the overload themselves have been a way to throttle growth of the big servers. People were not able to insert new posts and comments into Lemmy.ml - reducing outbound federation activity too, and they went to other servers. This went on all of June and July.