

They are not referring to passkeys. They’re referring to deterministic algorithms for uniquely labeling a particular device or person, despite any privacy enhancing features that device or person employed. It can be as simple as sampling various hardware specs, hashing the result, and using that as an ID for the person. So, if you switch browsers, they know it’s still you. More complex techniques exist, obviously.





Yeah, I see what you’re saying. As far as I am aware, passkeys issue a one-time-token derived from a private key stored on the device. You can only access the private key via your devices own security (i.e., typically biometric). GitHub can only access the resulting one-time token, and it can verify that the token was derived from the private key using some cryptography. So, agreed. It’s not much different from a tracking perspective than just tracking password-based logins.
Though, I got the impression OP was talking about something else. Maybe I misunderstood them.