twitter/the-algorithm
Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.
twitter/the-algorithm
Open source X recommendation-system repository for serving feeds across product surfaces. It is large, active, and widely forked/starred, with recent repository activity on 2025-09-03 and an updated default branch `main`. The codebase centers on the For You Timeline and Recommended Notifications.
Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.
Choose a fork to inspect
Prefer this fork only if you want a nearly pristine copy of upstream for inspection or a minimal starting point. If you need the newest upstream behavior or an actively maintained variant, use upstream instead.
Prefer this fork only if you want a frozen, heavily simplified reference copy. If you need an up-to-date recommendation platform, upstream is a much safer starting point.
Choose this fork if you value a cleaner, more consumable copy of the upstream project with added contributor and AI-discovery metadata. Choose upstream if you want the broadest, least opinionated baseline implementation and do not need the extra repo-level scaffolding.
Prefer this fork only if you want a close upstream snapshot with essentially no divergence. If you want active maintenance or fork-specific capabilities, upstream is the better choice.
Prefer this fork only if you want a frozen snapshot for inspection or isolated experimentation. If you want an actively maintained or differentiated fork, upstream is the better choice.
Prefer upstream unless you specifically need an untouched 2023 snapshot; this fork adds nothing and is materially stale.
Choose this fork only if you want an unmodified snapshot of the upstream X recommendation codebase. If you want current behavior or a base for ongoing work, upstream is the better choice.
Prefer upstream unless you specifically want a frozen reference copy. This fork adds no capabilities and is behind on recent upstream work, so it is a poor choice for adopters who need current fixes or maintained recommendation behavior.
Prefer this fork only if you want a static reference copy of the upstream project. If you need an actively maintained or feature-added fork, the upstream repository is the better choice.