Direct messages sent while offline aren't recieved by slack-libpurple

[aguenther]

It seems like slack-libpurple either isn't recieving notifications about offline messages, or isn't processing them.

When I - once per week or so - remember to open slack in the browser, it shows me various unread notifications of people who tried to contact me. Pidgin with slack-libpurple installed doesn't show any kind notification, and seems to be unable to fetch the missed text.

I just built the current master and tested it again. Can reproduce.

[dylex]

Are these IMs or group messages? Are they sent while you're connected or not?

[aguenther]

IMs, sent while I'm not connected.

[aguenther]

edit: just noticed that there is a MR open to fix this very thing already. I just built the plugin from his code for now...

[dylex]

Yeah -- the problem with the #58 approach is that it sends all the requests at once, which can make slack start denying requests, and eventually blacklist the client. I'm slowly working on a better solution on the lazy branch, but still trying to figure out the best way to deal with the unread counts. What I really want is to have them show up on the buddy list, rather than open all the windows. I think it should be pretty easy to just append an unread count label to the name in the buddy list (as long as the user hasn't set a custom alias), so I'm really tempted to do that. However, the community preference sounds like it is to open all the windows regardless, in which case these requests need to be thottled (serialized) somehow.

[aguenther]

IMO this sounds like a bad idea... My contact list is rather full, scrolling through it to see whenever someone wrote me might take a while..

I have to agree with the others, opening the windows (or displaying the notification, depending on the global Pidgin setting) would be better. It is supposed to actively notify you that someone tried to contact you, after all. Throttling requests sounds better here, from an end user's PoV at least.