Of course it’s slop
comments
The devs haven't said anything about this one AFAIK, though we can at least look at last year's AI-found LPEs.
Secureblue mitigated Copy Fail and blocked the xfrm-ESP exploit path for Dirty Frag. You can read more about it here.
Kicksecure did neither, as SUID and unprivileged user namespaces aren't disabled by default. You also can't selectively enable user namespaces after disabling it, which worsens security for web browsers and breaks some stuff.
In the age of radar detectors, I'm not sure any speed limit should be obeyed.
"or just describe it to your agent"
*shudder*
"May God have mercy on our souls."
-cprussin and/or claude code, 2026
i mean it's a one time thing to learn, like with sourceforge, moddb, apt, etc etc
Courts are slow but they will catch up eventually
I don't think it's difficult to know who triggered this when the announcement for the latest Omarchy announced support for Apple hardware. Thanks, DHH
All these comments about git, but OP is presumably asking about this: https://overthewire.org/wargames/bandit/
this just seems unnecessary, just hurts BSD (os). LLMs aren't stopped by licensing.
The original comment said "Sometimes those clankers can hallucinate useful ideas".. do you really think that they meant to say that the people are the ones hallucinating, not the machines?
Technically there was already the one used for ChromeOS
They asked about how to stop losing ssds in an environment with passive cooling and the answer is a heatsink.
Their pc has vents and is designed to rely on passive cooling. Perhaps it will last a long time, perhaps not.
And how's that going considering 3 ssd failures and current idle temp of 67C versus the expected 40's? You're clearly not so dumb that you don't know that a heatspreader will have its limits when you're up against dead air so this is plainly what's called being wilfully obtuse. And OP is the one who will suffer for it.
rushing into the operating theater to disrupt an in progress remediation of gunshot trauma to inform the staff that the persons heart disease is a big deal
Funny, I'd liken your advice to putting a bandaid on a gunshot wound. But keep telling yourself you're a trauma surgeon and not the janitor in a lab coat that OP was unfortunate enough to stumble into. Learn to admit when you're wrong.
Hey look, the thing many of us have been complaining about when it comes to the MIT license has been shown to be true, imagine that
They did not even launder it /s
In the age of LLM code laundering, I'm not sure any license will protect a project, open source or not
never heard of ts
OT, it completely checks out that danemadsen's github history is filled with "AI" development.
Why are you posting the entire article? It's generally considered kind of an asshole move towards the people that actually wrote the article.
I've been playing Linux for a while, and I'm pretty sure it's spelled "guthib".
OverTheWire bandit is really fun. I was able to get up to the level with the encryption stuff. The encryption stuff confused the hell out of me.
Be sure to use the manuals and the wiki entries about the relevant commands listed on the website. You need to use some comprehensive reading and crack your brain. It is quite literally a puzzle. Not much I can say to you to help you without spoiling the puzzle.
Sounds manageable but I will only know the next time I end up on GitHub. Thank you for the help though, it might just be enough to get me through.
I have not worked it out
The secret is you have to scroll all the way to the bottom and click the tiny link that says "releases". Or sometimes click the ellipses (...) at the top of the page and find it there. From there you scroll to the bottom of the latest release and expand the section that says "assets". Then you typically need to understand package formats and choose the correct one for your device.
I'm personally very happy with my proxmox based server(s). I'm using community scripts for many of the setups of actual services. Over all, it's low maintenance and if I'm having issues it isn't with the host system. Not once did a system update cause a failed boot after.
That being said, NASty sounds rather promising. I doubt I'll switch over, but it might at least make for a fun experiment. And being nix based is rather nice for reproducibility.
I have not worked it out, too many times a search ended at GitHub; it’s like the great filter for me, I cannot for the life of me get past it.
Similar/ related Linux instructions are often the same. Just do the gobbiligoo and write magicmumbojumbo in the wolooolooo. It is often just presumed that you know all terms, and that you automatically skip the first 5 steps which are soooo obvious.