torttube/docs/upstream.md
Kayos 76bd1d970e M0 docs — lock three-tier resolve + upstream-contribution posture
Cobb wants rustypipe primary, yt-dlp fallback, and rip-to-temp as the
last-resort path when streams die mid-play. README expanded to spell
out all three tiers + adds the 'fight YouTube alongside the FOSS
ecosystem' framing. MILESTONES M1 rewritten to cover all three tiers.

New file docs/upstream.md tracks every PR we file against rustypipe /
NPE / yt-dlp with honest outcomes. Opens empty; fills as M1+ surface
real bugs to fix.
2026-05-23 08:20:50 -07:00

1.6 KiB

Upstream contributions log

One row per PR/issue we file. Outcomes recorded honestly — merged, closed, abandoned, whatever happened.

Active

(none yet — opens with M1 development)

Filed

Date Project PR/Issue Title Status Outcome
empty

Watching (not ours, but relevant to torttube)

Project PR/Issue Title Why we care
rustypipe PR #77 "Some fixes" Open 2026-05-23, unmerged. If maintainer stays quiet we may need to help land it or fork.
NPE #1339 n-parameter deobfuscation broken Core to playback. Fix here = fix in our Tier-1.
NPE #1444 Distinguish unavailable vs unextractable Clean typed-error PR target.
NPE #1360 Refactor link handlers "help wanted" label.
NPE #1357 JDoc checks in PR pipeline "good first issue" — smallest credible first PR.

Posture

  • Every sidecar bug we trace ends with one question: is the root cause in rustypipe / NPE / yt-dlp? If yes, fix it there first; pull the fix into our sidecar via dep bump or backport.
  • We are not pretending to be on the rustypipe / NPE / yt-dlp maintainer level. We're a downstream consumer that does its share.
  • A merged PR > a forked patch. A fork is the last resort, not the first move.