this post was submitted on 10 Feb 2026
1633 points (99.5% liked)

Technology

81026 readers
5214 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 news or articles.
  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, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  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
you are viewing a single comment's thread
view the rest of the comments
[–] bekopharm@discuss.tchncs.de 1 points 18 hours ago (1 children)

Feel free to share your sources.

The source is the technical spec. Read this yourself more closely!

Interoperability: The solution ensures seamless integration across diverse device operating systems, wallet applications, and online services.

And let's not ignore the demo part:

The white label solution will be implemented based on the open source EUDI Wallet Reference implementation libraries.

And yes it is good that people watch this carefully (and voice their concerns in a civil matter, which does not seem to be the case with most heated comments from your examples). But!

This is the very same with e.g. Let's Encrypt. Or a VPN 'service'. Or CloudFlare, that so many people love to hide behind.

What ifs. The spec does explicitly not allow exactly this and it's our job to investigate such providers closely and in doubt start and run trustworthy providers ourselves. And Let's Encrypt is again a prime example for something like this.

Oh and no nothing in the spec nails this down to Google or Apple alone. These are examples for smartphones for existing eco systems. I do not need a smartphone for e.g. AusweisApp and I will ask the same for E-Wallet because this is also in the specs (Interoperability) and explicitly not tied to some vendor specific eco system but to protocols and cyphers.

And this is where the next FUD may come in: TPM[1]. This does [also] exactly this: Device attestation and is a perfect candidate for regular PCs. That's probably just the next can of worms for you though and with this I'll end this discussion because even with plenty of What Ifs I do not see this solved from anyone in any better way - and again especially not from some company like Dis-fuckin-cord. This is exactly what a GOV exists for and they'd be sleeping on their job not providing digital ways for this very use-case.

[1] And just so that you may understand my POV on this: I demonstrated against TCPA back in the days. I can accept TPM tho. It's a rather useful compromise and something similar exists for most smartphone ALSO. That is a good thing because this is responsible for keeping e.g. password wallets private. Something the "oh noes, Windows requires TPM now" crowd never understood - and this is from a die hard Linux user for decades.

[–] ell1e@leminal.space 1 points 14 hours ago* (last edited 14 hours ago)

I disagree TPM is a good candidate.

And I think many of us reject the premise we should submit to any central id provider for half of the internet in the first place. There are less risky approaches: https://www.politico.com/news/2025/10/13/california-law-online-age-checks-00606115