kosinus

Like, the bad bots you see when they get an https cert issued and it becomes visible in the public logs, or something else?

Agree discord sucks.

I was playing around with LG TV homebrew a while back. Still have the same TV, and in the age of AI, I'm considering putting a coding agent to work on a dump of the filesystem to see what it'd take to run stock Linux on it.

One of the reasons The Netherlands abandoned voting machines was because of electromagnetic emissions that could be read tens of meters away.

There are so so many reasons to get arrested for social media posts that have nothing to do with censorship.

Author here. Yeah, unfortunately, that's kinda it: just rebuild a lot. At work we have a custom setup with a build server and agents for provisioning, which is nice for multiple nodes, but also even slower. The QEMU setup in the attached repo was added later and also handy for testing multiple nodes. QEMU is also nice because you can just trash the disk images to get a clean start.

Author here.

You're right, it's very much a trade-off and preference where you put control, NixOS or Kubernetes. I'm not so much torn, but more believe you always have to weigh pros and cons.

For CoreDNS specifically, this setup adds CoreDNS to every node, and every node does DNS locally, so there's no redundancy benefit to using a Kubernetes deployment for CoreDNS. It does become a benefit as soon as you can't have a CoreDNS per node. I guess the obvious downsides to CoreDNS per node are that cache becomes very spread out in larger setups, and you may end up hammering your API server and upstream DNS servers more.

You can also start QEMU/KVM powered VMs with Incus, I assume that's also possible with IncusOS?

What is cutting off the ICC if not restricting. I think that was a pretty blatant move, and is a large part of the chain reaction we're seeing now.

I have no idea how the terminals operate, but I was on a flight two days ago and paid with a debit card. The flight otherwise required devices to be in airplane mode. Though there are flights that offer wifi, so there's a good chance the terminal can communicate with the ground, but they just don't allow anything else.

Debit cards are most definitely accepted on planes.

I think that is true when you initially switch and are still comparing browsers, but I certainly no longer check if something broken happens to work in Chrome. Stuff may equally be broken by my adblocker. Too lazy to debug someone else's work.

Personal gripe, but there are a gazillion note taking tools, but very few of them do real-time collab.

Me and my partner currently use Apple Notes for this, simple stuff like grocery lists, todo lists, etc. But Apple Notes perf is abysmal with real-time collab. The app constantly hangs and fans are spinning non-stop. iOS is not much better.

It goes on to say:

> The EDPS has also decided to order the Commission to bring the processing operations resulting from its use of Microsoft 365 into compliance with Regulation (EU) 2018/1725.

Which, to me, reads like they can keep using Microsoft 365, they just need to work with Microsoft to bring it in compliance.

So my guess is your second interpretation.

Thanks for pointing that out! Maybe we can improve on that, even if we keep it as a non-goal.

Right away, a partial mitigation for current versions of Portier is to modify the `email_*.mustache` templates to remove the link. But a second piece of information Portier leaks is simply which sites you're logging into. That's right in the subject for Portier, and not something you can customize for current versions.

I think it's worthy to try and harden against this type of attack, but I'm worried the effect is limited. There's often nothing stopping someone from simply starting the login process / creating a new session, so an attacker just has to know where, and there are a bunch of ways to find out.