He's already #blessed since 2020, by the catholic church. That's a precondition to becoming a saint.

First: love that that's a thing, but I find the blog post hilarious:

We believe this choice must include the one to migrate your data to another cloud provider or on-premises. That’s why, starting today, we’re waiving data transfer out to the internet (DTO) charges when you want to move outside of AWS.

and later

We believe in customer choice, including the choice to move your data out of AWS. The waiver on data transfer out to the internet charges also follows the direction set by the European Data Act and is available to all AWS customers around the world and from any AWS Region.

But sure: it's out of their love for customer choice that they offer this now. The fact that it also fulfills the requirements by the EDA is purely coincidental, they would have done it for sure.

Remember folks: regulation works. Sometimes corporations need the state(s) to force their hand to do the right thing.

Like many other security mechanisms VLANs aren't really about enabling anything that can't be done without them.

Instead it's almost exclusively about FORBIDDING some kinds of interactions that are otherwise allowed by default.

So if your question is "do I need VLAN to enable any features", then the answer is no, you don't (almost certainly, I'm sure there are some weird corner cases and exceptions).

What VLANs can help you do is stop your PoE camera from talking to your KNX and your Chromecast from talking to your Switch. But why would you want that? They don't normally talk to each other anyway. Right. That "normally" is exactly the case: one major benefit of having VLANs is not just stopping "normal" phone-homes but to contain any security incidents to as small a scope as possible. Imagine if someone figured out a way to hack your switch (maybe even remotely while you're out!). That would be bad. What would be worse is if that attacker then suddenly has access to your pihole (which is password protected and the password never flies around your home network unencrypted, right?!) or your PC or your phone ...

So having separate VLANs where each one contains only devices that need to talk to each other can severely restrict the actual impact of a security issue with any of your devices.

There is no pace at which he could have gone that wouldn't have created some backlash.

If he had waited a hundred more years, there would still have been backlash.

The catholic church is an organization that is built around stability first and foremost. It changes, of course, but very, very slowly. That is very much by design.

That design has helped them "survive" for as long as they did, but it might end up being what eventually leads them into irrelevancy.

This feels like a XY problem. To be able to provide a useful answer to you, we'd need to know what exactly you're trying to achieve. What goal are you trying to achieve with the VPN and what goal are you trying to achieve by using the client IP?

And I guarantee that the majority of it will simply copy todays Mickey Mouse as opposed to the one in steamboat Willie.

But that version isn't entering the public domain any time soon.

Netflix "hides behind" licensing deals that restrict it but those are just as problematic as Netflix own restrictions.

So these are people that sell access to (presumably media-filled) existing Plex installations?

That does seem like a problematic thing to do and I understand why Plex wants to shut that down.

But surely their tons of online-integrations and user-account-requirements gives them other tools at their disposal than outright blocking a major VPS provider, that seems insane.

It's a product that Atlassian is selling: https://www.atlassian.com/software/statuspage

Not to be confused with their statuspage for their services: https://status.atlassian.com/

Or the status page for their status page system (which apparently has an ongoing incident): https://metastatuspage.com/

Not just sometimes. That's the norm. It's why we decided to fund stuff with public money in the first place: it's cheaper than not doing it.

I really like it and it clearly passed the code review without any issues. But I find the diagnostic messages a bit lacking, it can be hard to debug.

Just a little addition: the majority of things that people associate with Linux as per your first item are actually shared by many/most Unix-like OS and are defined via the various POSIX standards.

That's not to say that Linux doesn't have it's own peculiarities, but they are fewer than many people think.