KRTirtho/spotube

Prefer this fork only if iOS background play is the main requirement and you are comfortable carrying a large rebase burden. For most adopters, upstream is the better default because it is far more current and broadly maintained.

Prefer upstream unless you need this exact historical snapshot. The fork adds no visible capabilities, is far behind, and appears stale enough that adopters should expect more problems than benefits.

Do not adopt this fork if you want an actively maintained Spotube. It adds no visible capabilities over upstream and is substantially behind, so the main value is only as a static baseline.

Adopt this fork only if you want a near-upstream Spotube snapshot and are comfortable carrying upstream maintenance debt. Prefer upstream if you want the latest fixes and active development; prefer this fork only if its branding or snapshot state matches your needs.

Do not adopt this fork as a production alternative to upstream. It offers no visible added capability and is far behind upstream, so the safer choice is the active Spotube repository unless you specifically need this exact historical state.

Prefer upstream unless you specifically need this fork's older pinned state or its tiny local edits; it does not look like a meaningfully enhanced alternative.

Prefer upstream unless you specifically need this older pinned state. This fork does not add capabilities; it mainly inherits technical debt from being far behind an active upstream.

Prefer upstream unless you explicitly need this exact old snapshot. This fork does not add functionality and is materially behind current Spotube, so it is mainly useful as an archive or private starting point.

Prefer upstream for almost everyone. This fork only makes sense if you specifically want the older desktop-centric behavior and are prepared to live without modern Spotube features and fixes.