@aris hope the gpu behaves now. That 12vhpwr socket can be a bit troublesome

@aris any luck?

@aris I have had “dirty” RAM cause a few hard crashes. System works fine until you need to use the actual capacity in that stick and thats when issues occur(system freeze or a sudden shut down). Dirty RAM in general can just acts funky. Sometimes it prevents booting up entirely other times it can take hours to actually cause a problem.

@aris try reseating the RAM and GPU if you can. RAM first preferably and while you have the RAM out, try cleaning it with a soft dry cloth and blowing on the contact pins to ensure they are clean. Might just be some very slight dust in the contact pins of one of the RAM sticks (if you have multiple)

@dalias what about projects where security patches and bugfixes being back ported are also slop

@nixCraft much as i hate AI, i have to admit a very, very vast majority of people are tripping over themselves trying to integrate it as deeply into their lives as possible. Such people will continue to attempt to bombard open source software with slop PR’s regardless of whether the project accepts those or not. This method of requiring human review and clear attribution for AI generated content is the only way to make sure people clearly mention when they used AI. If the kernel outright rejects AI slop, the AI-bros will just stop attributing generated slop. So maintainers won’t know if submitted code is slop or not without thorough manual review and maybe not even then.

@FirewallDragons This is insane. Now every open source software developer/organisation is at risk of microslop suddenly closing their accounts. Let’s hope this gets resolved without any nefarious requirements being added by microslop for reverting these changes