brooksgarrett

I'll second you. I full time admin our K8s infrastructure and clusters. It's a great solution for our production workloads and I've bootstrapped RancherOS/k3s a handful of times to look at using it at home but K8s is purpose built for cloud. I can get all the same benefits with significantly reduced complexity with Docker + Systemd at home.

Necrosoft.

Except we will never actually know...

73 DE WP3NIS

I went back and rewatched it. I completely forgot they forced it. I first saw this a couple months ago when our TC used it for extrication refresher. I have to admit, even though it is staged and the car is completely intact, watching those guys is money. Super smooth execution. The way he handled the halligan solo to create the frunk gap was pleasing to watch.

We don't. It's a cool video for a training night but really it's a pretty standard dash roll. Electric cars present a very real danger but so do ICE. High pressure fuel lines with pumps that don't shut down. Diesel engines which "runaway" with air intake leaks.

Every call is a special situation where you start with a baseline tactic and evolve the approach as needed. 20 minutes is overkill but the whole time we were watching it here we were discussing extrication in general. "Would you do this or that? What would you look for here? Did you see their step cribbing placement?" The Tesla responder guide is awesome and available online and is all you "need" to know where and what to cut. The video is more a conversation starter.

I'm not sure what ram speed has to do at all with extrication. The biggest problem area I see with the model 3 is the fact that a large portion of the high voltage carriers are centerline on the vehicle. In our department using the center post for dash lift/roll allows us to work both front seats without obstructing patient egress via the side/door. In the Model 3 you don't have the option to roll from the center.

I'm willing to bet my Hurst spreaders will get the frunk open sans battery. If you're cutting the car, it's already totaled and limiting damage to the frunk would be the last concern on my mind.

No. The internet is in a box and Jenn broke it.

In one, you intentionally give false information and lead the government believe you in good faith complied. In the other, the data is inaccessible and the government is aware it is inaccessible. They can then evaluate risk and seize the device or take some other action from that knowledge. IANAL and I don't play one on TV.

ETA: To complete the threat analysis, and if they seize two devices, one with a password protected key and a LUKS volume without headers? I'll take LUKS.

I took a workshop on custom Kali builds where they specifically spoke about LUKS headers and shipping them via email/gdrive to yourself and removing them from the physical device. It renders the partition useless. This was viewed as a better alternative than something like TrueCrypt with decoy passwords since if the government can ever prove you did it then that's obstruction. With the headers gone and no local copy you can't provide what you don't possess.

I agree. I've never been on a fireground and had someone yell, "We lost the house because you didn't divide by 12!" Fireground math is a very rough science. Every engine in our district has pre calculated charts for every cross lay and discharge so you aren't doing the math on scene. Additionally, once you deploy line you have a radio and can ask the engineer to increase or decrease pressure with no math required.

A much bigger issue is the lack of recruitment and volunteerism in the American fire service. People simultaneously don't want to increase property taxes to fund career departments and they also don't want to volunteer. Communities can't have it both ways. Lack of staffing is a far greater risk than whether I'm dividing by 10 or 12.