Use profile push names for sender resolution#7
Merged
steipete merged 2 commits intoMay 10, 2026
Conversation
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
2 participants
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.
Summary
ZWAPROFILEPUSHNAMEfrom the WhatsApp Desktop chat database during importZWAPROFILEPUSHNAMEand indexed by searchFixes #6.
Rationale
Some local WhatsApp Desktop archives have group sender fields such as
ZWAGROUPMEMBER.ZFIRSTNAMEorZWAMESSAGE.ZPUSHNAMEpopulated with opaque values.ZWAPROFILEPUSHNAMEprovides another local, read-only JID-to-name source that can improve the existingmessages.sender_namevalue without changing the archive schema.Because
messages.sender_nameis already indexed into FTS, this also improves sender-name search for the recovered names.Testing
go test ./...