That is probably an option in about 5 years, if at all.

WDYM? Germany will operate a hybrid fleet, with the majority of the fighter jets being Eurofighters, and the F-35s being used for nuclear sharing. At least that is my understanding. 3. is a hybrid fleet option

He’s right in my opinion.

The issue is that under the nuclear sharing agreement, Germany has to provide the bomber jets.

As part of nuclear sharing, the participating countries carry out consultations and make common decisions on nuclear-weapons policy, training, and deployment, and maintain technical equipment (notably nuclear-capable aircraft) that is required for the delivery of nuclear weapons.

To be nuclear-capable, an aircraft needs to be certified by the US in this case since they provide the nuclear weapons. In the past, this was done for the Tornado; that one however is being phased out due to age.

So the options are:

1. get out of the nuclear sharing agreement. I don’t think that’s currently a feasible option for Germany.
2. Certify a European aircraft. There’s no guarantee that a verification will be successful, but what will be guaranteed is that all design documents are to be provided to the certification body. I don’t think Europe is currently willing to reveal all their know-how in that domain to the US. Apart from that, I’m not aware of a current generation bomber jet, only fighters, but I don’t really care about that topic so maybe one exists.
3. Buy a certified US aircraft

So yeah he’s correct in that this doesn’t increase dependence on the US, the dependence stems from the nuclear sharing agreement itself, not this purchase.

I think so too actually if you’re looking to learn the basics.

Arch has very little actual “distribution” in its system (mostly pacman and mkinitcpio) and the former is a glorified tar with a database, and while it can run scripts, you’re expected to configure and set up everyone yourself using the upstream tools, and these usually come vanilla

I daily drove it for 15 years before I switched so it’s not like Arch is insured for that. But if you want to learn the basics of modern Linux it’s a good choice

And they too will be let believing they’re part of the in-group until they’re no longer useful

Spahn has been meeting with Trump and his allies (Grenell, Thiel) for years. It was Merz’ own party sanitizing that administration. Now they’re noticing they’re not actually part of the in-group. Get fucked

Technically, the question was even easier (yes/no), but I agree with the sentiment

Well, but the question wasn’t “what is a hash used for”, but rather “what is a hash”

Keep in mind this is a statement by a manufacturer who’s trying to get his customers to sign long term contracts at current prices, so it’s in their interest to have people believe that the shortage continues.

Doesn’t mean it’s not possible, bit it should be read in that context

Often times when there was a big new update for GNOME, I’d try it out, decide I still don’t like the concept and go back to plasma.

I don’t get the appeal of that desktop. Even the tiniest changes need gnome-tweaks? Why isn’t that stuff part of the base settings? But ok. You can’t ungimp GNOME. The usage concept is baked into it. Fine. But why?

I mean there must be people who want this and nothing else, otherwise people wouldn’t use it.

These protections work at different layers and hence, you use both.

First off, you can’t really encrypt the first boot loader by design, your UEFI needs something it can read and run. You need to protect this first boot stage somehow, and this is what Secure Boot is for; it verifies the signature of the payload it starts to protect it against tampering.

1. The spec allows changing keys by the user as far as I know
2. I’m unaware of a proposal of a better concept that stops attacks at this layer

I think once you’re at the level of caring about that stuff you’re no longer considered a newbie

Introducing the dummy thiccpad

I will roll into my grave

That’s a fun 50/50

You’re not supposed to modify shipped unit files, that’s why systemd supports drop in snippets

resolved is entirely optional and disabled by default, I use it on case of non-mobile devices but leave it on laptops etc.

DNS resolution isn’t something exotic, it makes sense for systemd to implement it in a simple optional daemon

No od either

It’s Stockholm syndrome

I mean who doesn’t like putting mandatory quotes around all variables (though exceptions, like in [[ ... ]], apply)?

Or keywords like fi and esac or worrying about $IFS