This is a test comment to see how front-end gets notification.

ok, you are a mod now

Made you a mod!

Made you a mod!

This is a test comment originating from bulletintree

You KNOW WHY nobody does testing and finds these problems? Because it's hard work, nobody wants to do it.

And when you actually go around and TEST federation by hitting Beehaw, Lemmy.world, Lemmy.ml, your own server, and a half dozen of the small ones - it takes TIME and EFFORT.

They they ignore you as to how important it is to get the crash logs off the big servers. Actual testing that you spent 80+ hours on in 14 days they don't seem to think is of any value.

The project SHOWS that they don't think TESTING and Quality Assurance is of much value. That's been the attitude I keep seeing, that testing isn't a priority! That sharing crash logs of the Rust code isn't important!

Test message #2 in this comment section of this posting

Test message #1

This message made it from Lemmy.ml to my server, that's good

Today I witnessed that Beehaw, Lemmy.world, most of all Lemmy.ml are crashing . Just 10 minutes of reading routine postings and comments

It has been this way every day since I started reading and before I even created an account. Reddit users kept recommending Lemmy - so I did eventually create an account on June 2. https://lemmy.ml/u/RoundSparrow

No issues from any of these major servers has been opened on GitHub saying "my server is crashing constantly", I'm baffled how all month this crashing has been going on in the application - and they are acting as if business as usual.

There were almost no messages in the databases of Lemmy.ml when I first started reading it 32 days ago. There were numerous communities that had been abandoned for years.

Reported crashes on meta Lemmy.ml today, ignored like when I reported nginx 500 errors. Server operator doesn't open issues on GirHub and seems to not care about the reports I am reading throughout the community that the site is crashing constantly.

There is a tone of intellectual dishonest that I keep sensing within the project. The "High Performance" claim on the front of GitHub really lures people into the project "it can run on a Raspberry Pi" claim.

The idea that a caching layer of the repeat SELECT statements keeps getting ignored. I shared this link on Lemmy and GIthub recently, and not one response: https://www.reddit.com/r/rust/comments/zvt1mu/comment/j1uxjs5/?utm_source=share&utm_medium=web2x&context=3

It's a "reality distortion field" gong on. Well meaning people keep defending the management of the Lemmy.ml server - but the lack of opening a bug about the server crashes is harming the entire project. It is the core hub of federation for key communities, and now there is more chaos than ever because everyone flocked to new servers - only adding to the crashes of federation sharing.

10 second timeout on HTTP default.

The home page of GitHub should really be changed away from "High Performance" into 'we are in urgent need of fixing stability in http and database, we need scaling help with Rust and a caching layer".

I've spent now well over 80 hours the past 14 days testing the big Lemmy servers and in total disbelief that they aren't opening GitHub issues and sharing their Rust crash logs. It really seems sharing the logs is something they won't touch with a 10 foot pole, for a server application.