Any digital noise or random signal would work to jam the navigation system, but Night Watch wanted to use the song because they think it's funny.
So they literally did it for the lulz.
Yet another reason to throw Windows out the... window. I have a Dell XPS 17" that runs fine under the current Linux Mint. It didn't a few years ago when it was new (sound card wasn't detected by older kernels), but it's quite nice now. It's even got two NVME slots, so I just added a second one for Linux.
The only issues I've had so far is when I reboot from Linux it wants to start Windows (probably a BIOS problem, fixed by having Windows boot manager put up a screen) and recently the 80% battery charge limit that I set in BIOS was ignored and it charged to 100% (still watching the situation).
I'm pretty sure that Gemstone III was on GEnie. I had been playing since the last month of GS2 beta... those GEIS computers were not very timeshare friendly, and the game would sometimes freeze up user commands while the monsters clicked away on their 10 second timers. As I recall, GS3 was set up on a Sun workstation to avoid such problems, and I guess it's possible that they could have added another gateway from Compuserve.
Thanks to how they did turn timing, I am to this day quite good at counting down seconds on my microwave while doing something else, usually to better than +/- 5 seconds per minute.
And you might be wondering what happened to Gemstone I. As I recall, it was the original demo which ran on an Amiga.
The state laws could be unconstitutional due to interstate commerce. However, the Feds should regulate it thoroughly. Enviromental, National Security, etc
There should be a national level effort like the Manhattan project. Companies should be working together under goverment oversight, and working toward a common goal. Maybe that will keep a AI apocalyse away for a bit. maybe protect us from it?
I know my opinion is in the minority. The future is starting to scare more than usual.
At this stage, we're all learning. (not that we ever stop), Vibe coding can be great for learning if the dev is taking time to understand what's being done. But I fear too many are taking the easy path and just writing a prompt and shipping. That's not safe for any environment, let alone production. Some time in the future it may be better. We'll have the proper guide rails for AI, the proper testing paths, and overall reviews. Right now isn't that time. If you want stable, efficient code, which you definitely do for Production and kernel maintenance, AI isn't ready. It's not any more ready than self-driving cars. Can they do it? Sure, would you trust them in every situation? probably not. That "Probably, not" is what gets you killed. Or Panics the kernel, or crashes the DB....etc.
Linus is a smart guy, I might not agree with everything he implements, but for the Linux kernel, I can say I never felt like he went in the wrong direction.
I'm sure this discussion will continue. It's not a once-and-done. But as newer and better coding systems come online, they'll need to be tested and verified, and eventually we may get something that passes the test. It's already miles ahead of where we were only 10 years ago. I can't predict how we'll be next year.
...officials from the Centers for Disease Control and Prevention confirmed to state health departments that the ongoing measles outbreak at the border of Arizona and Utah is a continuation of the explosive outbreak in West Texas...
Why are there still competent people at CDC who are able to do this? Anyone who knows anything about anything, was supposed to have been fired months ago and replaced by incompetent flunkies.
Commander Putin's orders have been very clear about completely disarming all American capability, whether it's in our health systems, military, or infrastructure. Who is the pro-American traitor in our midst, disobeying orders to destroy the USA?
If we're going to disobey Putin's orders, then won't he kill or embarrass our president? That must not be allowed to happen!!
$230
My jaw drops, but then I split. Half of me remains smugly looking down on fuckwits, but the other half hears that Samuel Adams' Utopia, which costs about the same, is supposedly showing up in CostCos, and while I can't justify getting a bottle
No.
No, it would still be stupid to do.
Google, Microsoft, Apple, Facebook, Amazon, or another one of the big software development companies could easily fork ffmpeg itself, fix the open CVEs, provide their own (likely incompatible) features, and become the new standard - leaving the original developers out in the cold. Google did this with Blink (forked from WebKit, which itself was forked from KHTML). They took a fork of a KDE backed project, put it into what is now the #1 browser in the world, allowed Microsoft, Opera, and others to then use it in their own browsers — and now Google owns the entire narrative and development direction for the engine (in parallel to, and controlled to a lesser extent by Apple which maintains WebKit). The original KHTML developers really couldn’t keep up, and stopped maintaining KHTML back in 2016 (with full deprecation in 2023).
That is the risk for the original developers here. You’re right in that there isn’t really anything out there that can do what ffmpeg does — but if the developers don’t keep up on CVEs then organizations are going to look for new maintainers — and a year or two from now everyone will be using the Google/Microsoft/Apple/Facebook renamed version of ffmpeg instead.
That’s the shitty truth of how these things work. We’ve seen these same actors do it before.
Yaz
Look — I’m a developer. I get it. I’m personally all for having organizations do more to support the OSS they rely on. But the people in the C-suite are more worried about organizational reputation and losing money to lawsuits. If a piece of software they rely on has a known critical CVE that allows for remote code execution and someone breaks in and steals customer data — that software either needs to be fixed, or it needs to be scrapped. Those are the choices. Our customers in the EU are allowed to request SBOMs of everything we use and pass it through their own security validation software — and if they find sev critical CVEs in software we’re using there is going to be hell to pay. And the people in the C-suite can’t abide that level of risk.
Most software development companies (outside some of the biggest ones) don’t really have the kind of expertise in house to supply patches to something as complex as ffmpeg. But a company like Google has the staff with sufficient experience in this area that they could fork the project, fix the issues, and redistribute it as their own solution to the problem — and now Google is driving ffmpeg development. Organizations that need a security-guaranteed version will simply switch to Google’s version, which will likely slowly become incompatible with the original. They’ve done it before — Chrome was Google’s fork of WebKit, huge swaths of users flocked to Chrome, and now Google has over the years made enough changes that their patches often aren’t compatible with WebKit (and, of course, WebKit itself did similar when they forked KHTML).
Now forking like this is great for the community, but it can be tough on individual developers who see their work co-opted and then sidelined by massive corporations. And that’s really why the ffmpeg developers need to be very careful about ignoring CVEs like this. They do so at their own peril, as anyone can fork their code, fix the issues, and slowly make it incompatible with the original. And a big enough organization can ensure they’re fork becomes the new standard, leaving the original developers out in the cold.
Yaz
Suck/not-suck aside, would you at least agree that it's as good as The Mandalorian?
Eyeball monster == Baby Yoda. So. Fucking. Cute.
Innovation is hard to schedule. -- Dan Fylstra