Collection and checks
On a schedule, we collect posts and replies from Tibo and other accounts on X, keeping each post's link and timestamp. We also read the public Codex reset history, and we use our own test account to check when usage resets and banked resets actually land. Every statement names its source.
Home page status
- If Tibo has posted an announcement since the last reset, it shows the announced timing (e.g. "Next week") and when the last reset happened;
- If a reset happened in the last 24 hours, it shows "Reset", the reset time and the original post;
- Otherwise, it shows how many days it's been since the last reset;
- If data updates are delayed, it shows when the data was last updated.
Estimates from history
When nothing has been announced and the data is fresh, the page shows an experimental estimate for the next 24 hours and 3 days. The baseline comes from past gaps between resets and the recent rate of resets. A limited hint from Tibo can add an adjustment that fades over time. Only one hint counts at a time, and it expires after 48 hours or when a new event arrives. This is a statistical estimate from past data, not an official forecast.
Who gets it, and when it lands
When an announcement names which users are included, the page shows those plans. Our test account confirms when a usage reset or banked reset lands, and that time is shown on the home and Codex pages.
Publishing
Collected and processed JSON goes to this site's data domain. The home and Codex pages reload it every minute; RSS, the calendar, history and event pages update when the static site is rebuilt.