• 2 Posts
  • 50 Comments
Joined 1 year ago
cake
Cake day: April 2nd, 2025

help-circle








  • So just to confirm the answer to my question question: Its pointless to use encrypted messaging on an Android device?

    Of course not. End-to-end encrypted messaging protects against eavesdroppers in transit. It’s an opaque envelope.

    (Edit: Keep in mind that Google is not the only potential eavesdropper out there.)

    What it cannot do is protect a message from someone reading over your shoulder when you write a message or open an envelope. On mainstream Android, that could be Google, if they choose to abuse their system-level access. On iOS, it could be Apple. And so on.

    Those companies might be eavesdropping on sent/received messages already, either at a large scale or in a minority of cases, or regionally, or they might not be doing it at all… yet. But they have the capability. You’ll have to decide for yourself whether that risk is acceptable.


  • Google has the capability to read everything that you can read on an Android phone, unless you have taken steps to remove all Google-controlled components that have system-level privileges. Last time I checked, this included Google Play Services, which are installed by default on most Android phones.

    Note that messengers with end-to-end encryption, like Signal, cannot protect against an adversary with full access to your device.

    This is part of why people de-Google their phones, which usually means replacing the entire OS with something like LineageOS or GrapheneOS.




  • who@feddit.orgtoPrivacy@lemmy.mlMost privacy respecting lemmy instance?
    link
    fedilink
    English
    arrow-up
    14
    ·
    edit-2
    8 months ago

    This is mostly true.

    However, it’s worth noting that your home instance is uniquely positioned: it can see not only everything you send out into the fediverse, but also everything you read or subscribe to, so its privacy practices can still matter.

    With that in mind, I suggest avoiding instances that run behind Cloudflare, which can see (and even change) every interaction you have with the instance.

    You might also want to disable off-site images in your web browser (if you use Lemmy’s web interface) and prefer an instance with a large image cache, because loading images that are hosted on other instances will leak your reading habits to those instances.







  • Even if you get past the loop, the fact that archive.is is now using third party CAPTCHAs means that their provider can track your interests: They can correlate the page you came from, the archived content you wanted, your browser fingerprint, your IP address if not using a VPN, etc. If it’s a big provider like CloudFlare or Google (spoiler: it is) they can also correlate all that with a significant chunk of your non-Lemmy web browsing.

    This is why I no longer use archive.is.