427
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
427 points (92.8% liked)
Fediverse
17425 readers
89 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 4 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.
I know you are salty about how you are getting treated over at GitHub, but you should look at it objectively, Blaze is clearly advocating that people join top instances that's not lemmy.world or lemmy.ml, not nobody instances that only have 1-2 users. They certainly aren't going offline as quickly as they come online.
No, it isn't about my personal treatment. It's about the cultist attitude you have towards Lemmy and the leaders without any ability to see what they are doing behind the scenes with the code. I know cults and religious faith is how many people enjoy the world.
A 2-line SQL TRIGGER removal takes about minutes to fix. It was crashing the entire site constantly. They sat by and asked for donations of money.
Then go fix it and open a PR
Do you think I am the one who created the mistake or something? That I have access to the servers to install it?
It's so odd to me that you respond this way, as if it was my coding mistake. It isn't even me who opened issue, that is GitHub "makotech222" - is that your answer to them?
I don’t believe they’re insinuating that you were the one that created the mistake. Rather, that you seem to be knowledgeable of the specific problem and may be the one most capable of fixing it. The two line fix may be obvious to you, but may not to the main Lemmy devs. Until phriskey got involved, a lot of db tuning was being avoided (they’re responsible for most of the big db improvements this version).
and I did not understand or properly relate to that project culture. It had been that way for years and I should have "read the room" "go with the flow".