Add Seal support for Android - #1294
Merged
Merged
Conversation
Two artifacts from databases/app_database: - Downloaded Media: each completed download with the title and author the source site reported, the URL supplied, the absolute path the file was written to, and the yt-dlp extractor, which names the service it came from. - Cookies and Templates: imported cookie profiles, whose presence records both a site and that a session for it existed, and the yt-dlp command templates. The download table carries no timestamp column, so none is reported. The only time signal is the modification time of the saved file, and the app's default template on the tested device was '--no-mtime -S "ext"', which leaves that as the time the file was written rather than the source media's own time. The notes say so and point the examiner at the file. The downloaded file is not copied into the report: Seal writes to shared storage, where the media is already within reach of the report's own media handling, and a video download can run to gigabytes. The recorded path is reported so the file can be located. Verified on a multi-container tree: the storage spellings collapse, a second Android user contributes its own rows, and a decoy package adds none. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Row counts from a real aleapp.py run against the emu_a15_oss_v6 corpus. The zero-row values are checked absences: the tables are present and empty in that image, confirmed against the source stores. Co-Authored-By: Claude Opus 5 <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.
Adds Seal (com.junkfood.seal) support for Android, an open source yt-dlp front end. Two artifacts from databases/app_database:
The download table carries no timestamp column, so none is reported. The only time signal is the modification time of the saved file, and the app's default template on the tested device was '--no-mtime -S "ext"', which leaves that as the time the file was written rather than the source media's own; the notes point the examiner there.
The downloaded file is not copied into the report: Seal writes to shared storage where the media is already within reach of the report's own media handling, and a video download can run to gigabytes. The recorded path is reported so the file can be located. CookieProfile and OptionShortcut were present and empty on the tested device.
Verified on a multi-container tree: the storage spellings collapse, a second Android user contributes its own rows, and a decoy package adds none. sample_data follows with the next corpus capture.