this post was submitted on 25 Jan 2025
187 points (96.5% liked)

Technology

61203 readers
5621 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
 

cross-posted from: https://lemm.ee/post/53562405

you are viewing a single comment's thread
view the rest of the comments
[–] goatmeal@midwest.social 1 points 4 days ago

Assuming the company running the service and doing the verification is acting in good faith (big leap here, I get it) couldn’t you verify an identity, store a piece of static information about that person (DL, SSN even tho that sucks) in a hash so that no one else could use that identity to create an account and then issue an account ID with no link to identity marker?

This would allow you to verify users, prevent people from using an ID that was already used, prevent you from being able to link an account to an identity, and prevent you from being able to easily return a list of everyone identified on the service. Best you could do is respond to an individual query on whether that person has verified with your service.

I think it could work technically, but I agree that in practice the US would use its power to make you conduct surveillance without alerting customers, or maybe enact some KYC type requirements for internet usage. This would likely be a first or skipped step on the way to that.