> I'm surprised there aren't trackers on all cars already, like a 21st century license plate.
Are you referring to a state or government tracker on every vehicle? If so, it seems like you're implying that's a good idea. If that's the case, I hope there's some joke in here I'm missing.
Found this while scouring this list of HTTP status codes, because I wanted to make sure I was giving appropriate responses in this web API I'm developing.
Getting the probe out there is no doubt indeed remarkable in its own right, but to build it resilient enough to remain communicative at this distance, after all this time in such hostile environment, along with the foresight that enables these lifetime measures to be taken almost a half century later, makes it all more remarkable, and to think all this accrued knowledge and ingenuity being generalized from things like chipping flint axes.
At my company (not finance, and never gotten sued), documents are ephemeral
primarily due to GDPR reasons.
Many of them contain various personal data of clients and/or employees, legal makes us specify for how long each service needs to hold on to it, and purge as soon as possible to minimize chance of leaks.
Is there any infrastructure out there to limit or securely monitor what apps or features are enabled on company/institution mobile devices? Or are we for the most part in a "we expect you not to do this or that" era?
I used to work for a small institution a while back (not USA), they used a Word file of approved apps, authored by a non-IT employee. Their whole idea of InfoSec was equivalent to taping a water balloon to a steering wheel and calling it an airbag. Can't imagine the situation is much better in most other places. Scary really.
What type of file was the export? Did it include one or multiple tables of data? What tools did you use to analyze it? Just asking out of random curiosity.