• 6 Posts
  • 97 Comments
Joined 4 months ago
cake
Cake day: November 8th, 2025

help-circle

  • Then why did they lock the fucking thread as controversial if it was such an innocent change?

    It’s paving the wave to implement a Californian law that can very easily end up meaning ID verification for everything.

    They could just not have done this at zero cost but decide to go to multiple projects, at this specific time which obviously isn’t coincidental, and actively work to start implementing this on Linux. I guess “Contributed to systemd” on their CV was more valuable than resisting the USA taking control of the whole internet and ending all sense of privacy.


  • Wow that’s an insane level of bootlicking, it was completely free for them to do absolutely nothing about this nonsense law and give the middle finger if asked by the US

    I didn’t care before but it turns out the systemd haters were on to something for a long time, fuck these owners for even considering this and even locking the PR to avoid valid criticism, I hope all the contributors create a fork, jump ship and never let the previous owners commit a single line of code to it




















  • A present day AI makes an educated guess which existing source code snippets best match the request, does some testing, and submits code that it judges is most likely to pass code review.

    That’s still on the human that opened the PR without doing the slightest effort of testing the AI changes though.

    I agree there should be a lot of caution overall, I just think that the problem is a bit mischaracterized. The problem is the newfound ability to spam PRs that look legit but are actually crap, but the root here is humans doing this for Github rep or whatever, not AI inherently making codebases vulnerable. There need to be ways to detect such users that repeatedly do zero effort contributions like that and ban them.