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

Sign-in: verification instead of a per-account limit, and queued password checks

  • github
  • github/openchronology/timeline-app
  • commit
  • main
  • github/athanclark

Repeated failures for an account now ask each further attempt for human verification (or, with CHALLENGE_PROVIDER=off, delay it by 1.5 seconds) instead of refusing every sign-in for that username, so its owner can always still sign in. Directory sign-in follows the same rule; linking a directory account is limited per account and per address. The per-address limits are unchanged. Password checks share a per-process pool of slots sized from the CPU (one per core, at least two, below libuv's worker threads), set with PASSWORD_HASH_CONCURRENCY. A check that finds them busy waits in line for up to five seconds before 503, rather than being refused at once. Unknown usernames still do the same work through the same line, so timing is unchanged. A password reset link is checked before any hashing. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/074676df1e793f77b29ec303df9a4584c4c7c326

Open Sign-in: verification instead of a per-account limit, and queued password checks in the timeline

Sign-in: verification instead of a per-account limit, and…