Lol, this post is number one on the leaderboard on the “filtered” list list. Trusting ai slop to filter out ai is as ironic as it gets.
32,237 karma · joined January 3, 2008
(I always upgrade projects by first upgrading the runtime and checking everything then separately (and maybe much later!) upgrading the framework.)
Not just prose. I think this is part of the reason why you see ridiculous code with insane error handling and type checking even for impossible cases.
But I think they don’t tell you because they sometimes use residential proxies to scrape search results the same way they used residential proxies to scrape the web.
This has two implications:
1) make sure if you use Postgres for anything beyond core rdbms functionality that there is no dependency between the two, so you can rip out the additional functionality and move to a different platform when you end up needing to reduce the load on your db server
2) if using Postgres for non-essentials complicates your db backup workflow, risks the data integrity, makes it difficult to maintain or upgrade your Postgres instance (eg you have to wait months or years for compatibility with newer Postgres versions), or loads relatively shoddy or unstable code into the beating heart of your application, then you should either use a different Postgres server/install/container for these ancillary services or bite the bullet and introduce an alternative dependency, depending on which makes more sense.
https://github.com/openai/codex/issues/29353
What even is the point of a public-facing bug tracker “for devs, by devs” when this is how reports get treated? Might as well use Apple’s Feedback Reporter that routes to /dev/null instead.
Anyway, I find it near impossible to see how this wasn’t already caught and flagged internally – it’s not a subtle pattern. Certainly they are at the very least collecting and graphing reasoning tokens vs model vs effort” and such an obvious spike at (multiple) single stops (not even distributed over a narrow range) should have been an immediate statistical red flag… which leads me to believe (combined with the fact the previously reported issue was closed without comment) that they’re at least internally aware of this behavior even if it’s not necessarily an intentional side effect of some internal forcing metric.
To me that means “it’s an inferior product but marketing dictates we try and hide that.”
And “our most robust safety stack to date. We strengthened protections for higher-risk activity, sensitive cyber requests, and repeated misuse, and spent multiple weeks finding weaknesses, pressure-testing our system, and hardening it against real-world attacks” is of zero value to me at best, and most likely to my detriment (increasing refusals or nerfing utility). Why do providers keep leading with that? Are there customers (besides support ChatGPT chatbot users, maybe??) that ask for this?
But test coverage of unsafe blocks is not a meaningful metric. The best automated solution is standalone Miri runners exercising all branches of the code (via tests or otherwise) because tests on their own won’t catch things like out of counts reads or heap corruption unless you get lucky.
Separately, sorry to nitpick, but while wide gamut colors with only eight bits of data have lower resolution than sRGB, that doesn’t make them an inferior option. You might not be able to specify the exact shade but a) your effective accuracy is still greater and b) you trade that for greater range.
Just as an example, assume you have buckets of granularity 1 (sRGB) and 0.5 granularity (wide gamut). With only eight bits you can precisely select any individual bucket of granularity 1, whereas with only eight bits you sometimes miss the intended wide gamut 0.5 precision bucket and hit its neighbor instead (as if you had a granularity of 1 in this specific worst case). That doesn’t make it worse; you just aren’t taking full advantage. On top of that, your range with granularity one is, say, 200 to 800 while your “range” with the wide bucket is 0 to 1000 (just as an example).
There’s a reason photos or graphics saved as eight-bit png or jpeg still manage to look ten times better in a wide gamut profile than in sRGB (on a better-than-sRGB display).
Hyundai (the chaebol) has no such policy. They sell their heavy equipment to oppressive regimes to blatantly use in projects and efforts deemed illegal under international humanitarian law and by the International Court of Justice.
I regret giving this article a chance and wasting my time trying to figure out why the “author” was saying what they were saying. Flagged.
Compilers literally made your project possible!