I never claimed it to be fine, to be clear, but again from a purely objective standpoint it seems like a pretty small cost to pay to contribute to the erosion of power a fascist, racist, hateful, and truly dangerous borderline hegemon wields. Perhaps I’m limited in perspective, but at first glance I see 2 main outcomes assuming you’re siding with the vandals: -The Tesla owner disagrees with Elon and was able to claim insurance on the car they’d likely otherwise take a bath on if they tried to sell (especially in Germany) and presumably wanted to get rid of: win-win. -The Tesla owner agrees with Elon and is an enemy of the vandal, which I’m sure they’d consider a win-win (damaging the market image of Tesla, harming an enemy)

To clarify once more, I am not saying I agree with or support the efforts of arsonists targeting regular people, but it seems like there’s asymmetric cost on the side of Tesla assuming properly insured/financially positioned owners so what they’re doing makes sense overall, and is likely effective. Let’s be real, Teslas are positioned as luxury vehicles; these aren’t people scraping buy that are being harmed.

If you have a car that valuable without comprehensive insurance, you were going to learn a hard lesson one way or the other imo. Something as simply as a bad rain storm can really expensive damage. Also, from an impartial perspective, used cars that attract crime seriously harm sales of other used and even new examples; Hyundai/Kia is an excellent example of this. Tesla has already lost virtually all of its reputation yes, but knowing it might be burned to the ground at any second will have even Elon supporters second guessing a purchase.

national “buy comprehensive” day would be a pretty strong signal to send

Not that I don’t believe you, but how are you sure that a kernel update is what fixed the Wi-Fi issue? Can you tell me how you came to that conclusion?

Also, have you tested the boot drive on the other laptop? It’s very likely that it has a different Wi-Fi device and therefore uses a different driver in the kernel. Let me know and I’ll help you as much as I can 🙂

I love flameshot, but unfortunately it’s support for more than one monitor on wayland has me looking for an alternative :(

Alternative found: Spectacle in rectangular capture mode is the best

I’m aware, but thank you. This post was intended to be a guide for people that end up in this situation.

I’m aware. The post was simply to get a recovery guide out there for a crappy situation.

This happened a while ago and I’m well past it. The point of the post was to help others that ended up in the situation, not sell best practices.

100% my stack going forward. Thanks!

That’s the move.

I’m aware. Any local storage wouldn’t do much about a poorly aimed rm, though.

Disturbingly effective is definitely the right phrase. It’s actually inspired me to create a script on my desktop that moves folders to ~/Trash, then I have another script that /dev/random’s the files and then /dev/zeros them before deletion. It eliminated risk of an accidental rm, AND make sure that once something is gone, it is GONE.

The server we were working at the time wasn’t configured with frequent backups, just a full backup once a month as a stop gap until the project got some proper funding. Any sort of remote version control is totally the preventative factor here, but my goal is to help others that have yet to learn that lesson.

As others pointed out, version control is probably the best fix for this in addition to traditional backups. My goal in this post was to help others that have yet to learn responsibility save their ass and maybe learn their lesson in a less pleasant way.

100%. The organization wasn’t there yet and seeing that I wanted to remain employed at the time I wasn’t going to put up a fight against management 3 layers above me. Legacy business are a different beast when it comes to dumb stuff like that.

I’m not denying that stupid stuff didn’t happen nor that this wasn’t entirely preventable. There’s some practical reasons that are unique to large, slow moving orgs that explain why it wasn’t (yet) in version control.