• poVoq@slrpnk.net
    link
    fedilink
    arrow-up
    13
    arrow-down
    1
    ·
    2 months ago

    This is false. There is still plenty of metadata that centralized providers can capture and turn over and that is usually sufficient for law-enforcement to get the information they want.

    • foremanguy@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      Right, WhatsApp is encrypted but not private at all. Reason? Metadatas, says as much as the message

    • Ulrich@feddit.org
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      7
      ·
      2 months ago

      This is false. They cannot turn over any type of data that is encrypted. Metadata or otherwise. That’s the point of encryption.

      • poVoq@slrpnk.net
        link
        fedilink
        arrow-up
        15
        arrow-down
        1
        ·
        edit-2
        2 months ago

        Except that most of the metadata isn’t encrypted anywhere and usually also can’t be encrypted as otherwise the service wouldn’t be able to function.

        • Ulrich@feddit.org
          link
          fedilink
          English
          arrow-up
          2
          arrow-down
          4
          ·
          2 months ago

          Plenty of services encrypt metadata. You need to do more research.

          • poVoq@slrpnk.net
            link
            fedilink
            arrow-up
            15
            ·
            2 months ago

            You seem to be highly misinformed what metadata is. A server for example will always have access to unencrypted IP addresses from the clients connecting to it, this is impossible to avoid unless you use a service like Tor that relays internet traffic, but that has very little to do with “encryption”.

            • Fushuan [he/him]@lemm.ee
              link
              fedilink
              English
              arrow-up
              1
              ·
              2 months ago

              Another thing a server can easily access is the timestamp of messages. Even if that is somehow stored encrypted in the server, messages are sent in real time and the server can easily log those, so an e2e encryption chat service will at the very least have logs with IP and timestamps. This can’t really be avoided.