They're locked in my an internal screw. So they'll at least last a few days.

Personally it feels weirder to have my address public today because it's too freely available across the world. Sure, someone back in the days of the yellow pages would still be able to get to me, but it would probably involve a bit more work of tracking what city I'm in then getting their hands on the book.

Now with it being digital it's too easy to casually find and abuse. The barrier to access is a lot lower.

Oddly enough, the information is just as available to businesses today yet it is less available to individuals. The digital databases have existed for decades. Certainly longer than the Internet as a publicly accessible network. Yet the phone books, that were accessible to anyone, no longer exist. (I also believe that cost of phone books were included in the price of telephone service, which meant that they were "free" for most households.)

(And, for the sake of accuracy, the yellow pages were a business directory that companies paid for higher profile ads. The white pages were the directory of individuals.)

Seems unlikely with how many different ways ui elements are handles across an OS (including apps that do their own rendering). Though I bet you could block some subset of well known ones and block a lot of the network traffic that feeds ads.

My favorite is "I'll log out the state of this object, it's all okay for privacy because I've checked every field and gotten the privacy reviews to prove it" then a few months later someone adds a new field to the object not realizing it's logged by a lower layer to a table no one remembers exists....

Then a month later someone queries that table and....oh shit.

Thats a good one. Seems like a scenario that is even more likely to happen because it would be much harder to find it in a code review than printf("user: %s, password: %s", userName, password) especially in a very large codebase. There is a lot less negligence required (though obviously not completely negligent free)

The fact that hearing impaired people prefer ASL interpreters to closed captioning tells me automated translation will never be enough.

It's the same reason we prefer interpreters to Google Translate when the message is important.

Interpretation adds the nuance of a human that all the automatic tools miss.

I'm sure it could make a small dent in the market for interpreters but only a small one.

I've never understood that outrage with one exception. Especially when you're remote it's painful to get immediately cut off from communication apps and not having a chance to say goodbye to people. When someone leaves willingly they get a chance to send one last email with a personal contact method for people to keep in touch. If you're let go you don't get that chance.

I wish there was a way to remove access to everything except that, but sadly I can't think of anything foolproof.

For typefaces you check for the distribution of similarities in each group. If it has large clusters then group by 3, 3', etc then run your outlier check on each of those groups

Still would risk some weirdness, but would help a bit I'd hope.

I wonder if it would be worth running some kind of language analysis or spelling/Grammer check to verify the scan too. At least for text, you'd need another solution for number tables.

By that logic you could in theory use a VOIP number to call...

Glider on Android handles this correctly

The failure here is on the manager/ops team for not seeing the critical project running on the hack instance and providing resources to stabilize it.

Hack instances are amazing for getting stuff off the ground or validating a use case when the proper channels are too burdensome to use, but they need to be migrated away from once something is critical.