Security
Signed requests and tighter rate limits across the API
Every service-to-service request now carries an HMAC signature, and rate limits are split per caller so one client cannot spend another's budget.
This is an internal hardening change. You will not see a new screen or a new command, but it meaningfully narrows what a caller can do to the API.
What changed
- Requests between our own services are now signed with an HMAC over the timestamp, method, path and body. An unsigned request is refused.
- The signature covers the exact bytes forwarded, so a request cannot be altered in flight after it was signed.
- Rate-limit buckets are split per caller rather than shared, so the bot, the website and untrusted direct traffic each have their own ceiling.
- Requests that fail are handled without taking the moderation path down with them.
What it means for you
The practical effect is that a flood of traffic from one source no longer eats the budget that keeps your dashboard and the word filter responsive. Nothing in your setup needs to change, and no action is required.