Lemmy.world should close registrations and not allow new communities
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.
26 comments
-
-
You are welcome to go to another instance to reduce lemmy.world load.
-
I'm not on world. I don't even have a world login. 🤷🏾♂️
-
I don't think you understand how the fediverse works of you think that solves the problem - lemmy.world being unstable effects its ability to federate properly with other instances
Badly managed popular instances unfortunately affects the whole fediverse
-
-
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?
-
-
Things have been incredibly unstable there.
I wish lemmy.ml (also unstable) or lemmy.world would hand out a (nearly) full copy of the database so we can get more analysis done on PostgreSQL performance behaviors. Remove the private comments and password /2fa/user, or whitelist only comments/posts/communities/person tables - but most everything else should already be public information that's shared via the API or federation anyway. it's the quantity, grouping, and the age of the data that's hard to reproduce in testing. And knowledge of other federated servers, even data that may have been generated by older versions of Lemmy that new versions can't reproduce.
It's been over 60 days of constant PostgreSQL overload problems and last week Lemmy.ca made a clone of their database to study offline with AUTO_EXPLAIN which surfaced a major overload on new comments and posts related to site_aggregates counting (it was counting each new post/comment against every known server, not just the single database row for a server).
I have an account over on World too, and every major Lemmy server I use throws errors with casual usage. It's been discouraging, I haven't visited a website with this many errors in years. Today (Sunday) has actually been better than yesterday, but I do not see many new postings being created on lemmy.ml today.
-
[This comment has been deleted by an automated system]
-
subscribe to every community, and let federation load overwhelm your server.
Did that, takes lots of time to wait for the content to come in.... and there is no backfill. Plus I suspect that the oldest servers (online for several years) have some migration/upgrade related data that isn't being accounted for.
-
-
-
26 comments
I agree. Wants the point of a decentralised platform if most of it's users are on a single instance.
Plus it's not a good look from a new users perspective if the platform appears down every few hours.
It's so that users have a choice of joining different instances. If .world is particularly well managed and provides amenities for users and has the capacity, there's no reason that new users shouldn't join.
The junk communities in every instance are a problem.
It clearly doesn't have the capacity and until certain pull requests are merged, the capacity for an instance is ~2000 users, world is way over that.
As I understand it, Lemmy.world's maintainer wants to own the biggest Lemmy server ever, just like they own one of the biggest Mastodon servers. It's a feature, not a bug.