med

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

I run grim/slurp

Looks like it does, but can you confirm if the script run fine from the terminal?

Can you send your hyprland bind config from your hyprland.conf? You'll want it set up as a global bind so no applications eat the keypresses.

Also, have you looked at wev or xev to find the name of your printscreen key?

https://wiki.hyprland.org/Configuring/Binds/#uncommon-syms--binding-with-a-keycode

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?