291–300 of 724 posts
That's fine, please make it VERY CLEAR how much of my limit is left, and how much i've used.
This is also exactly why I feel this industry is sitting atop a massive bubble.
> affecting less than 5% of users based on current usage patterns. How about adding ToS clause to prevent abuse? wouldn't that be better than having a statement with negative effect on the rest of 95%?
I'm probably not going to hit the weekly limit, but it makes me nervous that the limit is weekly as opposed to every 36 hours or something. If I do hit the limit, that's it for the entire week —a long time to be without a tool I've grown accustomed to! I feel like someone is going to reply that I'm too reliant on Claude or something. Maybe that's true, but I'd feel the same about the prospect of loosing ripgrep for a…
Earlier quoted context omitted.
if it affects only a minority of accounts, why not figure out how to special case them without affecting everyone else is the primary question I would ask myself if I worked on this the principle: let's protect against outliers without rocking the behavior of the majority, not at this stage of PMF and market discovery i'd also project out just how much the compute would cost for the outlier cohort - are we talking $5…
> if it affects only a minority of accounts, why not figure out how to special case them without affecting everyone else that's exactly what they have done - the minority of accounts that consume many standard deviations above the mean of resources will be limited, everyone else will be unaffected.
correct me if I'm wrong, it's not like we have visibility into the token limit logic, even on the 5hr window?
Earlier quoted context omitted.
No, it's not. It's the all you can eat buffet saying that 95% can eat all they want, but the 5% that keep sneaking food in their backpack to eat when they get can't do that anymore.
There's no lobster rolls stuffed into a backpack here. It's using the service as it was pitched, an all-you-can-eat buffer of API calls. Anything that limits what that means is scaling back access to that buffet. If the new limits are anything less than 24 * 7 / 5 times the previous limits then power users are getting shafted (which understandably is the point of this). What's worse with this model is that a runaway…
Earlier quoted context omitted.
You can set cash on fire if you want to.
you spend 400$ per month on api usage, but your AI builds the next unicorn worth billions, where is the problem?