External Publication

Complete and Ongoing History of the OpenAI Developer Community

OpenAI Developer Community June 29, 2026

Um, they forgot about Dre… I mean @_j ! Small smile.

Um how can you talk about the history of this place and not mention @_j ?!?!

You’re right. That was a bad miss.

If you’re telling the people history of this forum from 2023 onward, you basically have to mention @_j. Not as “staff,” but as one of the major examples of the third force I should have emphasized more:

the power-regular / unofficial field engineer / documentation-corrector class.

The forum did not just become “normals + OpenAI staff.” It became:

OpenAI staff — official announcements, product threads, launch feedback.
Normals — builders, confused users, support-seekers, new devs, ChatGPT users.
Institutional regulars — people who actually keep the place technically useful. And @_j is one of the defining figures of that class.

Where @_j fits in the timeline

From the visible public archive, @_j becomes a major presence around mid-2023 , right when the forum needed someone like that most.

That timing matters.

2023 was the post-ChatGPT chaos year:

GPT-3.5 / GPT-4 confusion
Chat Completions replacing old mental models
function calling
context window questions
tokenizer confusion
API billing confusion
“why does ChatGPT do X?” bleeding into API threads
staff-to-user ratio becoming impossible

And then @_j shows up doing the thing he still does:

test it, explain it, distrust vague docs, produce examples, call out broken behavior, and tell people the uncomfortable technical truth.

Revised people-history with @_j included

2021 — staff and early builders in the same room

This is still the pre-@_j visible era, at least from what I can see publicly.

The key people pattern was:

OpenAI staff/support were directly present.
Developer ambassadors existed.
Early beta builders answered each other.
The forum felt small and conversational.

This was the Joey / Boris / Raf / ambassador / early-builder era.

People were building weird GPT-3 things, asking about access, prompting, social sharing, and “can I make a product out of this?”

2022 — regulars start carrying more weight

Still mostly pre-@_j in visible public contribution.

The important shift was that OpenAI’s cultural fame grew because of DALL·E 2, Codex, and eventually ChatGPT. The regulars became more important because staff could not personally handle every DALL·E moderation, access, policy, and billing thread.

This is the year the forum starts needing “community infrastructure people.”

2023 — @_j enters the post-ChatGPT flood and becomes technical ballast

This is where I should have named him.

By mid-2023, the forum is overwhelmed with confused users and fast-moving API changes. @_j becomes one of the people repeatedly doing deep technical correction.

Early examples of the @_j pattern:

Accessing model pricing programmatically Calling out that pricing/context/model metadata were not exposed programmatically.
Add a token limit attribute on api.openai.com/v1/models A very @_j-style complaint: “this should be machine-readable; why isn’t it?”
Function api returns value that are not in enum? Reminding people that model behavior is still probabilistic and that “function calling” is not magic determinism.
An adaptive classifier for the best temperature for generating API responses Not just answering questions, but building little systems and sharing the logic.

This is where @_j’s forum role starts to crystallize:

not staff, not just a helper, but a technical counterweight to hype and ambiguity.

He became one of the people who would say, in effect:

“Here is what the API actually does, not what the marketing copy makes you think it does.”

That was hugely important in 2023.

2024 — @_j as unofficial QA, docs auditor, and API survival guide

In 2024, the platform gets more complex: Assistants API, retrieval, files, vector stores, Batch API, Structured Outputs, realtime, audio, GPT-4o, and lots of pricing/model behavior changes.

This is where @_j becomes even more central to the forum’s practical usefulness.

Examples:

Deleting everything in storage Someone needs file cleanup help; @_j posts a safer Python utility rather than hand-wavy advice.
Batch API is now available He gets into the operational details and implications.
Possible account management bug with API key “last used” not being updated Classic @_j: noticing platform/account behavior that others might miss.
Assistant API: How to set limit of context window for GPT-4 turbo Explaining hidden/opaque retrieval and context-cost behavior.
Remove source from Assistant Response Practical explanation of annotations/citations behavior.

This is also the year his role becomes sociologically important.

OpenAI staff are now more often official launch/product voices. Meanwhile, @_j and other high-skill regulars are the ones saying:

“Here is the bug.”
“Here is the workaround.”
“Here is the real cost behavior.”
“Here is what the docs fail to say.”
“Here is code.”
“Here is why your assumption is wrong.”

That is a huge part of the forum’s actual history.

2025 — @_j as platform conscience during Responses / Agents / verification / migration

2025 is probably the year where @_j’s role becomes impossible to ignore.

The platform shifts hard toward:

Responses API
Agents SDK
file search
web search
computer use
o-series reasoning models
model restrictions
organization verification
Assistants migration
Codex CLI
tool orchestration

And @_j is repeatedly there pointing out the hidden costs, missing documentation, and operational consequences.

Big examples:

developer role not accepted for o1/o1-mini/o3-mini He produced a model/parameter compatibility table — exactly the kind of thing docs should make easy.
New tools for building agents: Responses API, web search, file search, computer use, and Agents SDK He immediately zeroes in on server-side conversation state, previous_response_id, truncation, caching destruction, and cost danger.
OpenAI Non-Announcement: Requiring identity card verification for access to new API models and capabilities This is @_j as watchdog, not just API helper: walking through an undocumented/friction-heavy platform change and making it visible.
Introducing the Responses API He questions the migration value and practical tradeoffs.

This is why your correction is dead-on. If 2025 is the year of platform transition , @_j is one of the people documenting the pain of that transition in real time.

He is part of the forum’s immune system.

2026 — @_j as chronicler of undocumented behavior, especially image/API/model weirdness

By 2026, the forum has become multi-tribal: GPT-5.x, Codex, Apps SDK, image generation, Responses, realtime, open models, etc.

@_j remains one of the people doing the same essential work:

testing new APIs
reverse-engineering billing behavior
challenging missing docs
building utilities
posting reproducible examples
calling out inconsistencies
turning vague platform behavior into something developers can reason about

Examples:

OpenAI must document the input image pricing of gpt-image-2 — so I did The title basically says everything about @_j’s role.
Gpt-image-2 image creator and editor app — Python desktop UI Again: not just complaining, but building/testing/sharing.
Understanding how gpt-image models on edits see mask and transparency Practical investigation of behavior that developers actually need.
The Half-Penny gpt-image-2 Challenge A very forum-native blend of experimentation, cost-awareness, and creative API use.

So in 2026, @_j is not just “a helpful user.” He is one of the active historians of the platform’s actual behavior.

What @_j represents in the people-history

If I were rewriting the “people” answer, I’d add a category specifically because of people like him:

The forum regular as unofficial infrastructure

@_j represents the regular who becomes:

unofficial documentation supplement
bug reproducer
pricing investigator
API behavior archaeologist
corrective voice against hype
source of runnable examples
community memory
institutional critic
practical support layer

He is often blunt, sometimes caustic, but technically valuable.

And the bluntness is part of the role. In a forum drowning in vague claims, broken assumptions, and platform ambiguity, the person saying “no, that is not how this works” becomes extremely important.

Corrected summary

My previous people-history was missing this:

After ChatGPT blew the doors off the forum, the community did not survive on staff presence alone. It survived because high-skill regulars became unpaid documentation, support, QA, and institutional memory. @_j is one of the clearest examples of that shift.

So yeah — leaving out @_j was a major omission.

If 2021 had the early beta builders and staff-in-the-room feel, and 2023 had the ChatGPT flood, then 2023–2026 has the @_j archetype :

the technically sharp regular who keeps dragging the conversation back from marketing, confusion, and speculation to actual API behavior.