I personally don’t use it, but I often see people complaining that they cannot use it on their Linux phone and that might help.
I stumbled across a project which implements the client connection, like the app does, for WhatsApp: https://github.com/WhiskeySockets/Baileys
That would allow building a third-party WhatsApp client.
That should also be relatively simple to integrate into a Matrix bridge such as mautrix-whatsapp. Apparently it uses the same API as the app, but it authenticates as a web client. If someone were to implement the authentication of the app, people could start using WhatsApp without the app and also comfortably bridged to Matrix.
You can still link the bridge to the app currently, but the app needs to be online or the bridge will get disconnected after a few days. And if you don’t want to have a phone constantly running, you probably want a VM for the app and then that all gets fiddly.
Also, I recently found a blog post on how to build Matrix bridges, so that should be feasibe if anyone wants to implement that as part of the existing bridge: https://mau.fi/blog/megabridge-twilio/
I am pretty sure the existing mautrix-whatsapp bridge also uses the WhatsApp Web API, so there would be no difference.
It does not support the app’s authentication yet, so there would be a noticeable difference with that implemented.
Is Beeper’s WhatsApp bridge not open source?
It is, but you still need the app running somewhere.
Thank you so much for this post!
+1 for the mautrix bridge. The app only needs to be brought up once every 14 days after which you’ll get kicked
Yes, but even the app could be avoided altogether with the other authentication method implemented. :)
The dream!
Baileys also supports the native mobile API, which allows users to authenticate as a standalone WhatsApp client using their phone number.
does this mean we wouldn’t need an official client to connect to every 14 days?
