• rdri@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    6 months ago

    not encrypted by default

    Not e2e encrypted ≠ not encrypted.

    its closed

    Client is open source and you can use your own client with custom functionality if you like. I imagine nothing stops anyone from implementing their own e2e implementations on top of it.

    • Brayd@discuss.tchncs.de
      link
      fedilink
      arrow-up
      0
      ·
      6 months ago

      SSL on websites also is encryption. Still you can post your precious pictures “encrypted” via SSL for the whole world to see. I think everyone knew what was meant with encryption in this context.

      • rdri@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        6 months ago

        I think everyone knew what was meant with encryption in this context.

        I think not.

    • umbrella@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      6 months ago

      i know but neither encryption, nor foss clients matter much if it has to go through a closed server. thats kind of half the point of encrypting stuff. at least telegram supports it but cmon.

      its like saying facebook is private because your browser is foss and you use https.

      • rdri@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        6 months ago

        Anything goes through closed servers. Even more, serverless chat protocols tend to go through multiple users PCs (they are not open to you).

        point of encrypting stuff. at least telegram supports it

        I’m pretty sure telegram doesn’t support plaintext transfers.

        its like saying facebook is private

        I didn’t call telegram private.