Yes. But also, despite having done it literally thousands of times, I still can't tell you which way round to put the target and the link name for a softlink on the first go.

My first guess is always

 undefined

    
ln -s $NAME $TARGET

  

No amount of repetition will fix this.

Sounds like you have reason to bump it up the list now - two birds with one stone.

I need to do this too. I know I have stuff deployed that has plaintext secrets in .env or even the compose. I'll never get time to audit everything. So the more I make the baseline deployment safe, the better.

It's common with rootless docker/podman. Something needs to start up the services, and you're not using a root enabled docker/podman socket, so systemd it is.

Lots of this is covered in longer form, though still light detail in this video

Quite right, any country will do - that way the post is useful to more people than just me!

I'm not American, I just live somewhere where literally everything is international to me, so it doesn't matter if it comes from Timbuktu.

We're so proud of you

Also, your literal interpretation is much funnier - bothering god reminds me the Bruce Almighty scene with all the emails and post-its coming from the same person

That's the correct way of reading the structure of the word, but as always with english, there's how it's written, and how it's meant.

Almost universally, this is meant as someone who is bothering people about god, like jehova's whiteness knocking on your door, or wandering mormons inviting you to their church.

Sounds like I won't be using Vanilla because that (obsidian + synching + tailscale) is definitely my primary need.

The last time I played with it, I just remember thinking, cool - but why?

This issue is described by Poe's law.

Also, nothing electronic implements the various suggestions on irony punctuation.

I dunno about that, but there is a bit in there about burning bulls testicles to appease the lord god

That's fair, there's other angles of observation made available already.

Seeing as you like speculating about cyberpunk, how about if observation is just the initial way to way to sell the drone cloud? Depending on how cheap you can make them, there's an argument to made for reducing time-to-intercept for low-speed aerial objects.

If you've got a bunch of drones overhead already, you could run one in to the path of a kamikaze drone, or if your swarm is even lightly armed, you can extend engagement range and reduce required accuracy with a single buckshot shell to shoot an offending drone down.

If you're content to prioritize executive safety over public saftey, there's a lot that can be done.

Drone displays terrify me.

Not to mention, the minute it happens, the government will carpet the skies with observation drones in the name of safety

Just a little piece

That's what I was thinking, I know the pain of watching something run for ages, only to finally get past where it failed last time and run straight in to another stumbling block.

I don't envy you having to work in an SELinux environment with less than stellar developer understanding of policies and contexts.

Is it not possible to run it in audit mode in dev and have it tell you what the would have blocked?

I'm saving and planning to pay a $900 electricity bill in August.

Window units are a thing, and I recommend you get one.

Quad9. Swiss based, dnssec available, has beaten blocking orders by Sony before.

They're about as open as resolvers get, and they pretty much released everything they could when courts tried to interfere with them.

This article is basically referencing the same event as OPs article, but after Canal+ expanded the scope of their legal challenge.

And a dnssec policy will solve that for you

Devils on horseback!