-
-
Notifications
You must be signed in to change notification settings - Fork 418
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
Response to specific message #88
Comments
( |
In this change we are updating whatsapp message IDs to include sender JID as this is necessary to reply to a message tulir/whatsmeow#88 (comment) tulir/whatsmeow#148 (comment) Based on commit 6afa93e from 42wim#1934 Author: Iiro Laiho <iiro.laiho@iki.fi>
In this change we are updating whatsapp message IDs to include sender JID as this is necessary to reply to a message tulir/whatsmeow#88 (comment) tulir/whatsmeow#148 (comment) Based on commit 6afa93e from 42wim#1934 Author: Iiro Laiho <iiro.laiho@iki.fi>
In this change we are updating whatsapp message IDs to include sender JID as this is necessary to reply to a message tulir/whatsmeow#88 (comment) tulir/whatsmeow#148 (comment) Based on commit 6afa93e from 42wim#1934 Author: Iiro Laiho <iiro.laiho@iki.fi>
In this change we are updating whatsapp message IDs to include sender JID as this is necessary to reply to a message tulir/whatsmeow#88 (comment) tulir/whatsmeow#148 (comment) Based on commit 6afa93e from 42wim#1934 Author: Iiro Laiho <iiro.laiho@iki.fi>
* Handle Whatsapp threading/replies. In this change we are updating whatsapp message IDs to include sender JID as this is necessary to reply to a message tulir/whatsmeow#88 (comment) tulir/whatsmeow#148 (comment) Based on commit 6afa93e from #1934 Author: Iiro Laiho <iiro.laiho@iki.fi> * Fix replies. Sender JID can have a `:` inside of it, using `/` as a delimiter now. Added messageID parser + struct. messages sent with an attachment do not show replies But at least common `sendMessage` will make repies from whatsapp to an attachement bridge across. The new message ID format broke message deleting, so we change the messageID into the real id at the beginning of send. We really do need the extra info for when we reply to a message though. * Refactored message replies. file/Image/audio/replies all work now.
* Handle Whatsapp threading/replies. In this change we are updating whatsapp message IDs to include sender JID as this is necessary to reply to a message tulir/whatsmeow#88 (comment) tulir/whatsmeow#148 (comment) Based on commit 6afa93e from 42wim#1934 Author: Iiro Laiho <iiro.laiho@iki.fi> * Fix replies. Sender JID can have a `:` inside of it, using `/` as a delimiter now. Added messageID parser + struct. messages sent with an attachment do not show replies But at least common `sendMessage` will make repies from whatsapp to an attachement bridge across. The new message ID format broke message deleting, so we change the messageID into the real id at the beginning of send. We really do need the extra info for when we reply to a message though. * Refactored message replies. file/Image/audio/replies all work now.
* Handle Whatsapp threading/replies. In this change we are updating whatsapp message IDs to include sender JID as this is necessary to reply to a message tulir/whatsmeow#88 (comment) tulir/whatsmeow#148 (comment) Based on commit 6afa93e from 42wim#1934 Author: Iiro Laiho <iiro.laiho@iki.fi> * Fix replies. Sender JID can have a `:` inside of it, using `/` as a delimiter now. Added messageID parser + struct. messages sent with an attachment do not show replies But at least common `sendMessage` will make repies from whatsapp to an attachement bridge across. The new message ID format broke message deleting, so we change the messageID into the real id at the beginning of send. We really do need the extra info for when we reply to a message though. * Refactored message replies. file/Image/audio/replies all work now.
Is there a way to reply for a specific message, same like the case in the WhatsApp app, where we hold a specific message and reply to it. Thanks
The text was updated successfully, but these errors were encountered: