Skip to content

Serve single-video galleries through video API - #20

Merged
zachlatta merged 1 commit into
mainfrom
investigate-chmv0-reel-archiving
Aug 16, 2026
Merged

Serve single-video galleries through video API#20
zachlatta merged 1 commit into
mainfrom
investigate-chmv0-reel-archiving

Conversation

@zachlatta

Copy link
Copy Markdown
Member

What changed

  • project complete, single-video gallery bundles onto Arker's normal video manifest and download contract
  • expose their stored raw provider record through /video/:shortid/raw
  • preserve photo, carousel, partial, and ambiguous legacy captures as galleries
  • reuse the gallery media serving path so HEAD, Range, MIME sniffing, and size limits remain consistent

Why

Instagram serves the same Reel at both /p/{shortcode} and /reel/{shortcode}. Arker must choose an extractor from the submitted path before it can see the media type, so a Reel submitted through /p/ can be correctly captured as one MP4 inside a gallery bundle but remain invisible to video consumers.

This makes the stored artifact's proven shape authoritative at response time without duplicating downloads or changing gallery routing.

Validation

  • go test ./... -count=1
  • go vet ./...

@zachlatta
zachlatta merged commit a025a8d into main Aug 16, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant