this post was submitted on 08 Mar 2026
368 points (99.5% liked)
Technology
82460 readers
4523 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I mean, yes, it's the same process. It's just moving the convenience store to your phone, and instead of being issued a physical ID by the dmv or whoever, you're given a digital one. To be clear, that ID, and therefore your information is stored locally on your device, not in a server somewhere.
While I would trust that for a FOSS app, it would be too easy for a proprietary app to just “backup” your data.
With the physical method, everyone can be sure they are anonymous through common sense.
Sure, but I have 2 counterpoints:
There's no reason the 3rd party app needs to be proprietary. This is starting to get technical, but my understanding is that you get a cert from the requester, and it's the combination of that with the state issued magic cert that's used for validation. The 3rd party app is essentially just a calculator. It doesn't need any certs of its own
That's an implementation detail. My argument is that it's the implementation that's the real cause for concern here, not the idea