bannedbook/fanqiang

Choose the upstream unless you explicitly want a heavily pruned, frozen copy. This fork is not a good default for adopters because it appears to remove most of the practical documentation and is far behind current upstream state.

Prefer upstream unless you specifically need this older, heavily modified snapshot. The fork adds some local asset-heavy workflows, but its age and divergence make it a poor choice for anyone wanting current, maintained tutorials or packaged guidance.

Choose this fork only if you specifically need an old, self-contained snapshot of the project’s bundled tools and data. For most adopters, upstream is the better choice because it is far more active and much more current.

Prefer upstream for anything current. Choose this fork only if you need the older 2020 bundle structure or want to mine its data/assets; otherwise it is too stale and divergent for normal adoption.

Choose the upstream for current, broad coverage. Choose this fork only if you specifically want a frozen, older hosts/PAC-oriented bundle and can tolerate substantial staleness.

Prefer upstream unless you specifically need this older snapshot; the fork shows no meaningful added capability and is far behind current upstream activity.

Prefer upstream for current guides and broad coverage. Prefer this fork only if you specifically want the divergent Android/app work and are prepared to rebuild missing documentation and workflows yourself.

Choose this fork only if you specifically want the app-oriented divergence and are prepared to reconcile it with upstream; otherwise upstream is the better default because it is far newer, broader, and actively maintained.

Prefer upstream unless you need an old, frozen copy of the project’s bundled proxy/browser workflows. This fork looks like a legacy divergence with some customized rule and package assets, but it is far too stale for most new adopters.