A reader tab left open on one device (or restored by the browser) used to
save its old chapter as the newest position as soon as it was shown again.
Progress saves now carry the tab id and the newest progress time the tab
knows (`seen`); the server refuses a save when another tab or device saved
a newer position since. The reader then asks: jump to the newest position,
or keep reading here (which makes this chapter the head again). It checks on
open, when the tab becomes visible, and on every save. Reader links carry
`at` and the reader keeps it in the address bar, so reloads and restored
tabs still know what they had seen.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Zero-dependency Node server + plain HTML/JS frontend.
- Library is a folder tree (Manga/Book/Chapter/pages), indexed in place;
page roles (cover, double, extra, rotation) are file name tags
- Accounts with per-user progress, reading settings, follows and
new-chapter notifications (in-app + optional webhook)
- Reader with Flow, Page and Book modes, pointer-anchored page zoom,
tap zones, auto-hiding controls, chapter picker, page preloading
- Multiple versions per chapter with community votes
- Docker image and compose file
- Demo library generator (tools/make-dummy.js)
- Docs: architecture, library format, import, scraper guide
MaashkinoozheandClaude Opus 5.5