Reset confirmed —
This copy lets you verify the source behind an advance warning and the later confirmation record. It was taken at capture time and does not change if the live post is edited or removed.
The live post no longer matches the fingerprint below. The archived text is unchanged and remains the basis of the classification; any forecast scored from it has been flagged for re-review.
How corrections are handledArchived post text
“As we are still investigating, I have reset everyone's Codex usage limits. This is a hard reset given some users had stacked up to three banked resets already that they can apply on their own schedule. Funnily enough, this week at OpenAI is called the RESET week, which is meant https://t.co/UdCSbW03QU”
Captured verbatim, including line breaks. Quoted replies and images are stored alongside but are not part of the classified text.
No Wayback copy was saved for this version.
What we did with it
Reset confirmed, scope Everyone. As we are still investigating, I have reset everyone's Codex usage limits. This is a hard reset given some users had stacked up to three banked resets already that they can apply on their own schedule. Funnily enough, this week at OpenAI is called the RESET week, which is meant https://t.co/UdCSbW03QU
Capture record
- Author
Tibo@thsottiaux- Source
- Public source post
- Posted
- Pacific time (updates to your time zone)
- Captured on
83844 minutes after posting- Last re-checked
- Fingerprint
- sha256:4e213c21b193eda802b11d46733e01a3133aa1d60bd4d36d2084a69cd688e7ef
- Stored copy
- Captured text
- Evidence id
- 2071381664853319742
- Event type
- Reset confirmed
- Language
- English (as posted)
The fingerprint is a hash of the captured text. The re-check queue runs twice an hour, oldest saved copy first, so each saved copy is compared about once a day; a mismatch raises the notice above rather than silently updating the record.