These consist of a standard cell with a protection board stuck on the end, and usually a smaller raised positive terminal. This adds 3-5mm to the length, and temporarily breaks the circuit in the event of over-voltage, under-voltage, or over-current/short. There's no written standard, but most brands are making pretty much the same thing, and they almost always interchange. Safety does not require it to be proprietary.

Here's an example from a flashlight manufacturer: https://www.skilhunt.com/product/bl-135-3500mah-18650-protec...

Here's an example from a third-party battery distributor: https://illumn.com/18650-keeppower-p1840c-4000mah-protected-...

The light in the link uses an absolutely tiny 0.5Wh battery, which strikes me as insufficient for cycling. I use a light with a 21700 cell (20Wh).

The company's philosophy on the issue seems to be rooted in the hacker ethos of not giving repetitive work to humans if a machine could do it. When a machine can't do it, Google's thinking is to improve the machine. If the systems are good enough, nobody will need support.

The systems are not good enough, and that has been true for a long enough time that a reasonable company would have realized that a good support team is necessary until some far-future time.

It's not a great analogy to Wordpress, which attempts to provide as much capability as possible in a CMS while requiring as little expertise from the user as possible. Vanilla Wordpress, kept up to date is pretty safe. Plugins are just a click away though, and using plugins safely requires evaluating each plugin's risk profile and track record individually, which is real sysadmin work.

I've been using it on my tablet, as I do find it to be a nice UI for the touchscreen, but I may switch to KDE because Gnome's onscreen keyboard is horrid, and difficult to replace.

Commercial operating systems aren't immune. I found several people having a similar problem with Windows 11 on Microsoft Q&A, as well as a thousand third-party sites offering instructions to fix it, likely all infested with ads for "fix your computer" programs that will make things worse: https://learn.microsoft.com/en-us/answers/questions/5583596/...

I'd expect Mac OS to be better, in part because it only has to support a few models of computer. Perhaps it is, but it's also not immune: https://superuser.com/questions/1756912/ethernet-interface-d...

The author's inability to uninstall or fully disable AI features is one for Mac OS. Window management is a common one for people used to other systems.

Windows has many, with (again) AI features that are hard to get rid of, and attempts to coerce users to create an online account being two of the most prominent lately.

So yeah, KDE's NetworkManager frontend is a little janky sometimes, and they should fix that. Is it worse than trying to coerce the user into using services they don't want to? For some people, probably. For me, no.

A citizen may only be denied entry if they're entering the country for the purpose of committing a crime, and if the government can prove that, they'll probably admit the citizen and immediately arrest them instead.

People keep misconstruing this.

The border search exemption only applies when someone is actually crossing a border, and it does grant broad authority to search whatever they're carrying with them at the time. The authority to do border enforcement within a 100-mile zone around borders does not grant a broad authority to search. It does grant a narrow authority to do things like traffic checkpoints, but those don't permit searches for anything smaller than a person without additional evidence.

I do think the ruling establishing the authority to run checkpoints other than actual border crossings was wrongly decided and harmful, but it's not what's at issue in this case.

Non-citizens don't get the right to bear arms as far as I know.

The footgun isn't `reduce` in particular, but failing to use `join`.

It's still pretty early, possibly buggy, and almost certain to get breaking changes without warning.

My original thought was to combine Lisp syntax and structural macros with C semantics and see how much extra abstraction that would provide, but variants of that idea have been tried before. They may have been compelling at a certain point in time, but I think a new systems programming language in 2026 should offer more, so it does.

Some features include: strong typing, protocols (similar to Clojure or Rust traits), non-nullable references, error values, bound error handlers (a bit like Common Lisp), optional lexical lifetimes, namespaces, and no mandatory runtime overhead relative to C.

It's self-hosted, which I've noticed several new systems programming languages announced recently are not.

More modern, and also capable of improvised cooking are handheld searchlights from Acebeam and Imalent with many large LEDs, cooling fans, and even bigger Li-ion batteries. There are third-party videos of these and the older halogen type cooking eggs and setting fire to paper on Youtube.

What you're describing from the ads obviously violates the laws of physics. An alkaline AA would have a hard time cooking an egg on a dead short.

Flashlights that can do this exist. I don't know if they're being advertised on Meta platforms.