zlacker

Really pleasantly surprised at how progressive this memo is. It will be interesting to see the timelines put in place to make the transition.

Btw - I'd love to see the people who put this memo together re-evaluate the ID.me system they're implementing for citizens given how poor the identity verification is.

>>tims33+(OP)
I have an issue with using ID.me for government websites, because it is a privately owned company. Online authentication at this point seems as important as USPS service and warrants being owned and developed by the government itself.

>>YeBanK+AX
They even HAVE this already, at https://login.gov/ !

>>dmd+7p1
I have a login.gov account. Needless to say I'm not a US citizen, and the IRS should not cut me a refund check.

ID.me supports WebAuthn (or maybe U2F? In this context it doesn't matter) but importantly it does identity verification so it can determine whether I am a US citizen, whether I'm a tax payer, and if so which one.

Now, perhaps the US Federal Government should own the capability to do that instead of a private company. But, so far as I can tell, they do not and login.gov is not such a thing.

>>tialar+xt1
A private company shouldn’t own this capability. Especially as ID.me CEO lied about maintaining a database of every face “1-to-many” that uses their verification system. They’re right up there with Clearview AI.

https://www.theverge.com/2022/1/26/22903437/id-me-facial-rec...

>>tialar+xt1
Login.gov does support identity verification. Not all uses of Login.gov require it, so many accounts are just used for email with MFA.

>>tialar+xt1
Login.gov supports identity proofing. It’s part of the flow when signing up for a Social Security account using Login.gov at ssa.gov (Login.gov recently became their primary identity provider a few months back).

Login.gov also supports WebAuthn.

>>konklo+JI1
I thought I'd find you in here! Wishing you well friend.

-Mario