-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check if read receipts could be sent other than immediately upon receiving the message #22
Comments
This is one of the "highly optional" features, since (as far as I know) libpurple does not provide any interface to tell your prpl when the user actually reads something. |
So we did check it and the answer is no :) |
Well, just because I don't know of a way it doesn't mean there definitely aren't any :P |
purple_conversation_has_focus |
Otherwise I love this plugin, but unfortunately, this is a showstopper for me. Having pidgin with tdlib-purple is not only instantly marking all messages sent to me as read, but also by doing that, it prevents notifications on all my other devices, so i dont know if and when someone texts me anymore. |
Made version 0.7.5 which, when used with pidgin, is supposed to mark messages as viewed only when conversation window has focus, and then only for conversation tab that has focus. With used with bitlbee or spectrum, there is account option "read-receipts" to disable marking any messages as viewed. Let me know if anything is still wrong. |
Also love the plugin a lot. Would like to have mark as read when actually accessing the the conversation under bitlbee otherwise it is quite unusable when I let it running under screen session. |
I assume that's not possible because bitlbee doesn't seem to notify the plugin when you access a conversation? But there exists account option "read-receipts" to disable them completely. |
It's probably done as best I could |
This does NOT work correctly still: 1) the default value is still TRUE, this is wrong, should be FALSE, and the plugin should NEVER mark as read what is not read yet. 2) this forces to disable read-receipts for spectrum and in this case PURPLE_CONV_UPDATE_UNSEEN signals are ignored, so it is not possible to mark as read from spectrum which is able to mark as read when it is actually read. |
No description provided.
The text was updated successfully, but these errors were encountered: