hoehermann / purple-gowhatsapp

Pidgin/libpurple plug-in for WhatsApp Web.
GNU General Public License v3.0
283 stars 35 forks source link

Order of pervious message is as received and not by timestamp #51

Closed nihilus closed 2 years ago

nihilus commented 4 years ago

As one can easily see the order is not in order (pun intended):

(2020-05-02 14:53:31) XXX: läser mkt samtidigt, så jag vet vad ska jag skriva
(2020-05-02 16:17:48) XXX: Fan vad jag vill röka
(2020-05-02 14:53:13) Markus: Tur att du har hela helgen på dig
(2020-05-02 14:53:36) Markus: Mmm
nihilus commented 4 years ago

Also my latest message from the phone-app is not showed. I will try figuring out an easy fix for this.

nihilus commented 4 years ago

@EionRobb flags |= PURPLE_MESSAGE_SEND | PURPLE_MESSAGE_REMOTE_SEND | PURPLE_MESSAGE_DELAYED; Why does it have to be marked as 'delayed'?

nihilus commented 4 years ago

Seems related to issue #32

hoehermann commented 4 years ago

I know. After connecting, the server sends a burst of messages in random order. I'd need to collect them, sort them, and then display them. Problem is: I do not know when the burst is over. It seems to depend on internet connectivity, service quality, size of attachments, and the current phase of the moon. I described the problem in another issue, but I cannot find my original comment right now. I have no idea how to really solve this problem. It does not bother me enough to implement a fix which is only half-good.

EionRobb commented 4 years ago

@EionRobb flags |= PURPLE_MESSAGE_SEND | PURPLE_MESSAGE_REMOTE_SEND | PURPLE_MESSAGE_DELAYED; Why does it have to be marked as 'delayed'?

"send" is for pidgin, "remote send" is for bitlbee and spectrum2, "delayed" is for Adium

hoehermann commented 2 years ago

This does not happen with the whatsmeow branch.