It isn’t just the constant database crashes in Lemmy, GitHub issue 2910…

https://github.com/LemmyNet/lemmy/pull/3708

On July 24, sanitation of HTML was added to the code. But the testing was not called for and it broken titles of postings, link parameter ampersands, discussion of programming code in code blocks

It’s data… and now it’s very difficult to undo all the damaged data that has been put into the database for weeks now.

Lemmy is a Link aggregator, and it damages Links now… the ampersand parameter deliminator in URL links is now broken because of this code not being tested. Why wasn’t there a call for testing to something that was going to alter every new post and comment from both federation and Lemmy itself? how did such obvious things such as a ? parameter list in URL get overlooked… and then new bugfix release comes out after this was known as an issue - and still not fixed.

Database crashing that results in lost data from unsaved post and comments, failure to deliver Federation data without any way client or server operators are notified, and damaged data as fundamental as URL website links…

I’m all for code changes gong in fast, but the lack of actually testing things and spot-checking on Lemmy instead of just changing Rust code without really realizing that a link aggregator uses ampersand in URL links… and not asking people to help think of side-effects…

Development process could even ask just a couple sites with more attentive operators to try out the code for a few days and ask people to report any problems before advising all sites to upgrade and break their URL links.

  • RoundSparrow @ BTOPM
    link
    fedilink
    110 months ago

    Broken URL links because untested HTML sanitation… that then goes into a release and for weeks has been corrupting data.

    At the same time, another change went in with how deleted and removed comments are delivered to clients. And if a person deletes a comment, now all the replies below that comment - even from other people - are no longer shown.

    This is a fundamental data issue of the application! A change is made with the internal Rust code logic on how comments are deleted - and no client-side testing is done to make sure there are no side effects.

    If B and C reply to A, and A deletes their comment, they all 3 have their comments black-holed by Lemmy. But an admin logged in would not see the change. But the change was made in the Rust code… the developers did not test it as normal end-users of the website… and they do not seem to login on Beehaw or other sites just to check the health and use of the application. It’s like a business that never visits their customers and see what their engine is being used for. And it seems it has been that way for years…

    Data doesn’t matter… that’s the attitude. People’s comments just disappearing isn’t noticed.