I’ve got a 2007 laptop that was shitty even for its time, and it does the job perfectly as a home server with Debian and a few good open source services I want to host
- 5 Posts
- 7 Comments
iByteABit@lemmy.mlto
Programmer Humor@lemmy.ml•Looking for vibe coder with vibe management skills
0·7 days agoKnowing how to code is now “syntax heavy”
god I hate this world
iByteABit@lemmy.mlOPto
Open Source@lemmy.ml•What's your favorite FOSS Rest API client tool?
0·7 days agoIt’s foss but got purchased by Kong and started becoming a bit too much of a product for my liking, it has a fork called insomnium that keeps development where it used to be before but it’s no longer maintained sadly
iByteABit@lemmy.mlOPto
Programmer Humor@lemmy.ml•AI slop repository with 8k stars on Github that doesn't even compile
0·19 days ago“Example: fall detection” Sure buddy, that’s what this was intended for
iByteABit@lemmy.mlto
Open Source@lemmy.ml•This is really serious, something this essetial can't be AI Vulnerable, save OSS
0·21 days agoA 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.
iByteABit@lemmy.mlto
Open Source@lemmy.ml•This is really serious, something this essetial can't be AI Vulnerable, save OSS
0·21 days agoI’m no fan of AI generally, but “AI Vulnerable” as a term just doesn’t make much sense to me. Code reviewing should be filtering out bad code whether it originates from an AI or a human.
PR spamming with the usage of AI is another problem which is very serious and harmful for OSS, but that’s not due to some unique danger that only AI code has and human contributors don’t.



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