iawia002/lux

Prefer this fork only if its added batch/rate-control workflows are exactly what you need and you are comfortable maintaining it yourself. For most adopters, upstream lux is the better default because it is active and materially more up to date.

Prefer this fork only if its specific site support or legacy behavior matters more than freshness. For most users, upstream lux is the safer choice because it is actively maintained and much further ahead.

Choose this fork if its added platform coverage and cookie/cover workflows match your download targets. Choose upstream instead if you want the newer fixes, subtitle support, and a maintained baseline.

Prefer upstream. This fork adds no visible features and is materially behind on fixes and capabilities, so it is only reasonable if you explicitly want an unmaintained snapshot.

Choose this fork only if you need the old `cmd/ytdl`-style wrapper and are comfortable owning compatibility yourself. For most adopters, upstream `lux` is the better choice because this fork is stale and materially behind on features and fixes.

Prefer this fork only if you specifically need the YouTube visitor-ID fix and are comfortable being 12 commits behind upstream. Otherwise, upstream looks like the better default because it has newer site fixes and features while this fork appears to be a narrow maintenance branch.

Prefer upstream unless you specifically need this exact old snapshot. This fork adds no visible value and is materially behind on fixes and features, so adopters should expect worse compatibility and more maintenance burden.

Prefer upstream unless you specifically need this exact old snapshot. This fork has no unique code, is very stale, and is far behind current maintenance.

Prefer upstream Lux unless you specifically need this fork's custom downloader behavior or legacy compatibility. The fork is materially stale and highly divergent, so it is better viewed as a specialized snapshot than a maintained alternative.