Browser extension and local backend that automatically archives YouTube videos

Original Article ↗ Hacker News Discussion ↗

Project & Purpose

  • Extension + local backend automatically archives every YouTube video a user watches, using yt-dlp and ffmpeg.
  • Main use case emphasized: painless capture of source material for later clipping/editing in tools like Final Cut Pro, without interrupting viewing.
  • Several commenters like the idea for recovering videos that later disappear from YouTube, or for watching via local setups (e.g. Plex, Jellyfin) without YouTube apps or ads.

Implementation, Formats & QuickTime Debate

  • Backend saves to ./data/ and converts to MOV with hardware-accelerated ffmpeg; audio is copied, video is re-encoded for better QuickTime/FCP compatibility.
  • Some strongly object to re-encoding (quality loss, wasted CPU) and to using MOV as default; suggest keeping original bitstreams and using MP4/MKV instead.
  • Lengthy debate over whether QuickTime “can’t” play YouTube MP4s:
    • One side: “You must re-encode; QuickTime rejects direct yt-dlp MP4 outputs.”
    • Others demonstrate yt-dlp format selections that produce MP4s QuickTime plays without re-encoding, and the first side partially concedes but notes it doesn’t work for all videos.

Alternatives & Related Tools

  • Mentioned tools: yt-dlp scripts (clipboard-based), TubeArchivist, ArchiveBox, LocalTube (with SponsorBlock + auto-expiry), HEAP (macOS archiver using yt-dlp), ErsatzTV scheduling, plus general “universal web cache” wishlists.
  • Some prefer manual triggers (copy URL, press a button) to avoid “wasting” bandwidth/CPU on everything watched.

Archiving vs Hoarding

  • Extensive discussion about digital hoarding:
    • Critics compare it to old VHS/magazine hoards that were rarely reused.
    • Supporters argue digital storage is cheap; the real value is anti-censorship, preserving pre-edited/cancelled works, and enabling personal recall (“that one recipe/fact/song that later vanished”).
    • Several note many playlist items silently disappear from YouTube over time.
  • Broader reflection on what’s worth keeping, digital legacy for descendants, and the tradeoff between minimalism and preservation.

Shared Archives, P2P & Legal Concerns

  • Some propose adding DHT/torrent-like sharing to offload bandwidth and “solve global video distribution,” drawing comparisons to PeerTube.
  • Others warn any P2P redistribution of YouTube content would quickly attract DMCA pressure, unlike decentralized tools like yt-dlp which are harder to shut down.
  • A few dream about central repositories or monetized rehosting (e.g., via Lightning payments), but acknowledge copyright risk.

Browser & Web Archiving Limitations

  • Frustration that browsers don’t let users easily save already-buffered media blobs or automatically archive the current state of bookmarked pages.
  • Commenters note that integrating “one-click download” into mainstream browsers could invite legal action, pushing such functionality into third-party tools instead.

Backend Design & Edge Cases

  • Backend exists because browser extensions can’t run yt-dlp directly or bypass DRM mechanisms reliably.
  • Users ask about age-restricted/subscriber content; solution is to pass browser auth/cookies through to yt-dlp, which is acknowledged as a future enhancement.