Android class 2 batch 2: directions + views for Google Messages, TikTok, Google Chat, Discord#927
Merged
Merged
Conversation
Evidence-derived directions + conversation views, all validated against the Android test set: - Google Messages (bugle_db): direction from the sender participant's sub_id (self participants have sub_id != -2, the documented Bugle convention); adds Conversation ID. Validated 53/41 split over 11 conversations on one image. - TikTok: local account uid is the database filename prefix (<uid>_im.db); direction = sender uid == filename uid; adds Conversation ID from msg. Validated 9 Outgoing / 22 Incoming. - Google Chat (dynamite.db): account email is in the db path (user_accounts/<email>/); resolved to the gaia id via the users table of the same db; adds Group ID. Validated on two accounts (19/20 and 8/10 splits, owner rows matched by email). - Discord (kv-storage): account id from the @account.<id> path (same derivation as the iLEAPP artifact); emits Sender ID / Account ID / Direction. Validated 18/29 split on the public image. New columns appended; existing column order unchanged. Blank direction when the owner cannot be established.
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
Final four of the Android class-2 backlog — evidence-derived Direction columns and LAVA conversation views, each validated read-only against the Android test-image set before implementation.
sub_id != -2(documented Bugle self-participant convention; device's own number confirmed in test data)parts.conversation_id→ Conversation ID<uid>_im.db, incl.biz_*variants via trailing-number match)msg.conversation_id→ Conversation IDuser_accounts/<email>/) resolved to gaia id via the same db'suserstablegroup_id→ Group ID@account.<id>path segment (same derivation as iLEAPP #1648)Blank direction whenever the owner can't be established — never defaulted to a side.
Deliberately deferred (documented)
Testing
pylint 10.00/10 (4 files); byte-compile; PluginLoader 4/4 views registered; new SQL/derivations executed read-only against the real copied databases with the splits above.