• Possibly linux@lemmy.zip
    link
    fedilink
    English
    arrow-up
    7
    arrow-down
    10
    ·
    2 months ago

    Do you hate Signal or do you hate the west? There legitimate reasons to not like Signal but calling them hostile toward third party clients is untrue. Last time I checked Signal wasn’t proprietary.

    • jet@hackertalks.com
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      3
      ·
      2 months ago

      They have demonstrated history of asking third party clients to not use the signal name, and not use the signal network. The client that currently exists that do this do it against the wishes of the signal foundation

      • ᗪᗩᗰᑎ@lemmy.ml
        link
        fedilink
        arrow-up
        13
        arrow-down
        2
        ·
        2 months ago

        They have demonstrated history of asking third party clients to not use the signal name, and not use the signal network.

        The lead developer, nearly 10 years ago now, specifically asked LibreSignal to stop. A single event does not make a demonstrated history.

        The client that currently exists that do this do it against the wishes of the signal foundation

        If you have evidence to back this claim, I would like to see it so I can stop spreading misinformation.

        • jet@hackertalks.com
          link
          fedilink
          English
          arrow-up
          4
          arrow-down
          3
          ·
          edit-2
          2 months ago

          In the Libra signal issue that you linked to, they made it clear they don’t want third-party clients talking to signal servers

          • ᗪᗩᗰᑎ@lemmy.ml
            link
            fedilink
            arrow-up
            6
            arrow-down
            1
            ·
            2 months ago

            He was specifically talking to that developer. The “You” and “You’re” in that quote was specifically targeted at the LibreSignal developer.

            I recall the gurk-rs developer specifically mentioned that his client reports to Signal’s servers as a non-official app. The Signal admins can see the client name and version - just like websites can tell what browser you’re using - and could easily block third party clients if they wanted to but they don’t.

            If Signal wanted to block third party clients, they would have blocked them already.

            • jet@hackertalks.com
              link
              fedilink
              English
              arrow-up
              5
              arrow-down
              2
              ·
              2 months ago

              Moxie made it incredibly clear, he does not want third party is talking to the signal servers.

              Libra signal took him at his word and turn themselves off

              The other developers, like Molly, take a stronger road.

              Is signal currently banning third party clients? No. But they’ve made it clear they don’t like them. They didn’t actually ban Libra signal, they just asked them to stop. Could they ban the clients in the future? Yes

              • ᗪᗩᗰᑎ@lemmy.ml
                link
                fedilink
                arrow-up
                5
                arrow-down
                1
                ·
                2 months ago

                I’ll reiterate my statement as you didn’t address it.

                If Signal wanted to block third party clients, they would have blocked them already.

                • jet@hackertalks.com
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  ·
                  2 months ago

                  I respectfully disagree. They could be waiting until it becomes a big issue. Right now that would just cost them good PR, but if somebody was using the signal network and their client became very popular they absolutely have expressed the desire, intent, and as you indicated the capability to do so.

                  • ᗪᗩᗰᑎ@lemmy.ml
                    link
                    fedilink
                    arrow-up
                    2
                    arrow-down
                    1
                    ·
                    2 months ago

                    They could be waiting until it becomes a big issue

                    I guess I don’t see that as a problem if its causing a big issue.

                    Let me throw it back to you: If you were providing a service and a third party client was using your resources and causing a “big issue” like you stated, would you not want to remediate the problem? Lets say you introduced a new feature, but it doesn’t work for 15% of your user base because they’re using an outdated third party client that may not get fixed for another year or two - if ever. What would you do?

                    Here’s another example, lets say someone develops a client that lets you upload significantly bigger files and has an aggressive retry rate that as more people start using your client, it starts increasing the hardware requirements for your infrastructure. Do you just say “oh well”, suck it up and deal with having to stand up more infrastructure due to the third party client doing things you didn’t expect? Is that reasonable?

              • istanbullu@lemmy.ml
                link
                fedilink
                arrow-up
                4
                arrow-down
                3
                ·
                2 months ago

                If you have a backdoored client, then you would naturally object to third party clients :)