🇨🇦
I really don’t like the idea of every device automatically having a publicly reachable IP.
There’s certainly situations where that would be nice; but I’m quite fond of most equipment and services being behind a router and it’s firewall, requiring explicit configuration to be exposed to the open net.
Nobody outside my home network ever needs access to my toaster… (btw, why tf is my toaster wifi enabled…?)
My ISP blocks the ports needed for mail hosting :/
Pretty sure I’d have to go through them to get the rdns PTR records pointed at my domain too. PITA
Actually it looks like Caddy is supposed to set those automatically (I’m used to Nginx which doesn’t).
You’ll have to look at why the upstream isn’t accepting them then. I’m not familiar with azuracast.
X-Forwarded-For
And
X-Real-IP
The application you’re proxying also has to listen to these headers. Some don’t, some need to be told they’re ok to use. (if you enable them, but don’t have a proxy in front, users can spoof their ip using them)
Rebooting just seems like a very roundabout, slow and inefficient way to get back to that initial state you describe.
It’s exactly what the reboot process is designed to do; return you to that fully encrypted pre-boot state. There would be no purpose to implementing a second method that does the exact same thing.
Much of the data on your phone, including critical information that’s required to run the operating system and make the device function, is fully encrypted when the device is off/rebooted.
While in this locked down state, nothing can run. You don’t receive notifications, applications can’t run in the background, even just accessing the device yourself is slow as you have to wait for the whole system to decrypt and start up.
When you unlock the device for the first time; much of that data is decrypted so that it can be used, and the keys required to unlock the rest of the data get stored in memory where they can be quickly accessed and used. This also makes the device more vulnerable to attacks.
There’s always a trade off between convenience and security. The more secure a system, the less convenient it is to use.
I WANT OFF MR BONES WILD RIDE
It would, but he explicitly says ‘without even a slight tap on the breaks’ in the youtube video.
Then:
Here is the raw footage of my Tesla going through the wall. Not sure why it disengages 17 frames before hitting the wall but my feet weren’t touching the brake or gas.
- Mark Rober
As much as I like Mark, He’s got some explaining to do.
At 15:42 the center console is shown, and autopilot is disengaged before impact. It was also engaged at 39mph during the youtube cut, and he struck the wall at 42mph. (ie the car accelerated into the wall)
Mark then posted the ‘raw footage’ on twitter. This also shows autopilot disengage before impact, but shows it was engaged at 42mph. This was a seprate take.
/edit;
Youtube, the first frames showing Autopilot being enabled: 39mph
Twitter, the first frames showing autopilot being enabled: 42mph
Oculus was dead to me the moment it was announced Facebook was purchasing them.
It’s google; their entire business is built on fucking you out of your personal data. Once they have it, they will never let go.
Until a highly scrutinized third party audit proves otherwise; I doubt even GDPR removal requests are complied with internally. They might stop telling you they have the data, but thetly won’t actually get rid of it.