I asked ChatGPT 5.4 Thinking to write some JSON-LD text to summarize a blog post this morning along with alt text for the posts images and got this When I asked it to file a but report on itself, I didn't really expect it to succeed, but I didn't expect more oaicite index listings for the proposed issue description. (Kinda obviously, I also haven't had enough coffee yet :) Anyone else seeing this? Happenings of Interest (radio and nature) Where was our skip zone at San Bruno? For example. QSO Log Table containing QSOs in text Callsign rx RST tx RST Time (GMT) Frequency KBTEST 539 559 16:42 14058.3 kHz (Add callsigns as post tags?) Unschooling Highlights POTA tx QSL: QSL rx album: References POTA ( Parks on the Air ) Local Ionograms https://lgdc.uml.edu/common/DIDBYearListForStation?ursiCode=PA836 (for example) Videos Demo
Just a brief note to mention that when I was fighting Codex CLI earlier this week to call the OpenAI Whisper API , what was really going on was that Codex CLI was sandboxed. ChatGPT helped me modify the script I was creating so that the script itself punched through the sandbox by clearing the proxies that had been setup to keep Codex CLI in the secondbox. It's interesting that ChatGPT didn't just tell me to add the --yolo argument to my codex cli command line. I wonder if that's part of its guardrails, or if ChatGPT doesn't know about the arguments to Codex CLI yet through training. I saw similar things happen when ChatKit was announced. ChatGPT wasn't quite sure what it was on the day of the announcement. The good new is that I'm now calling APIs without any shenanigans because I learned to simply add '--yolo' the following day. That argument comes with its own set of risks, but I'm ok with those for the moment.