tweb VS whatsapp-web-reveng

https://web.telegram.org/k/

the writers are mathematicians I guess, russian minimalists... I remember I checked their site and it did not seem to use bloated stuff

compiled native UX code may be less kb than minimized js but actually I have never seen comparisons and I do not know much about UX programming in java, c++, android-java or swift or the like

however, a website can dynamically load (can, 99% do not make use of it) just in time what you need (or as a compromose, preload the next possible steps)... UX code, app code anything

you can make the client download always the very necessary code on its user journey... even UX code, app code...

what I find better in native is the built in bot protection :)

Today tried to login into Telegram. Gone at https://web.telegram.org/k/, entered my phone number, clicked "next" and... It's hanging with "please wait...".

Head over to https://web.telegram.org/k/ and log in with your smartphone. Use the search bar to search for “BotFather”.

For some reason not all sites are shown in cookies list (e.g. web.telegram.org/k, 4channel.org/sp/) is there any other way I can clean cookies of those sites?

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.