Changelog
Subscription confirmation limits
Shipped
Coverage-alert signup gained a two-sided rate limit, so neither a single address nor a single sender can be used to generate confirmation mail in volume.
- Per-address and per-source limits on subscription requests.
- Confirmation remains required before any alert is sent to an address.
This log records only changes that are already live on this site. It is not a roadmap, it does not describe work in progress, and an entry is added only once the change it describes is running.
Questions
Common questions
What counts as a change worth listing here?
A change to what readers or API callers can see or do: a new page or endpoint, a change to how a figure is derived or labelled, a change to published limits, or a change to how the site's evidence is retained. Internal work that leaves the published surface unchanged is not listed.
Does this log include planned work?
No. An entry appears only after the change is live. There is no roadmap on this page, and no entry describes something that has not shipped.
What date does an entry carry?
The date the change went live on this site, taken from the deployment record. It is not the date the work started or the date the entry was written.
Does a changed figure appear here?
No. Figures change as issuers publish and as chains are read, and a correction to an already-published figure is recorded on the revisions page, which keeps both the superseded record and the one that replaced it. This log covers changes to the site and the API themselves.