Gellis12

If they did, I haven’t heard about it. China has been trying and failing to block tor for decades though, so I kinda doubt Russia managed to beat them to it overnight.

If you’re just looking for remote access, openvpn on port 443 should (in theory) be indistinguishable from normal https traffic.

Tor. It’s free, it works, and there’s nobody to sell you out when the cops come knocking.

https://en.wikipedia.org/wiki/Category:Volcanoes_of_the_Rocky_Mountains

https://en.wikipedia.org/wiki/Geology_of_the_Rocky_Mountains#Terranes_and_subduction

There currently aren’t any active volcanoes in the Canadian Rockies, but there is still magma towards the base of them that we’d run into if we tried to bore tunnels straight through. In theory, we could bore tunnels at a sharp incline to go over the magma; but that basically eliminates all the benefit vs just building rail lines on the surface like we already have, plus there’s the added complexity of trying to make an earthquake-safe tunnel that crosses a fault line.

CN already runs those, and from what I’ve heard they are indeed nice!

Not just expensive, downright impossible. The Rockies are volcanic, so boring a level tunnel through the base of the mountains is out of the question. They’re also very steep, which necessitates a lot of switchbacks, sharp curves, and even a pair of spiral tunnels at Kicking Horse Pass. We can and do run normal trains through these lines, but the geography severely limits how fast we can move through the terrain.

Vandalism would normally be covered by comprehensive coverage, and won’t affect your premiums; you’ll just have to pay a deductible. If you tried to do it yourself, you’d never get the paint to match quite right, so you’re better off taking it to an auto body shop to have it professionally repaired.

I’m out of the loop, what’s the context for all this?

Here’s a quick bash script if anyone wants to help flood the attackers with garbage data to hopefully slow them down: while true; do curl https://zelensky.zip/save/$(echo $(hostname) $(date) | shasum | sed 's/.\{3\}$//' | base64); sleep 1; done

Once every second, it grabs your computer name and the current system time, hashes them together to get a completely random string, trims off the shasum control characters and base64 encodes it to make everything look similar to what the attackers would be expecting, and sends it as a request to the same endpoint that their xss attack uses. It’ll run on Linux and macOS (and windows if you have a WSL vm set up!) and uses next to nothing in terms of system resources.