kngspook

My understand is the people behind passkeys are working on an import/export solution. Who knows when it'll happen though.

For now, when companies let me have multiple passkeys, that's sufficient for me. I put one on my Apple Keychain and one in 1Password.

Yeah, I hate these. It's also a very not-ergonomic was to sign in. I wish those companies would redirect those efforts to passkeys.

Does the hash end in ...e63f2 perchance, or is it a different dump?

I feel like someone should spin up a separate GCP account, make a pile of projects, and then spam-add every google engineer they can find. Curious to see what happens next…

Google Takeout is actually reasonably robust. I create/download one of those fairly regularly.

For me, a big part of the value of typehints isn’t just the legibility, it’s also helping the interpreter to help me. I can have the interpreter tell me that a string got passed into a function instead of the list of strings that I was expecting, or I can have have my code output a single letter instead of a whole word from the array access call in my code.

I’ll figure out the bug eventually either way, but having the compiler give me the clearer warning earlier in the development process (sometimes even from pure static analysis) is a significantly more pleasurable development experience and a potential time saver

And 50X that, especially the time saved, if I’m integrating with code you didn’t author.

Gmail I believe is technically encrypted at rest, just they also happen to have the keys.

I mean, it was Bing not too long ago...

Google (or any company) wouldn't have a single point of failure for alerts like that. :P Those alerts would hit email, phone, etc. all at the same time.

No, Facebook/Google internal apps fall into two categories:

- Utilities that are only useful to employees of those companies (cafeteria menus, shuttle schedules, resources for salespeople on the go, etc.).

- Pre-release/testing (aka dogfood) versions of the apps they distribute to the public, for employees to use and find bugs on before they make it out to normal users.

Neither of those are pools that Apple wants to play in.

...and I guess there's a third category:

- Apps used gain "competitive intelligence" and spy on users.

I don't think it's about remind them who's boss. Apple will revoke the certs for as long as is necessary to protect their users, but I don't think they'll stay revoked for punitive purposes. I expect it'll be a period measured in double-digit hours, not weeks.

> The whole point of enterprise certificates was to allow creation of internal apps that even Apple shouldn't know about.

I think most/all of the companies in the program would say it's about controlling the distribution of their apps, since putting them on the App Store would expose them to the public, and less about hiding from Apple...