Getting private messages. from Lemmy users who say “go back to spez”. The Lemmy Community can call out the leadership of Reddit by name, they drone on and on about hate being a core value in hteir life, and how hating on spez is so important.
But when you have valid documented criticisms of the Lemmy leadership not reporting their server crashes and sharing crash logs, they private message you - because saying things out loud in public isn’t how Lemmy is run. “High Performance” is on the front-page of Github for the project, and if you have something to say about that, you are the one who needs to be socially “corrected”.
Here is what I’m getting in private messages because I keep pointing out that the major sites are not opening bugs on Github and sharing the crash logs:
I don’t want features, I think the “High Performance” claim is a big problem of project communications and expectations.
I think the site is crashing constantly, every day, for 32 days I’m using it for 6 hours a day. Nobody is reporting the crashes, and nobody seems to even notice them who is running the project. Where are the announcements that data is being lost?
Caching and turning off features/code, such as the “activity” database table, are obvious ways to deal with a crashing server. Yet they obviously aren’t being implemented. A caching layer between the API and the SQL database would provide immediate relief. This isn’t a “feature”, this is essential changes in a critical time period for the project.
Testing, I personally went around sharing information about testing, because the project isn’t getting enough testing… The person who private messages me seems to think that posting on Lemmy and testing Lemmy and identifying the problems doesn’t matter.
Server logs need to be shared. That’s really really really holding back the project. Caching needs to be added.
It also says a ton that they private messaged me back in June 25, 2023 before the Reddit June 30 API cutoff influx… as they didn’t want to be PUBLIC as to their wild non-technical claims that Lemmy PostgreSQL and lacking of caching - performance didn’t have fundamental flaws in it.
the site_aggregates UPDATE 1500 rows problem in the code is just one example of the crashes going on June 25 that was not getting attention. GitHub Issue 2910 was being ignored on June 25… and not addressed at all - a know site crashing problem.
Getting private messages. from Lemmy users who say “go back to spez”. The Lemmy Community can call out the leadership of Reddit by name, they drone on and on about hate being a core value in hteir life, and how hating on spez is so important.
But when you have valid documented criticisms of the Lemmy leadership not reporting their server crashes and sharing crash logs, they private message you - because saying things out loud in public isn’t how Lemmy is run. “High Performance” is on the front-page of Github for the project, and if you have something to say about that, you are the one who needs to be socially “corrected”.
Here is what I’m getting in private messages because I keep pointing out that the major sites are not opening bugs on Github and sharing the crash logs:
I don’t want features, I think the “High Performance” claim is a big problem of project communications and expectations.
I think the site is crashing constantly, every day, for 32 days I’m using it for 6 hours a day. Nobody is reporting the crashes, and nobody seems to even notice them who is running the project. Where are the announcements that data is being lost?
Caching and turning off features/code, such as the “activity” database table, are obvious ways to deal with a crashing server. Yet they obviously aren’t being implemented. A caching layer between the API and the SQL database would provide immediate relief. This isn’t a “feature”, this is essential changes in a critical time period for the project.
Testing, I personally went around sharing information about testing, because the project isn’t getting enough testing… The person who private messages me seems to think that posting on Lemmy and testing Lemmy and identifying the problems doesn’t matter.
Server logs need to be shared. That’s really really really holding back the project. Caching needs to be added.
This message made it from Lemmy.ml to my server, that’s good
It also says a ton that they private messaged me back in June 25, 2023 before the Reddit June 30 API cutoff influx… as they didn’t want to be PUBLIC as to their wild non-technical claims that Lemmy PostgreSQL and lacking of caching - performance didn’t have fundamental flaws in it.
the site_aggregates UPDATE 1500 rows problem in the code is just one example of the crashes going on June 25 that was not getting attention. GitHub Issue 2910 was being ignored on June 25… and not addressed at all - a know site crashing problem.