MAX no more allows logging in with a phone number from the web app, nor allows specifying a deviceType other than WEB when connecting over WS API.
Native apps (desktop, Android, iOS) use a custom binary protocol instead of WebSockets to communicate with the OneMe backend.
For a short description, see this thread in Russian: https://gts.dc09.xyz/@darkcat09/statuses/01KGWMHJ346266GXKQEE0E8GX5
I wonder if we should implement the protocol, and if yes, whether to drop websocket support or not. After i figured out payload is LZ4-compressed (thanks to pymax library!!), everything is clear to me now, so i think i can start writing a client
MAX no more allows logging in with a phone number from the web app, nor allows specifying a deviceType other than
WEBwhen connecting over WS API.Native apps (desktop, Android, iOS) use a custom binary protocol instead of WebSockets to communicate with the OneMe backend.
For a short description, see this thread in Russian: https://gts.dc09.xyz/@darkcat09/statuses/01KGWMHJ346266GXKQEE0E8GX5
I wonder if we should implement the protocol, and if yes, whether to drop websocket support or not. After i figured out payload is LZ4-compressed (thanks to pymax library!!), everything is clear to me now, so i think i can start writing a client