They're clearly trying to hide the fact that the pilot was of a specific ethnic classification, one which is already well known for causing a very large percentage of road accidents with tractor trailers.

In other words, it's like saying someone violated copyright by making a MIDI version of a popular song.

No, they did not release audio.

A spectograph is not audio, it's an image of the timing, signal, frequency of a signal.

The fact that it could be reverse engineered into coherent audio is not consequential.

That's like saying that someone released public source code to a program when all they did was release the binary. Or, more accurately, released a use video of the software, which someone then reverse engineered.

Please sar remove the audio spectograph sar it's very important sar

There's another way to mitigate this, and it's ideologically difficult for a lot of Open Source people to accept... but you'll have to diverge from the tried and true path. AI makes this much easier: instead of using $popular_thing_everyone_uses, you use something else - either COTS or roll-your-own. Yes, it might be bugs, and yes, they might be security bugs, but unless they're painfully obvious issues where you didn't do your due diligence, it's going to be a more obscure target which will require more targeted attacks.

No, this doesn't solve anything and it's 100% "security through obscurity". Perhaps I'm just missing something, but it seems like sound practice.

So, basically what you could do in W95.

What you describe is basically cron + freebsd rc or classic linux init.d

Systemd over engineered everything to better support corner cases, which ultimately doesn't work as well at the core functionality and causes systemic stability and security problems.

You say that, but then ignore the funding source and board of directors for the orgs that Lennart worked for... sure. Totally just a coincidence.

In other words, they've made largely superficial changes (except 9x -> NT) quite consistently which haven't added much in terms of value.

Because Lennart Poettering is basically the Linus Torvalds of fucking up Linux for Microsoft: systemd, avahi, pulseaudio, and associated shitware bloat which have made linux less stable, less secure, and increasingly difficult to diagnose or integrate.

He's always been a proponent of doing things on Linux the Microsoft way, seemingly as an agent of chaos.

Yeah, true - most of those systems are trash, bugzilla specifically.

They really should be built more like a CRM.

MBAs are "highly polished turds" because we've lost the ability (legally and culturally) to assess people on merit. You end up with a poor surrogate, which has become gameified to produce people who make the metric the measurement of work instead of basing metrics on the value of the outcome.

Where have you been? You couldn't be more wrong.

This entire culture has been bent around the idea of quarterly profits for decades. "Stocks are up!" Short term gain at the cost of long term employees and innovation. Ship faster!

While, yes, the trend to seek short term profits has slowed and even in some small ways reversed, we are a good number of years from being focused on incremental innovation and experience, again.

While the entire world moved to bugtrackers, Linux seems to have stuck with the venerable yet antiquated mailing list for tracking its bugs.

Except, it's worse than that. It's not even the exclusive source, they also use bugzilla - one preferentially over the other, depending on preference of the maintainers (and presumably, the submitters).

That's not scalable. While it's nice for a small team, perhaps, to continue using email, particularly since it's been the convention for a long many years, it's clearly not working anymore.

The purpose of the system is what the system does. Email has largely fallen out of utility due to everything/everybody trying to use it for... everything.

The problem here isn't the AI generated content, it's the mechanism used for reporting bugs. They (the kernel maintainers) need to use a proper modern bug reporting and tracking system, and probably one at this point which runs automatic regression/integration tests + LLM/SLM evaluation (classification and categorization) of submitted materials. I'd wager a great number of the bugs found are indeed real, and now they're just noise.

This is a relatively dire situation, given the events of the past week: significant, frequent exploits require a more attentive approach to this than free form email can provide.

Calculations based on average price of fuel + average household fuel use - public data. Those figures matched my experience of having an 1800sqft house with an oil burner heater in upstate NY some years ago when heating oil was about half as much as it is now (actually, a bit lower, but then my furnace was old - not that you can really fudge much efficiency out of these things, they're pretty efficient).