a little bit of this, and a little bit of that

Chicago, IL
Joined November 2007
A reply personified in a structure jsonified from tokens classified by an algorithm amplified with hardware commodified in a world forever unsatisfied
9
4,261
not openai
What’s cooking today
1
3
76
have you considered complex passwords, 2fa, and physical security keys?
my personal accounts are being attacked now too whole new world with ai powered hacking
3
168
BROkenCode oy vey
🚨 Confirmed. OpenCode hacked. Keys stolen. Telling customers to revoke.
1
2
318
lol
Day 12/ We’ve made improvements to Codex & Work that increase the effective usage you get. We achieved this by reusing context across subagents, keeping context cached longer, and improved request routing that allows us to increase cache hits.
40
Happy birthday FORTRAN!
1
37
lol
Day 11/ We've landed a series of changes and more compute to very significantly decrease the occurrence of the disruptive "Selected model is at capacity. Please try a different model". When it does happen, it should also eventually just continue by itself and not just block on it. Let us know if you still see it out there in the wild and we'll take a look.
1
53
"cake or death"
Pro users, would you rather have
33%5h limits, 2X week usage
38%no 5h limits, same usage
29%show result
240,643 votes • Final results
40
hate crustaceans? krill issue
hate pickles? dill issue
2
1
93
🤣
Day 5/ Composer predictions in the desktop app. Often leads to a double take with how on point they are. Included in the Pro plans without consuming usage.
41
illuminati confirmed
31
lol af
Day 4/ We have improved steering to be instant, leading to the model now reacting much faster to adjustments you make, allowing you to course-correct direction in realtime and not have the model waste effort. Also releasing GPT-6.1 Sol ultrafast. The two work very well together.
1
105
Remember when LLM's started responses with 'EXECUTIVE SUMMARY' lol
28
Weird. I had Mac mini GitLab runners setup in an hr a year ago
Day 2 of getting GitHub runners working on my Mac Mini 24/7 AI code factory
1
4
163
Not the fifty percent I wanted back
Day 1/ We have optimized the default speed to be ~50% faster across GPT-6 Astra and GPT-6.1 Sol through the subscription across all our products and partners using Sign in With ChatGPT (including OpenCode, Pi, Amp, Devin, ...). No changes needed on your end and this should be felt within the next two hours.
67
Interesting, another incorrect take.
If you want to know who survives AI, look at what happened to Hollywood in the 1970s. Movie Studios used to enforce tight “shooting ratios”; usually 5:1, maybe 10:1 TOPS. As in, for every 5 feet of film shot, at least 1 foot had to end up in the final cut (35mm was expensive!) In the 70s, there was a rapid elimination of production constraints. Improvements in film cost and camera portability made the old studio rules…obsolete. Why not take multiple angles, roll simultaneously? Set could have 3, 5, even 10 cameras rolling at once. Shooting ratios *exploded*, 50:1, even 100:1 (Apocalypse Now)! Of course, it also *radically* changed the workflow. Editing use to be the quiet, thankless job in the studio years (30s-50s). Suddenly, they became the most important people on the totem pole! How do you find the masterpiece hiding in the (literal miles) of film? A ton of the footage was…trash, of course. But as each individual camera because *less* important, it opened up directors to take on significantly higher risks. Now, don’t get me wrong. Insane shooting ratios were still *kinda* a niche in the 70s. More traditional directors stuck with only slightly inflated shooting ratios (15:1, 30:1 common); it was the more experimental pioneers (Coppola, Scorsese, etc) that hit the big 100:1 numbers. The huge ratios were still crazy. Until they weren’t. You can probably guess what happened in the early 2000s. Digital cameras reduced the cost of individual footage to a complete non-constraint. Effectively free, don’t even cut on set, just keep the camera rolling. Suddenly…*EVERYONE* starts shooting 100:1. Entire new forms of content get created, like Reality TV, where ratios can hit 500:1! Massive shift of human labor to the editing side. I’d say, we’re currently in the “1970s Hollywood” of AI. It can be easy (and cheap!) to produce things (code, tools, etc), but YOU have to be the ruthless editor. It’s the “miles of film” problem all over again. Hollywood solved it by throwing massively more resources on the editing side, and editing became a “constantly talking with the director about vision/direction” job, instead of a “hide in the back office and do your work” job. It’s a hunch, but I’d bet that filmmakers closer to the experimental 1970s “ratio explosion” directors handled the later 2000s digital shift *much* better, because the underlying principles were the same. They’d certainly be ahead of the curve predicting it, and (hopefully) were less surprised when the digital ratios did hit. I’m not saying AI is exactly the same problem. But it’s a good idea to look at parallels in history where rapid elimination of constraints changed an industry, and how that industry handled it 5, 10, even 50 years later! When something starts to get cheap…helps to imagine what would happen when it’s free!
1
4
161
I've literally been on sets since the influx of digital cinema -- As a digital imaging technician no less. In fact, I'm on one as I type this right now. I've handled and seen every frame a director shot. There is so much that is untrue, I wouldn't even know where to start.
1
47
How about putting the max 20 plan back Mr deaf ears
Over the next 28 days, each day we’ll either ship one thing that is a clear improvement and relevant for most codex/work users or ship a full reset. Let the improvements begin.
40