tttttt#300
Closed
sohepalslamat wants to merge 25 commits into
Closed
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the contributors list in the README.md file by adding several new members and reordering existing entries. The review feedback identifies several HTML syntax issues within the contributor table, such as missing quotes for 'href', 'src', and 'alt' attributes, which can cause rendering problems or truncated text. Additionally, the feedback suggests correcting an invalid semicolon in the 'width' attribute and updating the pull request title to be more descriptive.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…olMessage WhatsApp clients on mobile (iOS/Android, since ~mid-2025) deliver text-message edits wrapped in a `secretEncryptedMessage` envelope: the new text is E2E encrypted in `encPayload`, with the original message identified by `targetMessageKey`. Without decryption, the webhook only ships the ciphertext and downstream consumers cannot extract the edited text — silent dropouts for every mobile edit. Desktop edits are unaffected (they continue to arrive as the legacy `protocolMessage.type === 14` shape that whatsmeow already exposes plain-text). whatsmeow ships `Client.DecryptSecretEncryptedMessage` which handles every step (HKDF from the original message's `messageSecret` + AES-GCM with the event's IV/payload). It supports all four secretEncType values: EVENT_EDIT, POLL_EDIT, POLL_ADD_OPTION, MESSAGE_EDIT. We call it once at the top of the `*events.Message` handler and swap `evt.Message` to the decrypted body, so the rest of the handler (and every downstream consumer of the webhook) sees the legacy `protocolMessage` shape, identical to a desktop edit. Failure is silent (log + continue) — the webhook still ships the raw encrypted shape and behavior matches today. Verified: builds clean against the whatsmeow version pinned in go.mod (go.mau.fi/whatsmeow v0.0.0-20260305215846-fc65416c22c4). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ace to webhook Mobile WhatsApp clients (since ~mid-2025) deliver text edits wrapped in secretEncryptedMessage. This commit invokes whatsmeow's DecryptSecretEncryptedMessage at the top of the *events.Message handler so the rest of the pipeline sees the legacy protocolMessage shape, identical to a desktop edit. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…support The version pinned previously (2026-03-05 fc65416c22c4) only supports SecretEncryptedMessage_EVENT_EDIT in DecryptSecretEncryptedMessage — it rejects MESSAGE_EDIT with "unsupported secret enc type". WhatsApp mobile clients began sending text-message edits as MESSAGE_EDIT (not EVENT_EDIT) around 2026-05-13, breaking decryption for the DecryptSecretEncryptedMessage call added in PR #1. Upstream whatsmeow commit fcbcaad5f23d (2026-05-04, "add more secret encrypted message types") added the missing cases for POLL_EDIT, POLL_ADD_OPTION and MESSAGE_EDIT to the switch. We bump to the latest on main (9b5c6556698f, 2026-05-13) which includes that fix plus a follow-up improvement on decrypt error reporting. Verified end-to-end: mobile edit (secretEncType=MESSAGE_EDIT) now decrypts inside WUZAPI and the webhook ships protocolMessage.type=14 with plaintext editedMessage.conversation — Sayyad picks it up and posts restoration. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.