Besides the cross-posts there is another discussion in
!world@lemmy.world (this link should take you to the community in your app/website):
https://lemmy.ml/post/29400920 (this link will take you to the post on the website I’m viewing it from)
about the link to the Reuters video: https://www.reuters.com/video/watch/idRW057230042025RP1/

Like I agree it is a better message in the edit, but I fear a lot of people are not ready to hear that yet and still need to work through the original before coming around to this… Still stuck in denial and whatnot.

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.

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).

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?

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 sometimes forget that this picture exists, and then I happen upon it in places like here and it just smacks me in the face how perfectly it encapsulates the total and utter loss of decorum in politics. I mean it was never perfect obviously, but in past times there was a somewhat reasonable expectation of politicians being civil and them losing their office if they were publicly caught out not to be. It was rare, but it happened. Yet here you have the supposedly “most powerful man in the world” just dropping every pretence and hustling for some company in a flagrant abuse of his office. It’s so brazenly corrupt. And the worst thing is this was just another Tuesday for Trump, mild shit-storm, on to the next fucked up thing he did. Society never even had time to realise what a historic moment this was. It was just dropped on the pile.

Nah, this one was a direct link on purpose. But the edit box swallowed the @lemmy.ca part at the end due to trying user name auto-completion, so thanks for making me re-read the post. Good bot!

Ah with that link it’s easy to track down what happened.

First you go to the community on the server in question: https://lemmy.world/c/alberta

Then you click on Modlog in the sidebar: https://lemmy.world/modlog/3835

And since there is pretty much nothing in it we immediately see the entry for your post saying:

reason: Deceptive content. Calling to abuse government system.

Note that when you compare your servers Modlog that entry is missing there, so yes, only removed for people connecting through lemmy.world.

Not sure how appeals work there, you can probably reply to the account that notified you, or go to the !support@lemmy.world community.

Do you mean not initially designed to support? Because at least for displays and networking (in the sense of being able to send X events over the network) that seems wrong, a network capable display server is basically X’s entire purpose? And for keyboards and mice there are extensions now, so x.org as a standard now very much supports those by design. Actually to my knowledge Wayland basically just forked their keyboard standard, the X Keyboard Extension.