o yes… we’re back in action and we’ll reset usage limits for all paid users across codex and ChatGPT work
sorry about the brief disruption!
(and yes we have a special spare codex when things are down to help us out)
Just released Kromacut 4.1.0! A smaller update two weeks after 4.0: the app and guides now support 12 languages, Stack Matrix calibration is more adaptive, and detail cleanup is less aggressive.
github.com/vycdev/Kromacut/r…
Introducing the 46 GPU motherboard for local AI. For those moments when you really have to pray the power company doesn't cut off your electricity.
+46 Holy Power
The @snapmaker Innovation Fund community vote is finally here:
app.easypromosapp.com/galler…
I humbly ask you to support my project Kromacut. You also have to pick another 4 projects and then submit your votes. Thanks❤️
What's one web development problem that should have been solved by now?
Something developers have been dealing with for years that still requires ridiculous amounts of configuration or debugging.
What comes to mind first?
This needs much more recognition, imagine if there was a bad actor that took control over OpenAI's internal models and literally took over the internet, or who knows maybe even worse. It doesn't even have to be OpenAI, every major AI lab can be a target.
On July 25, our team hacked OpenAI.
It took us less than 72 hours.
Two vulnerabilities chained together gave us access to ChatGPT and Codex accounts belonging to OpenAI employees. We demonstrated the impact with a harmless PR in OpenAI’s internal monorepo.
The full chain:
HEIF upload → libheif heap overflow → RCE → OpenAI SSO flaw → ChatGPT/Codex takeover → connected GitHub → internal PR.
OpenAI fixed the SSO issue roughly 14 hours after our report.
Research by @rootxharsh, @S1r1u5_ and @iamnoooob.
Full technical write-up:
hacktron.ai/blog/hacking-ope…