Wary reader, learn from my cautionary tale

I’m not sure what to learn exactly. I don’t get what went wrong or why, just that the files hit deleted somehow…

I guess technically that makes them “not in Ukraine”, but it is the same war in the end. At least for me that’s the important part, not where exactly on the front line they are.

Well, NK and Russia have a defense treaty which obliges NK to sent military assistance to Kursk. So if they aren’t, they’re breaking their obligations.

In September the NixOS constitutional assembly should finish their work, and the community will be able to elect governance. I’m guessing that’s when the drama will start getting resolved.

In the meantime, there are multiple maintainers that have left because of the drama - which is more troublesome than the board members leaving - but nixpkgs has a LOT of maintainers, and there are new ones joining all the time. It’s still healthy and won’t implode so quickly.

They are major concerns, but they aren’t the only reasons people would use Linux, and also not everyone who uses Linux does it for these reasons. For example, while I care about them, my most important reason for using it is utility features such as my tiling WM.

That only works if the main reason someone uses Linux is personal privacy.

The biggest issue is that there isn’t a universal agreement on what causes harm. There is agreement on the basics - murder, violence, etc - but they’re already illegal anyways, no need to ban them by license.

upcoming EU AI Act that regulates open source systems differently, creating an urgent need for practical openness assessment

So when they say “openness” they do put it in the context of open source rather accessibility.

Because FOSS shouldn’t add burdens. You publish your work and let everyone else use it. That shouldn’t add extra obligations on you. Usually, you’d also write some docs - after all, without them nobody will know how to use your program, so why bother publishing - but it shouldn’t be an obligation. Make it easy for people to open up their code without this attaching strings.

Documentation is nice, but it’s kind of different thing that open source: a program can be open and undocumented, or closed but well documented - and I don’t see why we’d want it different for models.

A bunch of these columns are outright absurd TBH, to the extend I’m not sure the author really knows what FOSS is about. What’s open API access even supposed to be - API access is closed by definition.

Also there has never been a requirement that open source software needs to be documented - and for good reason - so I’m not a fan of the documentation column as well.

However, it also uses halium and libhybris. That means you can’t just install your favourite distro and upstream tools. Everything that needs GPU acceleration needs to be patched for libhybris. For example, that means no upstream wlroots - and the latest patched version I think is 0.12 or so.

Actually, no, this seems to work on a very different principle.

Not really. It seems to use a very different technology from termux.

15 hours for what period of time? The article mentions they’d refill in two days…

I like the idea, but I really hate that they’ve hardcoded the provider.

How do you declaratively apply the configuration? Is that a feature of Kvaesitso?

Good point. I’d try to grep for something like [Bb3][Ee3]g[Ii1][nη]\w+ but I just know I’ll miss something

Oh, in that case we don’t need to read either - just run a simple grep!

Finally, presumably if anyone added some malicious code in a their program, it would be sneaky and not obvious from quickly reading the code.

On the one hand, doas is simpler. Less code means less bugs, and lower chance someone manages to hack it and gain admin rights. On the other hand, sudo is more popular, and so has a lot more people double-checking its security. Ultimately, I don’t think it matters - when someone unauthorized gains admin rights, usually it’s not due to bug in sudo or doas, but other problems.