It sounds to me like the goal there is to spell out everything you don't want the agent to make assumptions about. If you let the agent make the plan, it'll still make those assumptions for you.

FWIW, NLNet is distributing EU funds, not Dutch funds.

That said, the Dutch government is collaborating with La Suite (fr) and OpenDesk (de): https://minbzk.github.io/mijn-bureau/

> People always will want the fastest, best, easiest setup method

When there are no other downsides, sure. But when the frontier companies start tightening the thumbscrews, price will influence what people consider good enough.

As I understand it, it's not all of it in Solvinity's hands; I think it's mostly infrastructure. Still, apparently it's not a matter of pushing a button to migrate off of that infrastructure.

All they'd learn that way is that that phone number has a Signal account, when it was registered, and when it was last active. In other words, it doesn't tell them whether it's part of a given Signal group. (See https://signal.org/bigbrother/.)

I think it was mostly a joke about IE being horrible.

Direct link for those interested in chipping in: https://servo.org/sponsorship/

Security concerns are exactly the reason the format doesn't have native support yet. However: https://github.com/mozilla/standards-positions/pull/1064

That's not the reason, but the excuse. The reason Firefox doesn't have jxl is that it is funded by Google, and someone at Google decided that it has to die.

Also the parent comment was about that you really shouldn't just let a random Russian guy run any javascript on any website you visit, that's stupid.

Also also, am I missing something, or Firefox extensions are broken, there is no way to limit an extension to websites (allow or disallow), or even just to check the source code of an extension?

The link I posted shows that Jpeg-XL will come to Firefox, and that that same Google is the one making that possible by writing a secure implementation.

> That's not the reason, but the excuse. The reason firefox doesn't have jxl is that it is funded by Google, and someone at Google decided that it has to die.

So what, you think they were just lying when they said that they'll ship JXL when it has a Rust implementation? You think Mozilla devs were just bluffing when they were working directly with the JXL devs over the last year to make sure everything would work right?

No, I don't think they can withhold support if it's a no-brainer to support it. But they also tried everything they could to not support it.

It's not a particularly old company (a little over ten years I think?), so presumably they've had to learn a lot of those kinds of lessons at the start of their lifetime. But at this stage, I'd assume they've learned the lowest-hanging lessons, at least.

I'm fairly sure they don't; at least historically, the goal has been to improve the situation on the ground, not to move production elsewhere. (I think this was the post in which they explained that thinking, but I didn't reread it just now: https://www.fairphone.com/en/2025/10/15/lets-talk-about-fair...)