I have to use Whatsapp, unfortunately. Are there any good alternatives to the default app on Android?

I’m worried about all the data it shares with Meta. I denied all permissions but this makes it less convenient, and the app probably still sends over the data that available without them.

  • MentalEdge
    link
    fedilink
    1
    edit-2
    29 days ago

    When was this?

    I’ve been using WA through a matrix bridge over a year, and I don’t think I’ve opened the WA app since setting it up. I do have to keep it installed, and allow it to run in the background.

    It, or my matrix app, doesn’t seem to significantly drain my battery more than normal.

    Is the once every two weeks thing an old requirement? I’ve never needed to deal with something like that.

    • Rolling ResistanceOP
      link
      129 days ago

      This summer? I disabled the WA app on my phone, though, so there was no background activity.

      My matrix app (an Element fork) had several bridges and multiple chats, I feel like they were all synching in the background. I haven’t noticed that when I was at home, but when I was camping, battery going from 100% in the evening down to 70% in the morning was a problem.

      • MentalEdge
        link
        fedilink
        1
        edit-2
        29 days ago

        How did that even work at all? All activity goes THROUGH the WA app. WhatsApp only allows one real client to be connected, all other clients (other devices with the app linked to the first device, bridges, whatsapp web sessions, etc. they all still go through your “main device”). If you turn your “main” phone with the whatsapp app off, for example, all others stop working.

        Looking it up, the bridge connection expires without activity at least every fourteen days to keep your account active in general. As long as you allow the app to run (which it has to do anyway, because that’s how WA works) it’ll do that on it’s own I think, no need to open it every fourteen days. Or at least, I’ve never had to. My bridge connection is literally over a year old, and I’ve definitely gone months without opening the actual WA app in that time.

        I run my own instance and bridges.

        I use fluffychat on mobile. Though I also have element installed as fluffy doesn’t support all message types, and has some bugs despite the nicer (imo) UI.

        As for the battery drain of element, that’s something you’ll have to look into yourself. One of my own qualms with matrix atm is that there’s no really excellent mobile client for it… It’s all kinda meh. There’s element which is feature complete but has a bunch of issues, or there’s stuff like fluffy, which is nicer, but not feature complete, and still has issues.

        • oranki
          link
          fedilink
          229 days ago

          The official app doesn’t need to be running constantly. It only needs to connect to Meta’s servers once every 14 days.

          The Mautrix-Whatsapp bridge will send a notification couple of days in advance to warn you if the main device hasn’t been active.

        • Rolling ResistanceOP
          link
          129 days ago

          Look up “Beeper”. It’s not about privacy, rather about convenience. They run bridges for you. Nothing went through the main app, but I had to authorize Beeper through WA as a separate session. It would die in 2 weeks with WA disabled, like I said, but I guess if I kept WA enabled this wouldn’t have happened.

          • MentalEdge
            link
            fedilink
            2
            edit-2
            29 days ago

            You are mistaken.

            I know it’s about convenience. That still isn’t how whatsapp works.

            Using WA you cannot be logged in on more than one device. If you do log in for real, the previous device stops working. All additional devices have to be linked to the first one, and they access the service through that one main device.

            You can’t use secondary “linked” devices or sessions if the main device is off. Try it. Open whatsapp web, login, then turn off your phone. The web session will stop working until you turn the phone back on, because it doesn’t actually connect to WA, it connects to your phone. Only your phone is what is actually connected to WA servers.

            All “linked” devices/clients/bridges work this way. All available whatsapp bridge software works by pretending to be an additional “device”, and as such suffers all the same limitations.

            And Beeber doesn’t do anything special, their systems are based on matrix. In fact I’m literally running the exact same bridge software they do.

            Edit: Something has changed. This used to be true. Somewhere along the years WA has significantly changed how their systems work. I can only assume they buffer activity for 14 days and somehow defer the synchronization of content with the main client, because all the same limitations of devices being subordinate to a main session apply.

            The most mind-boggling is the alteration that multiple client devices are now allowed, but also not really.

            And they still require that user history be monolithically stored by the user, on their MOBILE device. And the only way to have a backup is through their backup solution, and god-forbid you press the wrong button when setting up a new device, because not restoring when the one chance is given, means everything is gone forever.

            The main reason I use whatsapp via a bridge, is to have my message history stored on a proper server, so I don’t have to do the restore backup BS whenever I switch devices. I just re-link the bridge and go.

            • Rolling ResistanceOP
              link
              129 days ago

              This is a good little story, I enjoyed reading it :)

              Yes, having message history and a good desktop client are great benefits of a bridge.