• foremanguy@lemmy.ml
    link
    fedilink
    arrow-up
    9
    ·
    6 months ago

    Signal is using Google Push messaging, but it could be used with websocket. And officially it’s not on fdroid because they don’t want forks of their app

    • toastal@lemmy.ml
      link
      fedilink
      arrow-up
      11
      ·
      6 months ago

      Yet the Molly fork supports UnifiedPush so I can reuse my connection with mf XMPP server to deliver notification from a server I control. Folks have asked for UnifiedPush or MQTT as an alternative to having multiple persistent socket connections open on your device, but Signal doesn’t seem to care.

      • Possibly linux
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 months ago

        How did you get Unified Push working? Last time I checked it required dedicated server side software

        • toastal@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          6 months ago

          You have to proxy their socket. It’s dumb, & Signal is bad. Using FSM is bad for privacy & limits to only Android/iOS primary devices is a slap-in-the-face for users wish to bleak out of the duopoly owned by two ad companies.

    • doodledup@lemmy.worldOP
      link
      fedilink
      arrow-up
      4
      ·
      edit-2
      6 months ago

      How would that prevent you from forking the app? F-droid isn’t a repository for the code of the app. I don’t think this is related at all.

      I don’t actually know the reason why it’s not on F-droid but I assume it has some historical reason. It has never been on F-drroid since Text-secure. Moxy Marlinspike was strictly against it afaik. If somebody has more detail on it, feel free to share it.