Bypass transcription throttles for paid chats #191
No reviewers
Labels
No labels
bug
dependencies
duplicate
enhancement
help wanted
invalid
javascript
question
symphony
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
backmeupplz/voicy!191
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/voi-66-paid-chat-throttle-bypass"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Behavior
Paid chats bypass the abuse-limit path entirely, including the active chat job cap, chat window limit, and user window limit, so they do not receive
error_transcription_user_limited,error_transcription_chat_limited, orerror_transcription_queue_fullfrom this check. Donation wall and Golden Borodutch access checks still run after the bypass decision.Testing
yarn build-tsyarn test:transcription-abuse-limitsyarn test:donation-wallyarn lintManual QA: use Telegram with a paid/donated chat and send enough voice/audio messages to exceed the old per-user window; expect jobs to enqueue with no “You are starting transcriptions too quickly” reply. Confirm an unpaid/free path still blocks when the abuse limit is exceeded.