• youmaynotknow@lemmy.zip
    link
    fedilink
    arrow-up
    1
    ·
    12 hours ago

    Dude, you seem to be under the impression that I’m somehow defending meta, and you’re evidently in battle mode. I said my piece, provided the evidence as requested. I guess this is where I drop off of this convoy for ith you, buddy. Make of it what you will. Have a good day.

    • NewNewAugustEast@lemmy.zip
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      12 hours ago

      No, I am not in battle mode. I just read the link and found it interesting and responded with things I saw in it.

      What I didn’t do, was realize you sent TWO links, and I failed to read the second one. But believe me I am not trying to argue in any way. I am just responding.

      The second link was also just for backups.

      Again, I am just saying that they are not able to demonstrate that they are actually implementing this, AND that both of those links are for backups only. Thats all.

      And I totally get what you were driving at: it doesn’t matter, they have a “spare key”.

      • youmaynotknow@lemmy.zip
        link
        fedilink
        arrow-up
        1
        ·
        12 hours ago

        I don’t think it will. It’s just another outside audit (no idea if país by meta or not though). It is E2ee, that’s the bottom line. Now, the implementation is what dictates what that’s worth. It’s no different than client-side scanning or Microsoft co-pilot. What’s the point of having e2ee if someone else can get access either before encryption or by a third party, like meta, having a master key to decrypt anyway?

        The first thing was if there was any indo of e2ee being implemented, there’s plenty, even Cloudflare audited them at one point if I recall correctly. But, nobody knows how it’s implemented, except for meta, and that’s where the lack of trust resides, because we all trust meta as far as we can throw our cars.