The geographical data already exists in digital maps. And I would expect competent militaries already have maps of enemy territory. It's the second part that was so far missing.

This combined set allows the training of AI models that can say, "When my surroundings look like x, that looks like y on a map".

So when your drone's GPS gets jammed, it can look at its surroundings, reference its (internal and offline) maps, figure out where it is, and navigate.

> While we did initially start out on a single computer in 1987, the

> SDF is now a network of 8 64bit enterprise class servers running

> NetBSD realising a combined processing power of over 21.1 GFLOPS!

Which piqued my interest about how that compares to today's computers. nVidia's venerable 1080Ti from 2017 measures about 11300 GFLOPS, or 11.3 teraFLOPS. About a fifty times increase.

The main benefit of sleeping to RAM is of course the resume speed, which makes it more suitable for when you just left your computer inactive for 15 minutes. That goes double if you use encryption without TPM unlocking.

For leaving your computer overnight, hibernate wins on all fronts. I'm enthusiastic about sleep-then-hibernate schemes, but haven't gotten them to work on my devices yet.

The one major issue I had from the start was non-free Bluetooth codecs like AptX. That required me to taint the base image and add a non-official repo. It was messy but that was mostly down to it being a learning process, if I had to do it again I could probably do it with a single run of `transactional-update shell`.

The installer is super minimal and surprisingly user-friendly. One thing I remember is that there was zero partitioning choice: just use the full disk for encrypted btrfs and you get no swap (but zram swap is on by default). If you use OpenSUSE with secure boot enabled (as intended) then hibernate is prevented by `kernel_lockdown` anyway.

Snapper by default is nice, but you also get that with Tumbleweed. I ran into no applications that I couldn't get from Flatpaks or export from a distrobox, the latter being mostly for obscure stuff I need to compile myself. And my main toolbox hosts my Emacs environment that I spend most of my time in besides Firefox.

It's hard to recommend a MicroOS desktop over Tumbleweed, the latter being a great all-purpose distro as it is. But I'm hoping the benefits of forcing this "rootless" paradigm on myself will appear when it's time to move to a new machine. Just copy over my home directory and distroboxes and I'm golden, I could even switch to ARM without hesitation.

The distroboxes help with migrating because if I want to compile a newer version of that obscure program from earlier, I don't have to hunt down all the arcane requirements again. They're all still there waiting for me, in a Fedora/Ubuntu/Arch/whatever distrobox, depending on what works best for that program. At least that's the theory.

Happy to answer questions.

When I first read about the chardet situation, I was conflicted but largely sided on the legal permissibility side of things. Uncomfortably I couldn't really fault the vibers; I guess I'm just liberal at heart.

The argument from the commons has really invoked my belief in the inherent morality of a public good. Something being "impermissible" sounds bad until you realize that otherwise the arrow of public knowledge suddenly points backwards.

Seeing this example play out in real life has had retroactive effects on my previously BSD-aligned brain. Even though the argument itself may have been presented before, I now understand the morals that a GPL license text underpins better.

The linked post by F-droid additionally points out that even that very bad case is not certain. We shouldn't trust that Google will even allow sideloading at all based on their words on their own blog.

Media has a responsibility to report that there is no evidence that Google will even allow anyone to sideload at this point.

I'm most excited to try the perceptual analizer, which was something I found always had disappointing performance in plugins.

Which of the new features would you say posed the most interesting engineering challenge?

Vertical integration makes it possible but motivation makes it happen. Where is Samsung's ultra LTS Exynos device?

> I'm surprised that, having something immutable, you'd choose to go the other direction.

I can somewhat imagine that having been limited by space and having to swap out disks all the time one would jump on the train of mutability without fully appreciating the benefits of immutability.

That being said, for real portability of programs that have slightly outgrown the script moniker I really like Janet.

https://janet.guide/scripting/

It can compile your script to a static binary for distribution.

Is this implied, or is this detailed in the law? I can see why this would make sense. So many businesses just have a link to their facebook page as their business website, which you should still be able to view. And presuming platforms like YouTube fit the definition, banning kids from watching anything on there would be pretty rough.

> One might argue that this removes the algorithmic feeds. But I would wager that social media companies will just use browser fingerprinting to continue to serve algorithmic content to logged out users, if they aren't doing this already.

On the subject of YouTube, I wonder if they would allow for the creation of teen accounts, which restrict all social media functions but allow subscriptions. But would that then also remove algorithmic recommendations? What about data harvesting off those accounts? If so, I might have to look up how to get a teenage fake ID.

Of course the coin thing somewhat relies on coins of mentionable value being in common circulation, which rules out the US from the start.

Here few people still carry coins since contactless, but most still have a fake euro coin somewhere on their keyring or in their car for shopping carts.

They hand out these fake coins, which are usually branded with the supermarket's logo, for free inside the shop. But the system still works because having to go inside for a new coin negates the saved effort of not bringing back the cart. And there's probably some feeling of discomfort associated with abandoning the cart with your coin still in it.

We do have small parking lots here, and many carts have a coin deposit mechanism. It's not just that we're a morally superior people.

My current hobby language is janet. Creating a statically linked binary from a script in janet is trivial. You can even bring your own C libraries.

For now at least, some can't even determine which hand they have:

> LLAMA bets $170 on Flop > "We have top pair with Tc4d on a flop of 2s Ts Jh. The board is relatively dry, and we have a decent chance of having the best hand. We're betting $170.00 to build the pot and protect our hand."

(That's not top pair)

Usage of user-created plugins and access to cloud accounts aggravates the risk posed by a vulnerability.

Open source reduces vulnerabilities over time, so those who want to heed the author's warning may indeed want to switch to an open-source Markdown editor. Just not because the Obsidian team is Evil.

It is quite fun to try and think of ways that this could work though. Perhaps a bot that code-paraphrases (paracodes?) every accepted PR. Or maybe there's some crypto magic you could do to make the only option a clean room rewrite.

When a project requires a certain Python version a virtualenv suffices. But when you need a specific Python and NPM version then I might as well make a distrobox. Set a custom home and the project is isolated, speaking only to my IDE over LSP, and also to my web browser I suppose.

This only protects the developer themselves of course, but it's a start.