Discofork
Repository brief

NanmiCoder/MediaCrawler

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-30T12:50:48.091Z
3mo ago

NanmiCoder/MediaCrawler

MediaCrawler is a popular Python-based open-source crawler for public content and comments across major Chinese social platforms, including Xiaohongshu, Douyin, Kuaishou, Bilibili, Weibo, Baidu Tieba, and Zhihu. It is actively maintained, has a large user base, and focuses on browser-based login-state reuse with Playwright rather than JS reverse-engineering.

GitHub
Loading tags...
Stars46,908
Forks10,079
Default branchmain
Last pushed2026-03-24T01:52:40Z
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

9 of 9 fork briefs
Selected

Choose upstream if you want the broadest, freshest, and best-documented MediaCrawler. Choose this fork only if its specific local crawler changes match your needs and you are prepared to absorb the maintenance gap and missing upstream coverage.

Choose this fork only if you explicitly want a smaller, older branch and are willing to lose recent upstream capability. For most adopters, current upstream is the better default because this fork is materially stale and likely incomplete.

Choose this fork only if the reduced scope is the point. For most adopters, upstream is the safer default because it is far more current and much broader in platform support.

Prefer upstream unless you specifically want an older, minimally changed fork. This fork looks stale rather than differentiated, so adopters should expect to lose newer features and fixes in exchange for no clear fork-specific benefit.

Choose this fork only if you need its existing custom behavior and can live without upstream freshness. For most adopters, upstream looks safer because it is much newer and broader; this fork is best treated as a legacy, highly customized branch.

Choose this fork only if you want the learning-focused older base and its few targeted tweaks; choose upstream if you want broader platform coverage and active maintenance.

Choose upstream unless you specifically want this fork's client-abstraction direction and can tolerate losing newer fixes and some platform coverage. This fork is better as a reference implementation or customization base than as a drop-in production crawler.

Adopt this fork only if you specifically want its older customized behavior and are comfortable owning a stale, significantly diverged codebase. If you want broad platform coverage, active maintenance, and easier forward compatibility, upstream is the better default.

Prefer upstream unless you need a static snapshot. This fork adds nothing visible, while trailing 266 commits makes it a poor choice for adopters who want current fixes or newer crawling workflows.