I’m no longer sure what point you’re trying to make, but I don’t think I’m disagreeing with you. As MrEff described, and as you quoted, an underprivileged person might choose to hold the bag even if they have all the information because it’s the best chance they could get. And as I quoted, an underprivileged person might not have all the information. Both of these things can be true, and both show ways that whole classes of people can be mistreated.

From the linked Wikipedia article:

women executives are likelier than men to accept glass cliff positions because they do not have access to the high-quality information and support that would ordinarily warn executives away.

Sounds like it has similar goals to bcache (not bcachefs) and LVM caching, except that it operates in userspace instead of at the kernel level. Can you explain what the benefits are of keeping this out of the kernel?

Another fun fact: official German spelling later changed “thal” to “tal” (both pronounced as a hard “t”), so now the valley is Neandertal, not “Neanderthal”

The slowness was not a tax on the real work; the slowness was the real work. It was how the work got good, and how the people producing the work got good

This line reminded me of a couple of articles, linked below, that I read on AI use in astrophysics. Developing junior researchers is a big part of the point of their work, so they really are going to have to limit their AI use to make sure development happens. But worry that industry won’t care; they’ve been hollowing out junior positions for years, because there’s no value in training a senior who is just going to jump ship to a company that doesn’t train juniors. That’s an existing problem, but AI seems likely to make it worse.

• The machines are fine. I’m worried about us. by Minas Karamanis
• Find the stable and pull out the bolt by Natalie B. Hogg

And that’s only, like, the most basic part of an industrial e-stop. On top of directly disconnecting the energy source, it also has to include redundant circuits (since it’s possible for a contactor to break and fail open, or weld and fail closed), and some even need to have signal pulses constantly going through them to actively confirm they haven’t been pressed. They absolutely should not just send a signal to a Linux computer, because general-purpose operating systems are too complex to be rated for safety.

This isn’t even my area of expertise yet I know this stuff. The fact that they failed at the very first requirement is really messed up.

Even if you press that big red emergency stop button on the mower itself, a hacker can send another command to unlock it, Makris says.

Holy cow. I work in factories, and I know enough about industrial safety to know that would not fly.

I liked Buckminster Fuller and family’s use of “sunsight” and “sunclipse”. The way we talk about things affects the way we think about them, but pedantry is just annoying, so try on some neologisms instead.

It’s a forgejo instance. I don’t know why they don’t just say that.

They do say that. Has the article changed since you read it?

That’s why the Open Source Program Office (OSPO), a division within the Ministry of the Interior, has chosen to opt for Forgejo.

They don’t say it up front because it’s not too relevant to the article. The key fact is that the government is getting off of Github, not the technology they’re switching to, so that’s what goes in the headline.

I host a CalDAV server (specifically Nextcloud’s Calendar app, though plenty of others exist, like Radicale) and all my devices sync with it.

There is way too much sensationalism around this law. All this law calls for is an OS-level “Are you over 18?” button, the kind that’s been all over the internet for decades. See the Ubuntu mailing list discussion for a possible technical approach. There does not appear to be any requirement for age verification beyond that of the system administrator, and reporting is by a total of four age brackets, so even the privacy impact is limited.

The benefit of something like this is that age can be enforced by the system administrator rather than the user, so parents can set their kids’ computers with an accurate age bracket. Meanwhile, all of us with just a single user can set the highest age brackets and move on with our lives. Now, as the CEO of System76 says, kids will find ways around it, and we shouldn’t discourage kids from controlling their own computers, but he says “If there is any solace in these two laws, it’s that they don’t have any real restrictions”.

But that same article notes that New York has a proposed bill S8102A that is much more draconian. California’s law is a minor nuisance, while New York’s bill sounds like an outright danger. Please focus on a real threat, especially considering it’s much easier to change laws while they’re still only bills.

Distrobox might be the easiest way. If you use a custom HOME directory you can even keep the build artefacts isolated.

Nice review of the historical trajectory of desktop Linux. I was surprised that the article mentioned Homebrew rather than Distrobox. This is the first time I’ve seen Homebrew given as a solution for command-line tools on an image-based desktop.

That centralized low-power machine can even be your phone, if it has enough storage for your needs.

This is exactly how I use Syncthing, and as the author says, it sure would be nice if more things were just files. Really, most things are stored locally as files, but not always in a way that plays nice with syncing. Like, I can sync my Firefox profile between machines (it’s all in one folder), but I found it prone to conflicts, with little to resolve those conflicts.

In a similar vein, local-first apps built with Conflict-free replicated data types (CRDTs) can be another way to avoid server dependency. I haven’t seen any significant apps built this way yet (just occasional blog posts about it). I imagine the CRDT approach would work better for individual apps, since conflict resolution can be written in a way that works best for a given app, but I also imagine that such apps would not play nicely with a generic sync solution like Syncthing.

I believe that’s pretty much what happened after the dot-com crash. A lot of fiber was laid during the bubble, it went dormant after the crash, but it was useful afterward as the internet continued growing.

Yeah, this one’s completely different from the one I remember. I found this blogspam around a greentext that matches my memory.

I just looked it up. It’s actually 61,839 blocks in each axis.

Procedurally crafted tools, no restrictions on build height, a massive view distance are all very cool.

I’ll note that the well-established Luanti (formerly Minetest) has no restrictions on build height[1], but I have always wished I could get a longer view distance. And I’ve never seen procedurally crafted tools, but Luanti has extensive mod support, so I wonder if it would be possible.

[1] Okay, technically it’s restricted, but the limit is something like a 64 km about a 62 km cubic space, which is much more than I could reach.

Thanks, that’s an excellent article, and it’s exactly what I was looking for.