SOURCES · Transparency
Where every card comes from, fully in the open.
BitShovel collects from a dozen-plus public sources across subscriptions, direct APIs, and communities, running automatically at 06:00 / 12:00 / 18:00 Beijing time. This listing is generated from the same registry the production pipeline uses — add or retire a source and this page changes with it.
01
SYNDICATED · Subscriptions
Eight feeds, each registered after review.
Every feed below is registered and reviewed one by one. Snapshots keep only titles, links, and timestamps — never body text. Entry changes land in a candidate queue and only reach a card after editorial review.
- Simon Willison's WeblogPersonal tech blog · ENFirst-hand LLM engineering practice and tooling shifts
- Baoyu's DigestPersonal digest blog · ZHChinese-language retellings and commentary on overseas AI news
- Product HuntProduct launch board · ENNew product launches and community heat signals
- LobstersTech community board · ENComputing and open-source discussion threads
- TLDR TechTech daily digest · ENDaily cross-checks across technical headlines
- AIHOTAI aggregator · ZHDiscovery leads across 168 AI sources; we take titles and original links only
- AlphaSignalEngineer AI daily · ENEngineering-angle leads on papers, repos, and model releases
- r/LocalLLaMAReddit community · ENHands-on local-model discussions and first-hand feedback
02
DIRECT · Direct and community
Structured data is collected directly; community signal is watched separately.
Beyond feeds, the pipeline collects GitHub repositories and weekly trending, Hacker News and its product radar, the OpenRouter model catalog, and V2EX hot topics, plus scheduled snapshots of key official pages. These sources are structured by nature and run under their own evidence contracts.
- GitHub repos and weekly trending: stars, releases, and README changes
- Hacker News and product radar: discussion heat and product discovery
- OpenRouter catalog: model, pricing, and context changes
- V2EX hot topics: first-hand indie-developer discussions in Chinese
- Official page snapshots: verifiable changes to sites and docs
03
THE CONTRACT · How aggregators are cited
Aggregators are leads; the original stays canonical.
For aggregators like AIHOT and TLDR we hold three rules: when a card is minted, the original article link (originalUrl) points to the primary source while the aggregator entry is recorded only as a discovery reference; snapshots never store the aggregator's summaries or translations; and card copy — including why it matters and its biggest limitation — is written by our editors after opening the original.
Originals that are blocked or unstable must have a reachable alternate link, or no card is minted. Past evidence is archived per snapshot and hash-pinned, so what we saw at the time can always be replayed.
04
GOVERNANCE · Review and exit
Sources are reviewed in; exits leave a trail.
Every source lives in a version-controlled registry, and collection runs behind one security boundary (host allowlists, response-size caps, private-address rejection). If a source asks to be corrected or removed, we comply and keep the archived history so existing cards stay verifiable.