1. 14

…is available in the Copperhead F-Droid repository.

  1.  

  2. 3

    I wonder why strcat decided to name it this. It’s has a lot of name collisions, in fact the Noise Protocol which ironically is similar to the Double Ratchet (Signal) Protocol.

    1. 2

      I think its a pun on ‘signal to noise ratio’? Shame about the collisions though.

    2. 2

      I have a feeling this will go down the way LibreSignal did: https://quitter.se/notice/7959855

      1. 3

        I can see why you would feel that way if your characterisation of what happened is based on a straw man posted to a twitter clone.

        There’s some key differences, such as this isn’t using the Signal trademark, and with any luck the patch this uses will get merged upstream anyway, but only because someone not even involved with LibreSignal finally started writing the patch Moxie asked for 2 years ago (that tweet/“queet” left that bit out, did they run out of characters?)

        1. 3

          I can see why you would feel that way if your characterisation of what happened is based on a straw man posted to a twitter clone.

          It’s a simplification of what actually happened. The fact that it’s a twitter clone doesn’t seem related at all to any of this, though.

          Moxie rejected LibreSignal’s solution because he claimed websockets used up more battery than GCM. In the post, Copperhead mentions that Noise “isn’t optimized for low impact on battery life like Conversations”, which might mean it also doesn’t reach Moxie’s standards.

          Which is absurd because a hard dependency on a monopoly’s proprietary program should’ve never been considered for an app aiming security.

          1. 9

            HN thread for additional context

            To clarify this for casual readers, no data at all is transmitted over GCM. GCM is only used as a push event to tell the Signal Android client to wake up and connect to the Signal server to retrieve messages from the queue if the app isn’t in the foreground.

            This is pretty fundamentally just how Android works. However, people who want to use Google’s OS without any Google services flash custom ROMs onto their devices that are missing this dependency.

            I have said many times that I have no problem with supporting these custom ROMs. But I would like someone from that community to submit the PR: “I would consider a clean, well written, and well tested PR for websocket-only support in Signal. I expect it to have high battery consumption and an unreliable user experience, but would be fine with it if it comes with a warning and only runs in the absence of play services.”

            Nobody has done it.

            1. 6

              He has specifically said he expects websocket-only support to have higher battery consumption and that’s fine:

              “I would consider a clean, well written, and well tested PR for websocket-only support in Signal. I expect it to have high battery consumption and an unreliable user experience, but would be fine with it if it comes with a warning and only runs in the absence of play services.”