Remix.run Logo
sergiotapia 5 days 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 5 days ago | parent [-]

...maybe use their superintelligent AI to come up with a solution that specifically targets the abusers?

SatvikBeri 5 days ago | parent | next [-]

...like adding limits that only affect a small fraction of users?

Yossarrian22 5 days ago | parent [-]

Is 1/20 small?

dotancohen 5 days ago | parent [-]

I'm Jewish. We take that right off the top shortly after birth.

dom96 5 days ago | parent | prev | next [-]

Easy, 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

cyanydeez 5 days ago | parent | prev | next [-]

[flagged]

blitzar 5 days ago | parent | prev [-]

Claude 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.