Ideally this should have been hashed out before deploying passkeys everywhere, but I guess you can always register multiple passkeys for the sites that allow you to.
Iirc the original idea was that passkeys should be device specific. Of course that's impractical so now they're morphing to a long password that a human can't process.
In a few years someone will post "how about a long human retainable passphrase?" as a new and improved discovery.
They are still different to a password in that the service you are logging in to never gets the private key. So in the case the database gets compromised, if the service provider ensures no edits were made / restores a backup, there is no need to change your passkey since it was never exposed.
So much spam would go away if we just charged $1 per 5000 emails. Normal humans would be fine. Mailing lists would need charge, but it would be minimal for most useful mailing lists.
I'm not sure I agree with Karpathy's "the next wave of programming languages will be natural language", but I'm even more concerned about The Big 3 consulting firms message of how businesses _must_ integrate AI into _everything_ or perish.
My former FAANG uses internships at the Ph.D. level for both recruiting and talent acquisition. Hiring committees have a way easier time assessing candidates with feedback like "this intern implemented X, Y, and Z beyond their project spec W during the summer" or "this intern goofed off all summer."
The situation is not as dire as it first appeared. While the messaging wasn't handled very well, where everything is settling out is good, with pluggable auth and an open source reference implementation: https://lakefs.io/blog/why-moving-acls-out-of-core-lakefs/
reply