/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

ngosang/trackerslist

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T11:54:05.687Z

3mo ago

ngosang/trackerslist

ngosang/trackerslist is a highly active repository that publishes automatically updated public BitTorrent tracker lists. It has 53,333 stars, 6,623 forks, is not archived, and was updated on 2026-03-30.

Loading tags...

Stars53,333

Forks6,623

Default branchmaster

Last pushed2026-03-29T22:09:46Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer upstream unless you specifically want an older, customized tracker snapshot. This fork is materially stale, so it is only a good fit for users who value fixed list contents or fork-specific filtering over current tracker accuracy.

Choose upstream unless you specifically want a frozen forked snapshot; this fork is materially stale and is not a good fit if current tracker freshness matters.

Choose upstream for any real use. Choose this fork only if you specifically want a frozen historical variant and are prepared to maintain it yourself.

Prefer upstream if you want current public BitTorrent trackers. Prefer this fork only if you specifically need the Go embedding workflow or a frozen/custom-curated tracker bundle and do not rely on upstream freshness.

Prefer upstream unless you explicitly want a frozen 2021 snapshot; this fork is materially stale and removes some upstream list variants.

Adopt this fork only if you specifically want a customized, frozen tracker-list variant; otherwise upstream is the better choice because it is actively updated and more current.

Prefer upstream unless you specifically want an older, pinned copy. This fork does not show meaningful new capabilities and is materially behind the current list updates.

Adopt this fork only if you want a custom, low-maintenance snapshot to own going forward. If you need current public BitTorrent tracker lists, upstream is the better choice.

Choose upstream unless you specifically want a frozen, diverged snapshot. This fork looks like a stale derivative with reduced maintenance value and possible loss of some niche list coverage.

Prefer upstream unless you specifically need an old, frozen tracker snapshot; this fork is materially stale and likely worse for anyone who wants current tracker URLs.

Fork comparison

Petersui/trackerslist

38/100

stale

significant_divergence

Prefer upstream unless you specifically want an older, customized tracker snapshot. This fork is materially stale, so it is only a good fit for users who value fixed list contents or fork-specific filtering over current tracker accuracy.

Likely purpose

Keep a manually adjusted tracker list snapshot with different tracker membership and blacklist rules from upstream, instead of following upstream's daily automated updates.

Best for

Users who want a fixed historical tracker snapshot instead of a continuously refreshed feed.; People experimenting with their own tracker curation rules or blacklist policy.; Projects that prefer a stable fork over upstream freshness and are willing to manage tracker updates themselves.

Additional features

A customized tracker set derived from upstream lists rather than a straight mirror.
Protocol-specific list variants remain available across UDP, HTTP, HTTPS, WS, I2P, and IP-based formats.
An edited blacklist that appears to reflect fork-specific filtering choices.
Adds fork-specific behavior in `trackers_all.txt` and `trackers_all_ip.txt`.

Missing features

Daily upstream updates are not present; the fork last pushed in 2022 while upstream continues updating every day.
The fork appears to lag far behind upstream by roughly 200 commits in each direction, so current tracker coverage is likely outdated.
Upstream's more recent list curation and removal/addition cycle is missing, which matters for users who need fresh tracker URLs.
Some protocol variants appear reduced or altered compared with upstream, including deletions in `trackers_all_i2p.txt` and `trackers_all_yggdrasil_ip.txt`.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Useful if you want a frozen, fork-specific tracker set and do not need daily churn.
Still targets the same tracker-list workflow as upstream, so adoption cost is low for users already consuming tracker text files.

Risks

Tracker freshness is the main risk; stale lists can contain dead endpoints.
Because the fork diverges materially from upstream, its blacklist and list composition may no longer match current tracker availability.
Users depending on the newer upstream automation will likely see worse results here.

ngosang/trackerslist · Discofork