I have been a paying ChatGPT subscriber since GPT-3, and I have been a loyal user for years. That loyalty is not infinite. There are plenty of strong models now, and this usage cut is nauseating — it has materially wrecked how I work. If you cannot be honest with the people actually paying you, I can take my work elsewhere. Until there is a credible explanation or a real fix, I am cancelling my subscription.
@elonmusk Grok is getting better. Mr. Musk, you shouldn't let those overwhelming, colossal, staggering, torrential, innumerable free accounts ruin Grok. I just subscribed to SuperGrok Heavy for a week and already started hesitating about whether to renew next month. Please fix this.
@thsottiaux genius growth loop:
1. ask people to tweet about Codex
2. pay them in credits
3. delete the campaign
4. zero the credits
we didn’t switch to Codex. we got A/B tested.
next time just invoice us for the tweet.
@thsottiaux hit 'Selected model is at capacity' halfway through a Codex task. Reset does nothing. Extra usage quota is useless when the model servers are full. This breaks serious long sessions. Please fix the capacity issue.
@thsottiaux Codex is fantastic, and really appreciate the generous usage allowance. That said, there hv been far too many usage-limit resets lately. If the goal is genuinely to benefit users rather than make this a marketing gimmick, why not remove the time restriction on resets altogether?
Big respect to 5.6sol for the rigorous, hard work that actually delivers useful results instead of getting in the way. Claude had the potential. Their dumb approach lost users like me.
@thsottiaux@thsottiaux Not sure what's going on lately, but Codex has been hanging a lot for me these past two days. In some cases it gets stuck forever with no output, and sometimes it freezes while compacting context. Curious if this is a known issue on your side.
@thsottiaux no! it's not!!! Still encountering server_error on Codex after sending requests.
Error returned:
{"type":"error","error":{"type":"server_error","code":"server_error"}}