For the rest of your post, I don’t know what that has to do with people aggreating on LW.
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.
nor have they closed signups on lemmy.ml.
You know what is easy to do, lie and make-up facts. It is so much easier to bullshit to be popular around here.
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.
If they are closed, you wouldn’t even be able to submit a registration application.
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
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