What's this? A bunker full of billionaires unbothered by bees? My dump truck full of bees ought to put a stop to that!
Like how leaded gasoline, CFCs, and ActiveX cannot be uninvented and are still found everywhere? Regulation absolutely can restrict a technically society doesn't want around, as can a move to alternative solutions.
And that doesn't mean it disappears entirely. Avgas is still leaded and CFCs are still being used in specific contexts like Teflon manufacturing. But they're no longer everywhere. ActiveX is pretty much dead, though.
The amount of "what does this regex do?" - "dunno, ChatGPT wrote that for me" I see in code reviews these days doesn't inspire much confidence in either B or C. I don't have direct observational evidence for or against A but at least there's maybe a claim for people who restrict its use to very specific use cases.
Mind you, the people who are pushing to replace everything with LLMs are not the people who spend half a billion bucks on tokens in a month. They're the ones who charge half a billion bucks and the ones who charge them for the hardware. As far as they are concerned, that half a billion dollar bill is a rousing success they'd like to see repeated as often as possible.
Okay, and then there's the useful idiots who vibecode a 50 kLOC basic CRUD application with broken auth in two days and conclude that LLMs can craft arbitrarily complex applications instantly at near-zero cost. And then proceed to shill the stuff every chance they get because these days the internet is all about hyping yourself up and they can pretend that their finely-honed 1337 prompt crafting skillz will make them as god-kings among peasants when vibecoding will inevitably subsume all other forms of development, nay, all forms of creative work entirely!
While remaining cheap, of course, because nobody has ever offered a service for cheap and then made it more expensive.
Yes, infrasound is a fairly well understood phenomenon. Loud noise at frequencies below 10 Hz isn't commonly picked up by recording equipment but can induce things like anxiety, nausea, and sleep problems. While recently wind power plants have sometimes been accused of generating it, it's also been caused by industrial fans and even resonance in a building's ductwork.
It wouldn't surprise me if a data center's AC caused enough noise at frequencies not normally monitored to become an issue.
So Kaspersky found out that MD5 passwords are unsafe. That's literally 20 year old news. Actually, Kaspersky found out that brute-forcing MD5 on consumer-grade hardware has become slightly faster than two years ago, which makes me wonder if Captain Obvious's secret identity is that of a Kaspersky cybersecurity expert.
El Reg concludes from this that we should ditch passwords, which they back up with the opinion of a second expert. This expert immediately tells them they're wrong, that passwords are perfectly fine if used with MFA, and that a lack of public knowledge about basic cybersecurity is the real issue. They somehow treat this as him agreeing with them.
Actual technological alternatives to traditional password use (such as passkeys or password managers with per-site passwords) are mentioned only as an aside or not at all. It never occurred to El Reg or Kaspersky to mention that MD5 has been considered obsolete since the days of Internet Explorer 7 and that more secure hashes like bcrypt have been around since the late 90s. For that matter, the Kaspersky source talks about rainbow tables without using the word "salt" even once.
Finally they conclude with a call to action to "improve that user security stack", arguing that passwords are inherently unsafe due to their "complex requirements and hashed storage". That's so deep into la-la land that I'm not even sure what it is they're trying to say or who they're even talking to.
That's an amazingly badly written article.
What impresses me the most is that the Kaspersky article they're talking about is just as asinine as El Reg's confused stammering. The most sense I can make out of it is that they're making a bad faith argument ("we can brute-force MD5'd passwords with a 5090 so you should use MFA") because they're trying to get nontechnical people to do the right thing and hope they can scare them into compliance if they bullshit hard enough.
Edit: I just noticed how often Kaspersky's article refers to the own password manager they sell. So their bad faith argument is really just in service of an ad that happens to contain some decent security advice.
Best I can do is mandatory Lumen and Nanite. You can get almost-stable 60 fps on a 5090 with DLSS Performance and 3x frame gen, which should be optimized enough for anyone.
My game will sell for 80 bucks, 150 if you want the edition with all the preorder-exclusive content.
A shorthand for 000a:0000:0000:0000:0000:0000:0000:000s. It's part of the alphabet v4 spec.
I remember the early 2000s when basically 90% of all Americans were absolutely certain that jihadists were going to attack their local supermarket any minute now because Power Cable, Nebraska was such a strategic target.
Heck, there was a bomb scare because of an advertisement campaign for Aqua Teen Hunger Force that involved placing PCBs with LEDs on them that would display characters from the show. Because surely Al Quaeda would put conspicuous LED displays on their bombs.
News media want people to panic so they keep tuning in. Panicked people tend to come up with remarkably stupid scenarios like "Al Quaeda have unlimited resources and can show up anywhere to shoot people at random" or "Hamas want to take Dorcester as a strategic location to strike at Israel from".
He should go on vacation with the CEO of Nestlé and publicly endorse single-use plastics.
"Well, excuuuuuse me, princess!"
gets shot twice, just to make sure
The Cachy kernel is in the AUR if you're brave enough.
I gotta say that I agree with many of Cachy's choices. I use Garuda, which makes many of the same choices and uses them effectively. For example, BTRFS is a good default choice if you also have default Snapper with pre- and post- update snapshots.