ResetCat / Site sections
Sourcing and freshness
This page documents where the records come from, how they are classified, when they stop being treated as current, and how corrections work.
Collection
The browser never contacts the upstream data provider directly. A same-origin endpoint fetches the selected public feed, validates it, normalizes it to the small contract this site owns, caches a successful response briefly, and returns explicit freshness metadata.
Validation and classification
A record is accepted only when it has a stable identifier, a known type, a parseable timestamp, non-empty summary text, a genuine source author, and an HTTPS link to the original announcement. Anything that fails validation is dropped instead of being repaired.
- Direct reset — an announcement of a reset applied to eligible accounts.
- Banked credit — an announcement of reset credit that can be used later.
Freshness boundary
A feed older than 12 hours is never presented as current. The dashboard switches to an explicit stale notice, and a feed that cannot be validated at all is presented as unavailable rather than silently reusing an old success.
Corrections
If a record is wrong, the fix is to correct or remove it upstream and let the next capture flow through. Because each entry keeps its original source link, you can always check the announcement itself.
Limitations
This site is independent from the data provider and from every product it writes about. It republishes only what a public source already published, and it cannot confirm anything that was never announced publicly.