Sometimes things have had their run, and their death is ugly and uncomfortable. Remember the good times, try to forget the bad, but above all, let them rest in peace.

...so more digging and this appears to be entirely the FSF demanding that all four JavaScript bundles on BlueSky include this wrapping the published CDN bundles: // @license magnet:?xt=urn:btih:d3d9a9a6595521f9666a5e94cc830dab83b65699&dn=expat.txt ... // @license-end

Because apparently they don't recognize the existing @license NAME structure in separate .LICENSE.txt files that's been de-facto standard for a decade, and also don't recognize 'meta' license names like React being MIT (what FSF calls Expat) but since that lets you specify who to attribute copyright they name it 'React' license instead.

Yeah I read all the links across the FSF and this really is a core fundamental problem with many their issues that makes them feel more like random crusades:

They don't actually explain what the problem is, just lots of platitudes and links to 'approved' libraries and resources.

The best I can understand is they're complaining that BlueSky doesn't expose licenses of every JavaScript fragment in their bundle in the format their custom browser plugin demands?

https://web-cdn.bsky.app/stati... for the main React bundle is all MIT. Remove the .LICENSE.txt to see the original .js file that points to that one.

The main social app's codebase is also MIT: https://github.com/bluesky-soc...

Without the FSF actually specifying what part they feel ISN'T MIT at this point it feels like a FUD-like crusade not an actual campaign to improve things or just demanding Yet Another Proprietary Standard File every website must include because some random organization started demanding it.

Compared to the cost of equivalent chromebooks the Neo makes a compelling value IMHO, and has a lot more cases and shells and such to protect them already than almost any model of Chromebook ever did so more likely to survive the school year.

Like I'm all in on x64 between the Windows and Linux computers sitting around me, but even I picked up a Neo instead of a chromebook after trying one, they're shockingly competent and nowhere near as locked down as a chromebook is.

The term is specifically targeting solar and large-scale battery (like a whole home or grid-scale) inverters:

https://www.fcc.gov/covered-li...

* Device has to be bi-directional DC<->AC.
* Device has to support wireless remote management.

The U.S. Department of Justice can now set up a cutout and try to buy that data as part of a criminal investigation and sting operation.

Here's hoping they do, and that they nail these bastards, as an example to the rest of them.

This isn't "breaking userspace" because they're removing support for that specific flavor of userspace the same way they would any other deprecated-and-removed architecture.

It's been supported for roughly a decade, with minimal uptake, and was a bodge-hack on the x86 configuration registers in the first place.

This is not about 32-bit support in the Linux kernel.

It's about a mutant hybrid mode forcing memory accesses to 32-bit but running the actual CPU in 64-bit mode otherwise so you get twice as many (and wider) registers but pointers take up half as much memory.

"The change as been reverted as of May 3, but not before 1.4 million commits were made. Unfortunately, those messages cannot be cleansed and are permanent."

Nonsense. It's just ones and zeros. They can be changed. Microsoft just doesn't want to.

$900 USD is just not worth it for me for console gaming. I've already got a PC that works, and games I like for it.

I'm just going into a holding pattern for buying any computing equipment unless I absolutely need to. I suspect I'm going to be in the majority on that.

I'll just continue to purchase games from GOG on sale. My "to be played" backlog is already crushingly large, I'm not at a loss for something to play.

Also, SONY? I still remember that rootkit you and BMG hit people with. Sucks when your customers have long memories, doesn't it?

It's the same start/stop system and engine as the Ram 1500 pickups have used since 2013 (and still use today in fact), so it's not a Jeep-specific thing in this case, just I've encountered it twice because of the prevalence of Jeeps off-roading and they don't get the 'commercial vehicle' exception to being able to make the ESS optional at purchase time.

I've been on multiple off-road trail drives where at least one newer Jeep Wrangler had it's start/stop system start fail in some way and couldn't keep running because of how Chrysler implemented the system on those engines.

One had to be limped home with an escort 15 minutes at a time, the engine would just stop while in gear and ignore the gas pedal until it was fully switched off and restarted, code reader kept saying errors in the start/stop system, etc.

The other one just didn't risk it, called a tow truck and opted to wait. Code reader also said start/stop system fault codes when we looked them up. Different Jeep from the previous one, BTW!

Start/stop is basically built in for hybrids, but for non-hybrids they're often just a boat-anchor mis-feature along with cylinder de-activation that mostly only exists to game EPA numbers.

A well engineered one that for example has an electric power steering pump and brake master cylinder that doesn't rely on the engine running to maintain pressure? Can be good.

But that still needs a MUCH stronger starter to survive even a single heavy-traffic commute where it will cycle 20+ times in an hour and only a few minutes in between to recharge, let alone years of that, and stronger/larger alternator and battery to handle the much more frequent rapid charge/discharge cycles, etc.

And at that point you're most of the way to a mild hybrid, so the good ones just get turned into a true hybrid model at that point.

So as a Prius owner? Good riddance to this, IMHO. It never really fits well on non-hybrids because so many other things are tied to the engine running and moving those off is most of making a vehicle a hybrid already.

Whatever court hears Mumbauer's wrongful dismissal case will likely look at his actions post-firing and decide that he doesn't have "clean hands" in this matter. That will reduce the amount of damages the court is willing to award, or potentially end up with the decision going against Mumbauer completely, with him now being potentially on the hook for the company's legal fees.

If you have a legal dispute like this, keep your hands legally clean, even if it pains you to do so.

For those who need a refresher as to how the failure of the Fukushima reactors, see this video:

Understanding the accident of Fukushima Daiichi (from 2012)
https://youtu.be/YBNFvZ6Vr2U

Total time: 13:01. The key bit is at 4:49: "The waves went over the sea wall flooding the lower parts of buildings, and disabled the emergency diesel generators."

Had those generators and fuel tanks been higher up in the structure, things probably would have been fine, but with the reactors in control-rod shutdown and needing to dissipate the residual heat in the reaction chambers, the secondary cooling systems powered by those emergency diesel generators were absolutely crucial.