mccRE: https://mastodon.scot/@kim_harding/116108957641748718
I want this but as a Linux distribution. I don't think I'm asking for much here. I am just asking for the "open source community" to be to the left of Goldman Sachs
My understanding is that Bitwarden and KeePassXC, the two open source password managers, are *both* using random code generators at this point, which is terrifying as those are the exact tools where a small error could have the largest negative impact, and also tools that once you've committed to using it you can't quickly back out if they enter a code quality decline
🏳️🌈🎃🇧🇷Luana🇧🇷🎃🏳️🌈@mcc oh yikes wtf please not bitwarden
Nina Kalinina@luana @mcc nothing says "super safe password manager" more than "161 files changed, 776 lines added, 541 line removed, some files are hidden from PR by default, authored by Claude Sonnet, merged with some tests failing"
Gabriel Pires@nina_kali_nina @luana @mcc The file being “hidden” is an issue with Github’s UI, the source code is not actually “hidden” from people who want to read it. Also, who cares if master breaks? Do you pull Bitwarden from master and compile it or do you download pre-built releases? A lot of anti-AI sentiment today seems to have zero thought put behind it.
@gsprs I'm well aware that the "hidden" code can be read if one cares about it. But the UX is bad, and large changes go unnoticed for someone who only skims over the PR. Which is more or less the only option for a PR that changes 161 file. These PRs are generally very difficult to review for humans.
> Also, who cares if master breaks?
Every reliability engineer worth their salt.
@nina_kali_nina > These PRs are generally very difficult to review for humans.
Is it difficult for humans using AI? I’ve heard it’s easier that way 😁
The anti-AI crowd is more than welcome to put in the work and fork the projects they criticize for using LLMs and maintain their own repo with 100% organic homegrown code, I wouldn’t hold my breath waiting for that though, being outraged over other people’s generous contributions is far more attractive.
LisPi@nina_kali_nina @gsprs Honestly I'd be inclined to just reject the PR if it's not very pertinent. Even then I might procrastinate on having the energy to actually review that.
I refuse to just merge in code I didn't actually review.
I refuse to just merge in code I didn't actually review.