Libwa: WhatsApp C Library
github.com
github.com
Also, last time I was using it I needed to use a throwaway number as WhatsApp was detecting and banning anything that resembled a non-official client.
This may (finally) change with the Digital Markets Act [1][2] in Europe, but sounds too good to be true.
[1]: https://digital-markets-act.ec.europa.eu/index_en
[2]: https://techcrunch.com/2023/09/11/whatsapp-has-started-work-...
The previous version pretty much connected to your phone and proxied all send/receive message requests via your phone. The phone stored all the crypto keys etc for e2e.
The new version acts as a fully fledged client. All "1:1" chats are in fact group chats, containing multiple 'users' for all of your devices, and multiple users for all of the other persons devices. Cryptography is still e2e secure, but now there are n+m endpoints for all of your+their devices.
Therefore, I would expect major updates to be needed to this client to make it continue to work.
Wow, that’s a really interesting way to see it I hadn’t heard before. It works remarkably well, too.
Pessimistically any bit of code can scrape a present day service, is this easily maintanable, how often will it break, maybe permanently?
That said, fair play for sharing in the open, just querying the long term efficacy of using it.
Unless using an official API, things can be a bit brittle.
Perhaps there are implementation differences between this and the Go library underlying the Matrix bridge, but I don't think API incompatibilities should be a concern.
The only way to robustely deal with those "people" is to go thru extremely aggressive technical regulation: enforce a small and simple, but good enough, very stable in time network protocol support for the client.