I Am the Reason OpenAI Is Killing Unlimited Chats
chaosmanage.github.io
chaosmanage.github.io
> I am simply making the best use of what OpenAI has made available to me
People like this are why you can't have good things.
It should not be necessary to set up technical or written guards against every possible act of bad behaviour.
Instead be nice. Don't be that **ole who steals the whole candy bucket on Halloween just because you can.
> Do not attribute to malice that which can be attributed to really weird usecases.
see also, xkcd.com/1172 (spacebar heating)
I think the core issue isn't the abuse, but the very existence of a service that claims to provide infinite of something. Infinite is always BS because resources aren't infinite.
It's just like "all you can eat" places kicking out people after they've been in the restaurant for a while. We should discourage these marketing tricks because they are always a lie.
Regarding Halloween, we stopped leaving unattended buckets out because of bad actors taking everything. Now we hand out the candy ourselves. Our home no longer provides "all you can grab" treats...
We left a bucket out while we were out with the kids. No issue. Had too much at the end of the night, and had to tell the last stragglers to just take handfuls when we got back. Maybe that's a good, quick temperature check on whether your area is high-trust/low-trust.
* Lets people use whatever approach they prefer (- and if someone wants to keep their existing setup they can - with reasonable limits)
* Minimizes risk of users getting banned, including due to A) activity they didn’t know was disallowed, or B) false positives from OAI
* Heads off different future loopholes
* Avoids adding more TOS complexity
* Avoids users being uncertain if borderline activities will get them banned
But to do THAT you need to max out every 5 hour block. Of course people are going to start abusing unlimited chat in the mean time and start optimising the ability to burn tokens as fast as they can.
Good riddance. Like geez.
You're not wrong, but only in the sense that OpenAI and plenty of other powerful companies are full of people doing pretty much the same thing, and they cause a lot more "nice things" to disappear than individuals like the one you're talking about could ever cause to get taken away in their lifetime.
https://news.ycombinator.com/item?id=14511935#14514308
User stores 2 petabytes of porn on Amazon Cloud: https://www.techspot.com/news/70741-redditor-tested-amazon-u...
How is it abuse to use the feature as advertised? If they only wanted, say, 1 TB per user, then why not limit it to 1 TB per user? Only a vanishingly small number of people would even notice. The only difference is "unlimited cloud storage" doesn't sound as good in ads as "1 TB cloud storage". That's just marketing writing checks that engineering can't cash, that's nothing new.
How is this different from using your €90 Anthropic subscription to the fullest and then discovering same usage via api would cost many thousands a month.
No doubt they are loosing great deal of money on it, but if they provide this service why should an average person not use it?
It's the advertising that makes it different.
We had 2 major threads in the past 48 hours complaining about this:
* https://news.ycombinator.com/item?id=50319358 (AI/ML work with large models)
* https://news.ycombinator.com/item?id=50320255 (reverse engineering)
The threads are full of upset comments!
The only non-OAI options are open models and I guess Gemini 4 now.
Jokes on me if Codex refuses right out of the box, so I'll start low on the usage tiers and slowly upgrade as it proves it can be trusted to continue the work.
Someone on Reddit made a good point. Even a short fence stops most people from treading on your lawn.
In other words, people who try to divide and conquer recompilations will likely still succeed... for now.
I've been doing that and it seems like quite a deal.
Seems like the doors are (slightly?) open right now. OpenCode just announced that users can use their Claude subscription:
- https://x.com/opencode/status/2116198602523513081
- https://github.com/anomalyco/opencode/pull/58782#issuecommen...
Claude seems to have higher limits by default instead of playing the random reset games.
In a world where subscription value isn't obfuscated by unlimited chat, the choice for a power user is obvious, especially since it took a month after Sonnet 5.5 for OpenAI to get Terra 6.1 out, using Sol for everything just ate through the limits.
Multi-agent is mostly dead. One big agent loop running GPT6.1 absolutely dominates any weird ideas like this now. I still use sub agents for some tasks where I want to compress the action space and context. For example, testing a workflow that requires 100+ tool interactions for each logical test. Without a subagent it's really hard to guarantee a test makes it E2E. I have some very "persuasive" methods for long horizon tests that would break the main loop's dynamics.
We may not feel so compelled to exploit the system if we could figure out how to not be so wasteful. Multi agent schemes can bloat token usage by orders of magnitude. They force us to consider consuming less ideal tokens from contexts and vendors with higher variance.
HN loses its marbles when I suggest it's economically feasible to prepay for API tokens and use these as the exclusive means of performing AI work. I get done with a thousand tokens what my peers cannot do with a million. It doesn't matter how many hammers or workers you have if you don't have the aesthetic preferences and domain expertise to employ them correctly.
Wow that's a huge take. Seems like you're on your own with this one.. everyone I know is scaling up the number of agents they're able to keep fed with good, useful work.
Only you can decide if that speed is worth the cost.
I agree. It's possible future AIs will be able to salvage those code bases though.
/code-review <PR#>
versus
Review the changes in <branch> against <base>. Verify your finding and offer the fixes if the finding are valid.
Then, your LLM code reviews will never call this out. You have to look at the code yourself and correct it. If you don't, this type of monkey patch engineering will proliferate and make your codebase so awful that your successor will become a homicidial maniac.
That said, you're correct that even the code reviews often need to be triple checked before they are worth anything.
Anyone whose buainess wont be competitivw without a cloud model is going to lose their business.
Any government letting cloud models consume its private infrastructure is yielding its authority to private intetests.
In the US, that’s considered a feature.