We build Signal in the open, with publicly available source code for our applications and servers. To keep Signal a free global communication service without spam, we must depart from our totally-open posture and develop one piece of the server in private: a system for detecting and disrupting spam campaigns. Unlike encryption protocols, which are designed to be provably secure even if everyone knows how they work, spam detection is an ongoing chore for which there is no concrete resolution and for which transparency is a major disadvantage.

  • PandaCoderPL@lemmy.ml
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    3 years ago

    Signal is centralized and you can’t verify what is running on the server so does it really change anything? I think it doesn’t, so people should stop panicking and switch to some decentralized messengers like Session instead.

    • M500@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      3 years ago

      THIS! We have no way of knowing what they are actually doing on their servers so I don’t 100% trust them. Maybe like 90% trust. This really doesn’t change anything.

      • PandaCoderPL@lemmy.ml
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        3 years ago

        I don’t know where did you get that 90% from but IMO people shouldn’t trust them at all and should use decentralized platforms instead.

    • Echedenyan@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      3 years ago

      Try Status instead of Session.

      Fully FLOSS and their developers are not dicks who prioritize “muh dont want fixed notification” to digital rights.

      • PandaCoderPL@lemmy.ml
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        3 years ago

        Could you at least tell me any reasons why you wouldn’t use Session? Nobody will take you seriously if you have no arguments to back up your statement.