Add speaker-tracker example#71
Open
jaredtribe wants to merge 1 commit intosteipete:mainfrom
Open
Conversation
A Python companion tool that reads wacli's SQLite database to track speakers across WhatsApp conversations. Features: - Speaker profiles with first/last seen, message counts - Privacy-preserving hashed JIDs - Opt-out support for contacts who don't want to be tracked - Conversation notes for manual annotations - Non-intrusive: reads wacli.db (read-only), writes to separate db This demonstrates how to build complementary tools on top of wacli's message data without modifying wacli itself.
Author
|
Closing - need to review for sensitive data exposure |
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.
Summary
A Python companion tool that reads wacli's SQLite database to track speakers across WhatsApp conversations.
Features
wacli.db(read-only), writes to a separate databaseWhy an example?
This demonstrates how to build complementary tools on top of wacli's message data without modifying wacli itself. It's a pattern others might find useful for building their own integrations (CRM sync, analytics, search indexes, etc.).
Usage
Requirements
wacli syncHappy to adjust location, naming, or scope based on your preferences. Just wanted to share a working example of building on wacli's data.