Schools might call 'em on it. "Okay, we'll use Duck Duck Go, or Startpage, or Dogpile, or Bing, or..."

Then I see no reason to give human-generated earnings to a company that does not value human programmers and artists.

Before one buys any hardware, or comes to rely on any software by Google, it's a good idea to visit Google Graveyard and take a few minutes to ponder over how long it will be before Google abandons the technology it's trying to sell you, leaving you with yet another piece of e-waste.

From the article: "Supermarket cold aisles are typically run by control panels that manage an entire store's fridges and freezers and can be accessed over the internet, which lets maintenance companies adjust them from anywhere."

Well, there's your problem. Stop doing stupid things like that.

Decart's acronym for DOS is "Decart Optimization Stack".

Those of us old enough to remember will immediately think "Disk Operating System" though.

... and dig the base out of the ground, and carefully transport base, pole, and cameras for each installation into room without windows that can be locked. Most importantly, do not damage Flock's property. Leave the cameras operational and running.

Then, send Flock a letter letting them know their property is intact and undamaged, but is now safely stored away to prevent vandalism against their equipment. Further let them know that they are welcome to come collect their property, but they are not welcome to re-install the cameras anywhere on Campus due to safety issues.

Unless there's some sort of penalty against removing the cameras in the contract they signed with Flock? (Probably is, come to think of it...)

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.