|
> On a related note, they built their digital ID so that third parties could verify attributes Isn’t that the entire point of government ID of any variety? The only reason anyone ever asks to see ID is so they can use it verify attributes of your identity, such as name and age. Otherwise what’s the point of an Identity Document, if it’s not to document something? Digital ID has always been sold as something approximating your passport/Driver License (there is no official government ID in the UK), but digital, on your phone, and actually a government identity document. Rather than a government document that has a specific purpose (such as crossing the border or driving a car), which people pretend is government ID. Something that can cause a serious problem for people because passports and driver’s licenses aren’t free to obtain, replace or keep valid. Plus the government departments that issue them refuse to take any responsibility or liability for the accuracy or validity of the documents for any use case outside their very specific role in narrow government functions, like crossing the border, or figuring out if you’re allowed to drive a car. The UK already has citizen SSO that stretches across all digital government services, and has had that for a decade plus now. Although it’s not really attached your identity, it’s just a unified auth system so government departments don’t end up creating their own broken auth systems instead. |
Ideally this could be done without deanonymizing accounts to service providers unless the user wants to for a 'verified' account linked to their identity publically but I don't think any digital ID system has been built that way. Imagine it acting like OAuth but instead of passing back an identity token it's just verification of age, platforms would store that which would show they had performed the age verification and could be used for other age gates if there are any.