One person can’t run every version
Versions keep shipping as rc and plugins change daily. Claim one item, contribute one post.
Which recipes are unrun, which plugins unverified, which ledger needs re-testing—all listed below. Submit by template; editors check facts only, not your conclusions.
Claim list
Only three states: open, in progress, merged.
| Type | To do | Status |
|---|---|---|
| Recipe | Recipe: build an index for 100 PDFs, run it once, and complete the run log | Awaiting claim |
| Recipe | Recipe: Excel monthly report with recomputed-formula verification, run once and complete the run log | Awaiting claim |
| Lab | Lab: Standard vs PTC on the same task; submit raw records | Claim in progress |
| Lab | Lab: compare token usage and cost across five context plugins | Awaiting claim |
| Lab | Lab: config backup and rollback drill before and after an upgrade | Awaiting claim |
| Compat | Compat: verify 30 common plugins on 0.2.2-rc.1 | Awaiting claim |
| Compat | Compat: retest the blast radius of the two breaking changes in 0.2.0 | Awaiting claim |
| Fix | Fix: reproduce UNKNOWN_TOOL / HTTP 400 and provide minimal reproduction steps | Awaiting claim |
| Fix | Fix: reproduce the settings-page 403 and confirm its link to browser extensions | Awaiting claim |
| Plugin | Plugin: verify dsh-context's install command and net token savings on a specified host version | Awaiting claim |
Community rules
Six rules, all about “never write untested as tested.”
- Only write up what you actually ran; if you haven't run it, mark it 'Not yet tested'.
- Host version, model, mode, permissions, and date are required; a missing field means no merge.
- Copy numbers straight from the run log: no estimating, no rounding, no tweaking to look better.
- If it doesn't work, say so honestly; a failure record is more useful than a success record.
- For third-party plugins, describe only observed facts: no endorsements, no 'must-install' labels.
- Don't speak as an official source, don't impersonate DeepSeek, and don't impersonate other community sites.
Submission templates
Submit by template; missing fields won’t be merged.
| Type | Required fields |
|---|---|
| Recipe | Use case / version and environment / full prompt / outputs / acceptance checklist / failures and boundaries |
| Lab | Question / control group / environment / raw data / conclusion / what cannot be generalized |
| Errata | Original page / what was wrong / evidence (version or screenshot) / suggested fix |
Contributor wall
Named by merged content count, not post count.
Nobody has claimed this yet. Read the rules first, then submit by the template.
How phase one runs
Don’t make people guess.
The site does static archiving and indexing. Discussion, Q&A and submissions all happen in the built-in forum (/bbs/) — register to post. The AI Q&A node is auto-answered by MyDSH AI. Merged content enters the static site; credit stays on the contributor wall.
- Discussion: https://mydsh.org/bbs/
- Submission: https://mydsh.org/bbs/?p=node&slug=submit