4 ms·
Think of an insane number of requests. Now 20x it, that's what the top 1% of Claude users are at. Just fleecing the service dry. hard problem, what else could C
by sergiotapia 1y ago
Think of an insane number of requests. Now 20x it, that's what the top 1% of Claude users are at. Just fleecing the service dry. hard problem, what else could Claude do tbh
- handfuloflight 1y ago...maybe use their superintelligent AI to come up with a solution that specifically targets the abusers?
- cyanydeez 1y ago[flagged]
- SatvikBeri 1y ago...like adding limits that only affect a small fraction of users?
- Yossarrian22 1y agoIs 1/20 small?
- dotancohen 1y agoI'm Jewish. We take that right off the top shortly after birth.
- blitzar 1y agoClaude says - The key is maintaining user agency—let them choose how to manage their usage rather than imposing arbitrary cutoffs. It suggests: Transparent queueing - Instead of blocking, queue requests with clear wait time estimates. Users can choose to wait or reschedule. Usage smoothing - Soft caps with gradually increasing response times (e.g., 2s → 5s → 10s) rather than hard cutoffs. Declared priority queues - Let users specify request urgency. Background tasks get lower priority but aren't blocked. Time-based scheduling - Allow users to schedule non-urgent work during off-peak hours at standard rates. Burst credits - Banking system where users accumulate credits during low usage periods for occasional heavy use.
- dom96 1y agoEasy, they just gotta hit up the AI on each request with a prompt like "You are an AI that detects abuse, if this request is abusive block it" /s