• haggyg@feddit.uk
    link
    fedilink
    arrow-up
    2
    ·
    2 months ago

    Didn’t have time yet to watch all of the video, but on my own GrapheneOS device, and assume especially useful on tablets, I have been using Molly for Signal messaging.

    Its cool because I can use an existing account (already attached to a phone number) so the device doesn’t require a SIM. The normal Signal app does not support this.

    Unfortunately at the moment I am having to use “Molly” not “Molly FOSS”, meaning I have some of the proprietary blobs in normal Signal app. It is currently too much hassle (for me) to setup notifications with the FOSS version.

    • Andromxda 🇺🇦🇵🇸🇹🇼@lemmy.dbzer0.comOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      I can use an existing account (already attached to a phone number) so the device doesn’t require a SIM

      The device never requires a SIM to actually use Signal/Molly, you only need to enter the verification code when signing up, it doesn’t matter on which device you receive the code.

      Unfortunately at the moment I am having to use “Molly” not “Molly FOSS”, meaning I have some of the proprietary blobs in normal Signal app. It is currently too much hassle (for me) to setup notifications with the FOSS version.

      It’s very easy, you don’t really have to set up anything, it just uses a little more battery life. If you already use multiple apps that support UnifiedPush, you can check out Molly-UP. It’s available in the Molly F-Droid repo, or you can just pull the apk from GitHub using Obtainium. You don’t have to self-host anything, there are public instances of both mollysocket (like molly.adminforge.de) and ntfy (like ntfy.rollenspiel.monster or ntfy.adminforge.de).