Ok, so let's look at recent changes that they have deployed.... https://github.com/LemmyNet/lemmy/issues/3886

One of which makes entire tree of comments disappear. Do you see developers fretting over this and fixing it? Or do you see them ignoring the May 27 PostgreSQL JOIN problem.

How did such a bug go out? Do you see Lemmy developers actually using Lemmy to test things and notice these crashes and problems? Do you look at their posting and comment history? Do they actually go login over at Beehaw and Lemmy.world and see just how terrible the code performance is?

If it isn't hazing, what is it?

It's as if they build a product only for other people to use... and they don't notice any of the constant crashes, incredibly slow performance etc - and they act like nobody in the computer industry ever heard of Memcache or Redis to solve performance problems. If it isn't extreme hazing going on, then what is it?

may I voice my opinion on the exchange? This is coming from a place of trying to help, since I really do appreciate all the work you’ve put in and are putting in, and the fediverse can really use your talents, so I hope I don’t offend you.

Can you explain to me why it isn't social hazing?

it didn’t appear that you were being ignored/hazed

Do you know how to read a SQL statement? I just can't grasp how it isn't social hazing. I've been reading SQL statements for decades, this is obviously a problematic one.

Can you offer alternate explanations of how 3 people could think that SQL statement isn't ... poor performing and gong to cause problems? And how an SQL statement without a WHERE clause took them months to discover and fix?

Extreme hazing is my best answer. I just can't accept that the SQL statements don't speak for themselves along with the server crashes. 57K users for 1300 servers is very... taking several seconds to load 10 posts....

Look at the date... May... this has been going on since May. If it isn't social hazing ... what is it? I keep asking myself that.

dismissing client-side techniques as nonsense without seeming to understand why they were being discussed in the first place.

I'm the one who started a post about a server-side solution that entirely is based on Reddit's code for a server-side solution. YOU are the one coming along with this wild idea that a server change isn't needed at all. yet, you have not demonstrated this wild claim you made!

I’m not interested in any multireddit feature that reduces sub privacy. I’d consider it a net loss for lemmy.

It does NOT require it. I will repeat it: IT IS NOT REQUIRED! It is a sub-feature that facilities better openness that I am suggesting be added as part of the core feature I'm developing.

On Reddit, multi-reddits personal in nature.

10 years ago Reddit announced it as entirely not being personal! That sharing them was the whole point. I again question if you even understand what multi-reddit is!

rows=1675 was the actual number on Saturday in July 2023.

rows=1675 from lemmy.ca here: https://github.com/LemmyNet/lemmy/issues/3165#issuecomment-1646673946

Latest, at the time of this comment: still over 4 SECONDS

yep, another big outage.

a lot of db tuning was being avoided

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".

I could list 50 reasons I could think of. Many of which would be even more offensive. I didn't sit patiently by watching June 4 issue 2910 go ignored because I was trying to over-react. In fact, I couldn't believe what I was seeing as they upgraded hardware June 13 and continued to ignore the June 4 issue on Github. Even further when June 30 deadline for Reddit API came.

I have been very wrong in how I dealt with it this past 10 days, as I did not come to understand how much the community has come to enjoy the environment of Lemmy. Talking to you has enlightened now just how socially driven the whole platform is and that any training and experiences I have running mission-critical apps with PostgreSQL and DB2 on production servers do not apply here and I should have realized just how wrong my social interpretation of the situation has become.

It's like watching the recent Nolan film release of Oppenheimer on IMAX. The massive size of the platters and how projectors have run into problems on opening night / first few days of showings. It's about the style and cool factors, just because Lemmy uses PostgreSQL I considered reliability to be important, but now I clearly see I socially failed to understand how much the community here has come to adore Lemmy history and progression.

Rock Stars being criticized about their style and use of the technology was a huge mistake on my part. It's all about putting on entertainment people like and the fans of the project are loyal to how it is done. I have been far too slow to recognize the "cool factor" of the Rock Star cultivation happening in front of me. I'm worried about the tire engine maintenance costs on an exotic sports car that draws huge crowds. Sorry I did not grasp that the crowds were so enamored and how that drives the project choices.

Heavy drinking, first time since New Years, reset my brain and I now re-interpret everything I learned about Lemmy history in a new light.

Matrix is a better discussion platform than Lemmy,

It was not crashing every 10 minutes of every day due to SQL TRIGGER code that the developers ignored.

Why don’t you go create a PR instead?

It's amazing how you have fallen hook line and sinker into believing that the problem is difficult to solve. It's the agenda that is the problem.

They have people like you who will not read actual code to see that they only care about the fact that "Rust is cool programming language" and crashing code doesn't get any priority.

They even started a new front-end Rust application this month, because they don't care to bother with the core of the site, PostgreSQL doing INSERT and SELECT statements to load comments.

And I would like to see a federation-wide policy that all bots must be clearly identified as bots (an attribute on their account). And features in the site code to block all bots as a user preference.

The interesting thing about Snowden to me after 10 years is how few times I see the public think about how low-level staff with hardware-level access can bypass all command and control decisions. He was a contractor who just wholesale scooped data off the servers. Nearly 10 years later... Jack Teixeira leaks documents because he has server access to documents outside his immediate need too.

I think a lot of organizations really don't see how vulnerable they are to deliberate attacks and theft - if the NSA can't protect their data 10 years ago, do you really think your mobile phone network provider or these VPN companies are not subject to internal staff selling off data, etc?