Honestly, I’m a bit relieved that OpenAI is at least trying to intervene here. When I heard they backtracked and re-released 4o, alarm bells went off for me that they were going to give in and just rake in profit off this type of dangerous AI addiction. Sounds like at least some of that original non-profit “managing the future of AI” concern is still there, if obviously far less than I’d like.

At this point, my assumption whenever I see heavy handed RTO orders like this, is that you’re seeing disguised layoffs.

Don’t want to spook the stock market, but still “need” to cut people to show profit “growth” this quarter? Just be such a massive ass to your employees that a ton of them quit. It’s that easy.

Might be a good use case for Anubis, in addition to the URLParam passwords mentioned elsewhere. Enough protection to prevent trivial brute force scraping, while also being basically invisible to users.

Ugh, this is what our legacy product has. Microservices that literally cannot be scaled, because they rely on internal state, and are also all deployed on the same machine.

Trying to do things like just updating python versions is a nightmare, because you have to do all the work 4 or 5 times.

Want to implement a linter? Hope you want to do it several times. And all for zero microservice benefits. I hate it.