444
Lemmy.world down, probably following the upgrade. A reminder to move to smaller instances for a better experience
(files.catbox.moe)
this post was submitted on 29 Jul 2023
444 points (93.2% liked)
Fediverse
17700 readers
3 users here now
A community dedicated to fediverse news and discussion.
Fediverse is a portmanteau of "federation" and "universe".
Getting started on Fediverse;
- What is the fediverse?
- Fediverse Platforms
- How to run your own community
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
A reminder that this constant advice people blindly parrot to install and flock to smaller instance has now created something like 1000 new servers in 50 days that are poorly run and already going offline as quickly as they went online.
Github Issue 2910 is the kind of PostgreSQL problems that the developers ignored for months and people still defend the developer choices to have the code doing real-time counting of every single comment and post for numbers nobody needs to needs done in real-time.
PostgreSQL is voodoo to this project, they do everything they can to avoid going to [email protected] community and asking for help, learning 101 about how to fix their SQL TRIGGER logic like Github Issue 2910 spelled out June 4.
And this will always.. always be the biggest problem in the FOSS community.
"I dont like X, so I'm going to leave and make my own version of X"
So userbases get spread thin, manpower gets spread thin, developers get spread thin, and the user experiences degrades for everyone until it pushes them back to the bullshit websites and products.
And, factually, the project leaders telling everyone to create 1000 new instances and shutting down sign-up on Lemmy.ml caused more performance problems.
They had a bug in their PostgreSQL TRIGGER logic where 1500 instances were updating + 1 comment and +1 post counting instead of WHERE site_id = 1, a single database row. So each new Lemmy server that went online made the table larger and crashes more frequent on lemmy.ml
The amount of disk writing by lemmy was ignored
They've neither told people to create 1000 new instances, nor have they closed signups on lemmy.ml.
Again, you should really stop revolving your entire life over one GitHub issue, and go touch grass.
You know what is easy to do, lie and make-up facts. It is so much easier to bullshit to be popular around here.
It's disgusting the people who lie like you do and believe liars: https://lemmy.ml/post/2421636
The irony in you saying that, and posting second-hand recounts by other people. They aren't closed. If they are closed, you wouldn't even be able to submit a registration application.
Man reading this thread, you're kind of a dumbass. Especially if you think rewording your answer here from the last reply to reframe to current time period vs what was being talked about would throw off the scent
They've not closed sign ups. Requiring approval of sign ups, is not closing sign ups. How am I wrong?
Currently no. But they had, which was clearly stated as it was talking on the past.
Show me in the code. Because I have closed the registration on my Lemmy server, and it does not turn off the "Sign Up" link or HTML input fields. But you sure like lies and deception