Because Whatsapp crushes any client other than their official client. Everyone else is confined to scraping Whatsapp Web.
Matrix bridges are rather complex. They rely on a combination of private APIs (WhatsApp), Chrome extension scraping (LINE), bots (Telegram), mobile clients (Android SMS), and jailbroken iPhones (iMessage).
Given that puppeteering should be indistinguishable from real application usage and that $5/month/user should be more than enough to diversify IP addresses, I suspect the model can actually be sustainable in the long term.
* Encrypted with a private key which Google have access to.
I wonder if you can get them via one of those data access requests?
And on top of that Google or Apple or whoever you "trust" with your mobile operating system of choice.
Speaking of mobile OS, Element will likely run fine on mobile Linux whereas you can be sure Whatsapp will never release a Linux client
Element, on the other hand, is MITM by design.
Indeed then very weird why I should trust them more with my personal data than anybody else.
All bridges, and the matrix homeserver itself have been open source and self-hostable for years. I host a homeserver + some bridges myself.
This is just the sugar-coated SaaS for people who dont want to do it themselves.
It is! https://matrix.org/bridges/
I don't think I want to sacrifice the security for having all my chats in one place.
If they can fix that I might reconsider.
They already reverse engineered the Whatsapp protocol. I see little reason why it can't live in the client? I don't really follow why they move the bridge to the homeserver.