• 2 Posts
  • 203 Comments
Joined 2 years ago
cake
Cake day: April 27th, 2024

help-circle
  • It may be initially inconvenient, but you can choose a bank that offers 2FA/TAN beyond the smartphone app.

    Not sure what healthcare apps you mean. There’s lots of categories, so won’t comment without clarification.

    Same for employers tbh. Would love an example. (Besides: work apps can’t be forced on your private phone in most places.)

    I live in “modern society” and do own a smartphone, but I’m aware that it’s a convenience, not a necessity.


  • I have multiple young-ish (30s) friends that don’t own a phone (not just smartphone; any phone), and basically all people I know above 80 years don’t own one either.

    You can absolutely live a perfectly fine and good life without a smartphone. You’re just drawing the line where it’s convenient for you.

    Or let’s put it in more familiar words…

    [Owning a smartphone] is not “participating in society”, this is participating in, contributing to, and directly benefitting from the very thing they’re complaining about.









  • I think the text is somewhat dubious in its arguments, but this (and the arguments built on this assertion) is just plain wrong:

    [Signals servers have] a few important pieces of data;

    Message dates and times Message senders and recipients (via phone number identifiers)

    Signal clients implement the Pond protocol. As a result, Signals servers know who a message is for (obviously, how else do you get the message) but cannot know who it is FROM.

    I’ve been playing around with implementing a secure/private messenger demo for myself, and have been consistently impressed with how privacy preserving Signal is when reading their papers and code. I wish it was selfhostable, but apart from that, it’s great.

    The server would be NICE to be OSS, but ultimately, privacy breaches are prevented client/protocol side.


  • This doesn’t make a call to government servers.

    The app (or desktop application BTW, incl. Linux) reads your national ID’s NFC tag, once. When you need to prove your age, the app locally computes a zkp that only tells the site “at least 18yo yes/no”.

    Note that every EU country has a form of national ID, and the digital capabilities of these IDs are already used for a bunch of stuff (e.g. taxes, bank account creation,…). This doesn’t worsen the privacy situation for EU citizens, but instead ensures that no privacy-unfriendly solutions emerge.