this post was submitted on 25 Oct 2024
20 points (83.3% liked)
Privacy
31814 readers
247 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I used a setup like that, but there were 2 things that I didn't like
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.
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.
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.
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.
Read further into the thread.
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.
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.
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.