4 ms·
It looks like you're using base64 encoding. If WhatsApp allows an extended alphabet then you might be able to switch to base85 for a slight performance bump.
by gnfargbl 4y ago
It looks like you're using base64 encoding. If WhatsApp allows an extended alphabet then you might be able to switch to base85 for a slight performance bump.
- kevincox 4y agoSince WhatsApp is end-to-end encrypted you can probably just send bibary data. Stick a prefix on it so that the real client is guaranteed to ignore it as corrupted. I think the only risk is that if you have a real client running it reports the invalid messages and WhatsApp uses this as a signal to van your account.
- staindk 4y agoNote AFAIK WA is e2e encrypted BUT they can flag any weird looking messages (weird patterns etc) to see and review their contents. So I think Meta/WA can opt to decrypt any suspicious messages they come across.
- preisschild 4y agoMeta/Facebook is the last company I would trust regarding their E2EE. They probably have a key themselves.
- orestarod 4y agoThe E2EE here is not about privacy, but about being able to send whatever data you want (like binary) since WhatsApp will only see one type of data (encrypted) in transit, in contrast to needing to send data in a specific format to have it transferred at all. Meta can peek at the original "messages" all they want, they will see encrypted packet data anyway.