Repository navigation
feat: store MyAnimeList's larger image copy - #19
Merged
Merged
Conversation
MyAnimeList serves two copies of every image under the same name: the 225px thumbnail the scraper records and a ~424x600 one with an l before the extension. One HEAD per image picks the larger when it exists, with the small one as the fallback. Decided before the skip rule, so an object stored from the small copy is replaced once by the large one and then left alone. Nearly twice the resolution at the source beats anything an upscaler invents; text on a poster is legible at 424px. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
bludot
force-pushed
the
feat/mal-large-images
branch
from
October 5, 2026 13:10
3f51fc6 to
5910ca4
Compare
Contributor
Author
|
🎉 This PR is included in version 1.20.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Stacked on #18.
MyAnimeList serves two copies of every image under the same name: the 225px thumbnail the scraper records, and a larger one, about 424x600 for a poster, with an
lbefore the extension:…/images/anime/1668/108792.jpg…/images/anime/1668/108792l.jpgThe processor now asks for the larger copy with one HEAD and falls back to the small one when there is none. It is decided before the skip rule, so an object stored from the small copy is replaced once by the large one (its recorded source length differs) and then left alone. Nearly twice the resolution at the source beats anything an upscaler can invent, and text on a poster is legible at 424px where it was not at 225.
Expect one wave of re-downloads as events for existing anime come through; each object upgrades once. upscaler-service's per-kind scale (2x for root images) lands those at about 850px, where 4x of the 225px copy did, with far less invented detail.
Tests: the URL rule (anime, character, already-large, query strings, non-MAL hosts), the large copy being stored with its length recorded, and the fallback when the large copy is missing.
🤖 Generated with Claude Code