FYI you have a typo in your last screenshot (This sign m[a]y not…):

I don’t know if there is any single takeaway here, this story is just fucking ridiculous on every single level.

1. They bullshited themselves into a search warrant based on typical cannabis “investigation methods”.
2. In a state where recreational cannabis use is legal.
3. Persisted in the search even after their main argument for it, high energy usage indicating a grow-op, fell away when it was clear it was indeed a medical facility.
4. Made the motherfucking “Gun flies to MRI” TV trope a certified reality. This is a thing that verifiably happened now.
5. Instead of getting help, used a sealed (!) emergency shutdown button…
6. …which damaged the machine. And released thousands of dollars worth of helium gas.
7. Forgot their loaded magazine on the ground.

This can’t be real. I’m fucking dying over here. Please let there be bodycam footage of the cop speaking in a high pitched voice after. (I know the helium was probably not released into the room, but one can hope I guess)

android auto

First I heard of this, but since it seems to be just some software that runs on the hardware of car manufacturers it seems rather unlikely. But very theoretically possible, if the car manufacturer was using default process scheduling in a CPU constrained machine and now switches to real-time scheduling in an update. But that was possible for years before this news, the code has just been mainlined to the default kernel now. If the car manufacturer cared about that they would probably have done it already with a patched kernel.

And further from that, maybe if Youtube’s Chief Enshittification Officer is against it then taking 23andme private might actually be the best thing to do?

And it keeps getting worse. Basically the whole base plus some forests and residential areas seem to be burning.

I think these are satellite measurements that accumulate over 24 hours though, so not sure if the image reflects the current situation well.

Link to the NASA map btw if anybody wants to check it out

Because bee stingers are mostly used against other insects. They don’t get stuck in a chitin exoskeleton, only in the more flexible skin tissue of mammals. In insects the barbs instead pull out soft tissue from inside, thus making them more lethal (to the bees victim).

Sittenhaft

*Sippenhaft

Sippe = kin/clan Sitte = morals/tradition

You thought it was AI, but she just has ulnar polydactyly. How do I know this is ulnar instead of radial or central polydactyly? The wedding ring, it’s on the ring finger.

(/s of course, this is obviously AI. But yeah people with extra fingers do in fact exist. They or the parents often cut away the extra finger for cosmetic reasons.)

I’ll have you know that this is famous sci-fi author Charles David George Stross posting an excerpt from his seminal novel Don’t Create The Torment Nexus. The warning is right in the title, I’m sure nobody will be dumb enough to ignore it!

Depends on the kind of colour blindness you have I guess. I think I have the congenital red-green blindness common among men, and saturate Just Works™ for me. Plus I don’t have to fiddle with setting a rotation degree there.

Oh yeah, can’t use the same IP range as your LAN, that will lead to problems. :D Glad it’s fixed.

Out of curiosity, does forwarding work now without the output (-o) command in PostUp?

PSA for my fellow colour blind people, you can use inspect element option of your browser to add a filter: saturate(100); rule to the element for this kind of image:

Like I said in another thread on this post, I’m pretty sure that’s because they are forwarding input but not output in the PostUp rules. Setting a /32 in AllowedIPs works fine for me.

What are you trying to say? That reply also shows AllowedIPs set to a /32 on the server side.

I don’t think that’s what the setting does. Anyway, I have them set to a /32 IP in my server config and it works nonetheless. I get full access to the /24 behind the server from the client.

You have ALL traffic being routed over Wireguard here.

Please correct me if I’m wrong, but isn’t it the other way around? All Wireguard traffic is forwarded to the local interface.

I think the problem might be your PostUp/PostDown lines have an in-interface (-i) but are missing an out-interface (-o) for the forwarding. Try this:

PostUp   = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o ens3 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o ens3 -j MASQUERADE

I don’t think capitalism is necessarily at fault, nor must the working/middle classes be struggling for fascism to emerge. If anything, quite the opposite. It is the better off countries that end up turning fascist. All fascist countries are/were first world countries, in various states of advanced development.

That’s not right, at least not for the fascist regimes in Europe that emerged prior to WW2. The countries where it happened (specifically Germany/Italy/Spain) had all seen civil unrest or even civil war in the recent past, they were hit hard by the global financial crisis in the twenties and had high unemployment and widespread poverty. This was the very thing the fascists used to ingratiate themselves to the public at large, by creating jobs through massive public building and rearmament projects.

By the way “first world countries” is post-WW2 terminology and didn’t originally have a connotation of superior economic status, but was referring strictly to ideological alignment. Whether a country belonged to the capitalist/communist/unaligned block in international politics during the cold war.

Hence my disclaimers in said post, and my efforts at explaining following your accusations.

Learn to read.