whatsapp-web-reveng VS Baileys

Whatsapp problem isn't in the algorithm, but their identity resolution (hence their roundabout way of doing their web client: https://github.com/sigalor/whatsapp-web-reveng)

iMessage approach is to treat every conversation as a group chat between all the recipient devices and all of yours. There's another risk here, that Apple doesn't let the end user verify the list of devices the chat is encrypted for.

Which is to say, a perfect E2E experience isn't trivial to design, but you don't have to drop the ball completely.

Yeah its encrypted, you have to reverse the web app, but people already done it and you can search for info like this github the code in js but I only look the readme and code it in python, right now im making a custom whatsapp web client that maybe I will upload to github

Si. L'algorithme utilisé par Whatsapp est le même que celui de Signal. La preuve : leur API a été reverse-engineeré, et des projets comme celui là https://github.com/sigalor/whatsapp-web-reveng le prouvent.

This uses Baileys [0] which appears to reverse-engineer the protocol Whatsapp uses for it's web app.

[0]: https://github.com/adiwajshing/Baileys

A better approach to this than simply scrolling through chats, is to directly use whatsapp web's api. Obviously writing this yourself takes a long time, so I tested this using this javascript whatsapp web api: https://github.com/adiwajshing/Baileys