An unofficial field guide to sorting official software, simulators, RL repos, and community notes without mixing them up.
Hobby robotics tabs multiply fast. One browser window holds a demo video. Another holds a fork of a training repo. A third holds a Discord invite that may or may not still be current. By the end of an evening you have bookmarks, but not a map.
This note is a practical way to sort MicroDuck-related resources before you clone anything. It is written for builders who want a calm first pass over software, simulators, RL repositories, and community links. It comes from MicroDuck Robot Community, an independent unofficial site. It is not affiliated with Pollen Robotics or Hugging Face, and it does not invent metrics, shipping timelines, or user counts.
Separate "official surface" from "community notes"
Start by labeling what kind of page you are looking at. Official software pages, browser simulators, and primary repositories deserve one pile. Community write-ups, local-training notes, and DIY checklists deserve another. Mixing the two is how people treat a fan guide as a release channel, or treat a release channel as the only place to ask beginner questions.
When a page is unclear, ask one question: who maintains this URL? If the answer is "the upstream project," keep it in the official pile. If the answer is "an independent community site or volunteer notes," keep it in the community pile and expect it to disclose that status.
Prefer one hub link while you are still exploring
During the first exploration pass, one curated hub beats ten parallel tabs. A single resources page that points at official software, a browser simulator, RL repositories, related communities, and a training-readiness tool lets you see the landscape without committing to a clone yet.
That is the role of the MicroDuck resources hub on the unofficial community site: a map, not a substitute for upstream docs. Use it to decide what to open next, then go to the primary source for install commands.
Check readiness before you treat RL repos as tonight's project
RL repositories look inviting because they promise motion. They also assume a stack: Python version, lockfiles, CUDA discovery, and task registries. Before you schedule a long run, confirm that the repo you opened matches the revision you intend to follow, and that the environment questions (Python, CUDA availability, task names) are answerable from that checkout.
A short install check is usually cheaper than discovering a broken stack after hours of silent compute. Treat community training notes as orientation; treat the pinned guide and primary repo as the copy-paste source.
Keep DIY checklists boring on purpose
BOM mistakes, prerelease image flashes, and "almost the right part number" failures are unglamorous. They are also the failures that waste weekends. Keep DIY checklists boring: quantity times unit price, connector families, battery rows, and spreadsheet formulas that accidentally omit a line. The goal is fewer cart surprises, not a more exciting story.
What this map does not claim
It does not claim that the unofficial hub is complete. It does not claim endorsement by Pollen Robotics, Hugging Face, or upstream maintainers. It does not invent traffic, stars, or benchmark scores. It only argues for a calmer order of reading: label the source, use one hub while exploring, then verify readiness before a heavy RL night.
Disclosure: MicroDuck Robot Community (microduckrobot.org) is an independent unofficial community site. It is not affiliated with Pollen Robotics, Hugging Face, or the upstream MicroDuck maintainers. I help operate that community site. The resources map above points to public pages for orientation; it is not an official product listing and not a performance claim.
Top comments (0)