Where should each request go?
| Request | Recommended channel | Why |
|---|---|---|
| Specific bug | GitHub Issues in the relevant repository | Keeps versions, reproduction steps, and fix status together |
| Product idea | Relevant GitHub Discussions or Issues | Keeps public discussion beside the project context |
| Open-source collaboration | GitHub profile and relevant repository | Provides source code, license, and contribution details |
| Public conversation | X @liuzhao_666 / Bilibili 黑纹白斑马 | English technical updates and Chinese video content |
Project feedback channels
- YouDub IssuesVideo download, transcription, translation, dubbing, mixing, and rendering.
- Codex Account Switcher IssuesMac installation, account addition, usage, and switching.
- Codex Account Switcher DiscussionsWorkflow questions, product ideas, and tool comparisons.
- Claudex IssuesInstallation, model access, and local runtime issues.
- Remember Me IssuesContribution workflow, page generation, and project ideas.
What should never be posted publicly?
Do not post passwords, access tokens, API keys, real authentication files, private account data, unpublished project information, or sensitive information about another person in Issues, Discussions, comments, or screenshots. A useful bug report usually needs only the software version, operating system version, visible failure stage, and sanitized reproduction steps.