circagraph
Sign inSign up

openchronology/timeline-app on GitHub

The OpenChronology repository on GitHub, mirrored by och-import-github: issues and pull requests as durations (ongoing while open), what happened to them as moments, plus releases, milestones, commits and branches. The Branches view shows the most recently active branches each in a track of its own.

Source: https://github.com/openchronology/timeline-app

3,131 moments · 2026-10-05 CE 20:21:49 UTC – 2026-11-16 CE 12:10:45 UTC · by @athan · @athan

#524 Harden the server against anonymous load and small leaks

–

  • github
  • github/openchronology/timeline-app
  • github/openchronology/timeline-app#524
  • pull request
  • state:merged

Closes #503. **Request bodies:** - **Per-route limits:** routes anyone may call now take only what they need. - **Device sign-in and OAuth start:** 1 KiB. - **Timeline queries:** 1 MiB + 64 KiB, because an overview may carry a comparison's plugins. - **Saves and imports by signed-in accounts:** 16 MiB, as before. - **Early refusal:** a too-large `Content-Length` is refused before reading. - **Nesting:** JSON nested more than 128 levels deep is refused before it is parsed. **Limits on anonymous work:** - **Queries without an account:** 600 a minute per address, counted before the body is read. - **Separation views:** a filter keeps only the tags the timeline has. A filter that matches nothing reads the timeline's own index or one shared empty view, rather than building a new one. - **Building a view:** limited to 20 a minute per address for guests and 60 per account, and to two at once per process with up to 16 waiting (503 beyond). Views already built are served without the limit or the queue. **Smaller fixes:** - **Proof of work:** answers to the human-verification challenge are bound to the salt exactly as issued, so one challenge gives one answer. Existing clients are unaffected. - **IPv6 rate limits:** per-address limits count IPv6 clients by their /64, and IPv4-mapped addresses as IPv4. - **Resolving an address:** an address with no timeline and one with a private timeline get the same answer. - **LDAP:** the sign-in filter keeps a username's characters as typed, `$` included. **Tests:** - **Unit:** `http.test.mjs`, `auth.test.mjs`, `challenge.test.mjs` and `ldap.test.mjs`. - **PostgreSQL:** `views-postgres.mjs` and `timeline-links-postgres.mjs`. - **Passing locally:** all unit tests and the PostgreSQL suites for views, links, challenges, browser forks, LDAP, OpenAPI, passkeys, account security and relationships. **Docs:** `docs/administration.md`, `docs/authentication.md`, `docs/tags.md`, and the OpenAPI description (the new 413 and 503 answers). 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/pull/524

Related

Open #524 Harden the server against anonymous load and small leaks in the timeline

#524 Harden the server against anonymous load and small…