Tomer

But text messages are blocked correctly?

Regarding Edit 3, This sounds like the normal behavior because the extension shows "Read receipets were blokced" only when the device actually tries to send out a receipt, not immediately...

Okay, Nice catch. I added blocking of play receipts for voice messages in 0087a403d399bf976ffb8e8d28e4ad78efbc4cd7.

Oh, I'll try to see if there's a quick fix for it later, shouldn't be hard. At least for now you can just temporarily disable read receipts blocking, right?

Do you need it on Windows?

This is something that's now slightly better thanks to an algorithm in [FindValidationInfoForInterfaceName](https://github.com/tomer8007/chromium-ipc-sniffer/blob/54fb53e0cc185d7187c35650225563983f11fdd6/Chrome%20IPC%20Sniffer/Setup/MethodHashesExtractor.cs#L189). Still far from detecting all names.

I think this is a pretty low priority feature. I'd say we'll leave it for the client controller.

Did you try retrieving history?

You can request history using the `request_messaging_history` method, this is probably tha API you're looking for: https://github.com/tomer8007/kik-bot-api-unofficial/blob/1cc91cf3c83df247bd41908a7f4461e711744385/kik_unofficial/client.py#L390

Hmm, looks like a useful information. But what are those `PUT` requests? Are they HTTP requests? In general, how did you generate this data and what does it represent?