mirror of
https://github.com/Evil0ctal/Douyin_TikTok_Download_API.git
synced 2026-10-16 20:31:19 +08:00
Evil0ctal
d6b9fd90de
Five things, and a check for the bug the fifth one shipped with. The author mode pages the feed now, to a depth chosen from a menu - newest 20, 50, 100, 200, or everything the feed gives up. A menu rather than a number field because the cost is the thing worth showing: every post is a download and every page is a read through the pool, and a free-text depth invites "99999" typed without a thought. It walks pages rather than trusting one, because a page is whatever the platform felt like returning - 23 when 20 was asked for - and "the newest 100" has to mean 100. It also takes a bare sec_user_id, which is what the archive and the playground hand you. Both platforms spell it the same way, so the `MS4wLjABAAAA` prefix is the test - a recognition check, not a validator; the platform decides whether the id exists. The overview counted requests and nothing else: how many, how well, how fast, and not one number about what the instance is accumulating. A second row says what was kept - archived posts, media downloaded, disk used against its ceiling, downloads in flight, watchlist size - all of it from endpoints the page simply was not calling. The logo is the 2022 mark redrawn as an SVG. The braces are the part people recognise and they stay; the two dot clusters do not, because at the 24px this renders in the sidebar five dots collapse into a smudge. A downward arrow survives the size and says the other half of what this is. It draws in currentColor, and the accent tile it used to sit inside is gone - a line drawing needs its strokes apart, and a third of the box was going to padding. dtk is DTK everywhere the product names itself. Clicking an identity opens its history. It used to open the probe dialog and only if a probe had already been run, so a click usually did nothing. The drawer answers "degraded by what": a per-endpoint breakdown, because one endpoint refusing while the others answer is a signature problem or a sign-protected path, and every endpoint refusing is the identity itself - opposite responses, and a flat list of thirty rows does not tell them apart. Verified on a live identity: 30 calls to content_detail with one payload.withheld refusal, author_posts and comments clean, and the banner naming content_detail. That drawer shipped asking for two keys no catalogue has, which rendered as raw "identity.column.streak" in the middle of it. check-i18n verified en/zh parity and never looked at a t() call site, so nothing saw it - not tsc, not eslint, not the test suite. It scans them now, literal keys only, skipping call sites that pass their own defaultValue. Confirmed by reintroducing the exact typo.