catacomb/ROADMAP.md
Luna b58d393d98 Update ROADMAP: reflect a session's worth of shipped work
The roadmap had drifted far behind reality. Reconcile it:

State table → 16 ahead / 2 behind / 11 tied (was 11/4/6). Newly tied or
led: per-distro packaging, N-level folders, notes, restore, error
classification, subtitles; new "we lead" rows for the anti-bot stack,
cookie freshness, auto-retry/throttle, and player-client config.

Phase 1: only format conversion (1.7) remains as a real Tartube parity
gap. Notes (1.5), packaging (1.8), and N-level nesting (1.2+) moved to
"shipped". Phase 2: 2.3 / 2.4 marked done, 2.5 mostly done (crash log +
disk-full preflight + auto-retry shipped; lock-poisoning audit + hang
watchdog remain).

Expanded "Recently shipped" with this session's anti-bot + subtitle +
packaging + perf + wgpu work.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-06-01 16:53:19 -07:00

10 KiB

Roadmap

North star

Surpass Tartube in every dimension.

A structured analysis of Tartube's codebase, data model, operations, and configuration surface lives at docs/tartube-spec.md. It enumerates the exact features we need to match — every Phase 1 item below traces back to a specific Tartube subsystem.

Tartube is the mature open-source yt-dlp GUI and the obvious benchmark for a project in this space. yt-offline has architectural advantages Tartube can't catch up on quickly (Rust + axum + a real web UI + bundled toolchain + a modern security model) but trails on feature breadth and years-of-edge-cases maturity. The plan below closes those gaps first, then pushes past.

Current state vs Tartube (2026-06-01)

Area Us Tartube Verdict
yt-dlp wrapping Tied
Multi-platform sources first-class per-platform routing generic We lead
Web UI accessible from any device desktop only We lead
Single-binary distribution Rust binary + venv installer Python+GTK deps We lead
Per-distro packaging .deb / .rpm / AppImage + PKGBUILD + CI .deb .rpm .pkg.tar.zst Tied
Security model (auth, CSP, rate-limit) never network-facing We lead
Plex export with NFO sidecars We lead
Anti-bot stack (impersonation + POT + nightly) curl_cffi + bgutil-pot + nightly yt-dlp user-installed We lead
Cookie freshness / anonymous-jar warning We lead
Auto-retry + adaptive throttle on rate-limit We lead
Configurable YouTube player clients global + per-channel We lead
Themes 10 themes GTK default We lead
Live-stream recording recent Tied
WebSocket real-time progress polling We lead
Mobile-responsive web UI desktop only We lead
Per-channel custom download options JSON-blob overrides deep Tied
Subtitle controls (auto / embed / convert) global + per-channel Tied
Folder/group hierarchy N-level nesting N-level Tied
Filter UI (date / size / watched) chip-style rich + presets Tartube leads (presets only)
Comments capture --write-comments + viewer raw JSON We lead
System tray ksni (Linux SNI) GTK Tied
Library backup + restore DB snapshot + idempotent import Tied
Per-channel notes / annotations searchable Tied
Error classification + suggested fixes 9-class + hints rescue recipes Tied
Crash log + disk-full preflight partial We lead
Format conversion / re-encode remux only ffmpeg pipeline Tartube leads
Maturity / edge cases ~months ~years Tartube leads

Score: 16 ahead, 2 behind, 11 tied. The big remaining gap is format conversion (1.7); everything else is polish or stretch.

Phase 1 — Remaining Tartube parity items

1.7 Format conversion pipeline — the one real parity gap left

Post-download re-encode option: H.264/AAC mp4 at a configurable CRF, or audio extraction at a target bitrate. Useful for shrinking large 4K files.

  • New post_process config field per quality preset.
  • ffmpeg job runs after the download completes, replaces the source file (or keeps both with an .original.mkv suffix).
  • Visible in the job log as a separate "transcoding" phase.

1.3+ Filter presets (extension of completed 1.3)

The chip filters ship, but Tartube also lets you name a filter set and restore it later. Small UI layer on top of what's already implemented.

  • "Save current filters as…" button next to the clear-filters link.
  • Presets stored in localStorage (web) / SQLite (desktop).
  • Dropdown chip to apply a saved preset.

Phase 2 — Polish where Tartube is mature

Things we win on architecturally but lose on real-world ruggedness.

2.1 Integration test coverage

91 unit tests are good for parsers/helpers/resolvers, but don't cover end-to-end correctness. We need real-yt-dlp integration tests against a recorded fixture corpus.

  • Mock-server fixtures for yt-dlp's JSON output.
  • cargo test --features integration exercises the full download pipeline against the mock.
  • Headless web-UI tests via headless_chrome or playwright.

2.2 Documentation site

README is the only user-facing doc. Need a real docs site with:

  • Per-platform setup guide (deeper than current README sections).
  • Troubleshooting playbook for the top 10 yt-dlp errors.
  • Architecture page (for contributors).
  • Hosted via Codeberg Pages.

2.3 Error recovery / structured logging — DONE

Shipped a 9-class error classifier (RateLimited, MembersOnly, Geoblocked, NotFound, CodecMissing, DiskFull, NetworkError, BadCookies, Other) with a one-line suggested fix per class, surfaced in both UIs. Remaining stretch: opt-in anonymous error telemetry to surface new patterns.

2.4 Library restore — DONE

POST /api/restore/db + file pickers in both UIs do an idempotent merge (watched / positions / flags / folders / notes), schema-validated.

2.5 Stability hardening — mostly DONE

Done: crash.log panic hook, disk-full preflight (synthetic DiskFull job), auto-retry + adaptive throttle on transient failures. Remaining:

  • Replace remaining .lock().unwrap() with poisoning-aware accessors.
  • Hang watchdog: if a yt-dlp job stalls past --socket-timeout * retries, kill and re-queue.

Phase 3 — Surpass

Once we're at parity, we push past Tartube on its own ground.

3.1 Cross-compile macOS + Windows binaries

The current "later" roadmap item, blocked behind 1.8.

3.2 Android client

Native client over the existing web API. Background download via WorkManager + JobScheduler. Push notifications via Tailscale-routed HTTPS or a userland push channel.

3.4 Smart auto-tagging

Cluster channels by uploader frequency, content type, and metadata. Suggest groups ("looks like a music channel — move to Music?"). Builds on Phase 1.2's group system.

3.5 Federation / multi-host

A "remote library" mode where one yt-offline instance can browse another's library (read-only) over the same axum API. Useful for a "home archive + travel laptop" setup.

3.6 Comment viewer enhancements

The comments capture (1.4) already ships a viewer. Surpass Tartube (which only dumps the raw JSON) with:

  • Threaded display with collapse/expand at any depth.
  • Full-text search within a video's comments.
  • "New since last visit" highlights.
  • Sentiment / keyword filter chips.

3.7 Library-wide deduplication

Right now maintenance finds duplicates by yt-dlp video ID. Surpass by fingerprinting media bytes (ffmpeg-derived perceptual hashes) so the same video re-uploaded under a different ID gets flagged.

3.8 Plugin / scripting hook

Lua or WASM-based hooks that run on download events: pre-download filename rewriter, post-download archive uploader, custom metadata enricher. Inverts the "we hardcode everything" model.

Phase 4 — Stretch / blue-sky

Probably never, or much later.

  • A web UI built around a "TV mode" remote-friendly layout.
  • AI summarisation of videos (transcript → bullet points).
  • Multi-user accounts with per-user watched/positions (currently single-user).
  • Integration with Plex / Jellyfin / Kodi as a source plugin rather than a symlink generator.

Recently shipped (highlights)

Roughly reverse-chronological. Items that closed out a roadmap line.

  • Anti-bot stack — POT token provider (bgutil-pot, version-matched plugin), nightly yt-dlp for working curl_cffi impersonation, dropped the captcha-prone forced player_client=web, auto-retry + adaptive throttle on rate-limit, configurable player clients (global + per-channel), cookie freshness / anonymous-jar warning.
  • Subtitle controls — global [subtitles] config + per-channel overrides (download / auto / embed / convert-format / langs).
  • N-level folder nesting (1.2+) — parent_id tree, recursive sidebar, move-folder-into-folder with cycle prevention.
  • Per-distro packaging (1.8) — .deb / .rpm / AppImage via scripts/package.sh + Forgejo CI release artifacts.
  • Per-channel / per-video notes (1.5) — searchable annotations.
  • Library restore (2.4) — idempotent backup import.
  • Error classification (2.3) — 9-class classifier + suggested fixes.
  • Crash log + disk-full preflight (2.5) — panic→crash.log, statvfs guard before download.
  • wgpu renderer — fixed NVIDIA+Wayland crash-on-maximize.
  • Performance pass — info.json mtime cache, thumbnail worker pool, /api/library body cache, opt-level=3 + thin LTO.
  • System tray (1.6) — ksni-based SNI tray, minimize-to-tray opt-in.
  • Filter chips (1.3) — watch / date / size / has-subs / has-chapters, AND together, persisted to localStorage.
  • Web downloads modal — bottom #jobs bar replaced with a ⬇ button in the header opening a full modal. d keyboard shortcut.
  • Desktop screens refactor — Settings/Stats/Maintenance moved from floating windows to full CentralPanel views with vertical scroll.
  • WebSocket job progress (3.3) — replaced HTTP polling.
  • Mobile-responsive web UI — proper media queries at 640px / 380px.
  • Library backup (2.4 — backup direction) — DB download from settings.
  • Theme contrast fixes — every theme now passes per-state fg_stroke contrast checks.
  • Shuffle play — random unwatched video on the desktop + web.
  • Keyboard shortcuts/ r d ? in the web UI.
  • Bulk tagging + channel-name search — multi-select + flag bulk-set.
  • Channel folders + per-folder Check all (1.2) — one-level grouping.
  • Per-channel download options (1.1) — JSON-blob overrides applied on scheduled re-checks.
  • Per-video state flags + smart folders + comments capture (1.3/1.4) — favourite / bookmark / waiting / archive flags as smart-folder views; --write-comments with viewer tab.

How to read this

  • Phase 1 is the remaining parity work — four bounded items.
  • Phase 2 is concurrent polish — pick up between Phase 1 items.
  • Phase 3 is the year-1 ambition once we're at parity.
  • Phase 4 items might be valuable, but commit to nothing.

Items inside a phase are loosely ordered by user-visible impact, not strict prerequisite. 1.8 (per-distro packaging) is the biggest multiplier for new users; 1.5 (notes) is the biggest workflow gap.