You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While debugging the crash issue, I noticed that the purple-discord function discord_process_dispatch is not able to handle MESSAGE_ACK messages. I'm not sure about the appropriate response to them, if libpurple has some sort of API for marking messages as delivered, probably purple-discord should call that. Alternately MESSAGE_ACK messages could just be ignored.
PS: I noticed a number of issues in other projects relating to MESSAGE_ACK support, perhaps some of them will indicate the purpose of this message type.
While debugging the crash issue, I noticed that the purple-discord function
discord_process_dispatch
is not able to handleMESSAGE_ACK
messages. I'm not sure about the appropriate response to them, if libpurple has some sort of API for marking messages as delivered, probably purple-discord should call that. AlternatelyMESSAGE_ACK
messages could just be ignored.PS: I noticed a number of issues in other projects relating to
MESSAGE_ACK
support, perhaps some of them will indicate the purpose of this message type.Rapptz/discord.py#1851
discord-net/Discord.Net#84
terminal-discord/weechat-discord#29
Kiskae/DiscordKt#2
discordrb/discordrb#211
discord-jda/JDA#14
The text was updated successfully, but these errors were encountered: