mirror of
https://github.com/Evil0ctal/Douyin_TikTok_Download_API.git
synced 2026-10-16 20:31:19 +08:00
Evil0ctal
f950b42ad9
145 issues were closed on this repository during the v4 wind-down. The ones that could not be answered were not unclear people - they were reports with no version, no deployment method and no diagnose output, where the only possible first reply was "please tell me more". Four forms per language, each asking for exactly what a first reply would otherwise have to ask for. Bug and Endpoint both require the diagnose output, and say what to send instead when the stack will not start and there is no api container to run it in. Endpoint is its own form because a platform changing its API is not a coding mistake and needs different evidence: which identity kind served it, what `explain` reported, and a link the reporter has confirmed still opens. It also asks first whether every endpoint is failing or only one, because an empty pool looks exactly like a broken endpoint from outside. Every form leads with "do not paste credentials" and makes it a required checkbox. People debugging this will have a cookie jar, a secret key and a proxy URL in front of them, and a public issue is a bad place to discover that. Blank issues are off; four contact links carry the traffic that is not an issue - Discussions for questions, Troubleshooting and Installation for the answers that already exist, and a private advisory for anything security. Labels are namespaced so they group in the picker: type, area, status, platform. The forms apply type and status: triage themselves. The v4-era labels are left alone - they are attached to closed issues and deleting one rewrites that history.