feat: recursive media discovery in --extract-scan#16
Merged
Conversation
…ilename-param output)
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
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
The scanner in
scan.conly looked at the landing page, so sites that load the player one or two clicks away (episode page -> /watch?file= -> the real .mp4) produced an empty skeleton. Now when the landing page has no direct media,scan_pagefollows internal watch/play/embed links up to--extract-scan-depthhops (default 2, max 3), re-scans each body with the same scoring, and records the capture chain that reached the media soscan_emit_configcan write a reusable multi-stepget/varconfig. Series index pages are detected and emit alistplus a per-episode pipeline. The crawl is bounded (visited-set,SCAN_MAX_FETCHES, 8 MiB page cap) and the ad-host blocklist still applies.Config generation no longer writes into the active dir:
run_extract_scanprints the config, stashes a pending copy under.pending/<id>.confkeyed by a stable id derived from the source URL, and suggestsflux --save-config <id>to install it active (refusing to clobber). Both the argv id and the config name parsed back out of the pending file are sanitized before they touch a path.Changes