fix: API 分页速率限制 + 429 检测#2
Open
alloevil wants to merge 1 commit into
Open
Conversation
- Detect HTTP 429/403 responses with exponential backoff (1s→16s) - Detect Weibo business error codes (10023/10024 frequency limits) - Detect auth expiry (error_code 21301) and stop gracefully - Add consecutive error counter with MAX_CONSECUTIVE_ERRORS=5 cutoff - Increase base delay from 300ms to 500ms - Add extra 2s rest every 50 pages - Replace bare catch-retry with proper backoff strategy Previous behavior: 500 requests at 300ms intervals with no error handling could trigger Weibo's rate limiter and risk account suspension.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
问题
auto-archive-simple.js的 API 分页逻辑存在速率限制风险：修复
影响
归档行为不变，但遇到限流时会自动降速而非硬冲。