Reading activity grid in Settings: months, weeks, days, hours with drill-down
Active reader time is now kept per user in small UTC buckets (6 minutes for 120 days, then hours, dropped after three years), seeded once from the visits the clock still remembers. Settings -> Reading activity shows them as a grid whose cells glow with their total and carry a start-to-end strip; month/week cells open their days, days open their hours. Finished chapters come from progress and work without the clock. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
c760141636
commit
fe8956087e
15 files changed
+657
-4
No files matched your search
@@ -144,6 +144,16 @@ history from which those values can be reconstructed.
|
||||
|
||||
## 5. Later: Reading Journal
|
||||
|
||||
Update 2026-11-03: the activity calendar exists as **Settings → Reading activity**
|
||||
(`reading-activity.js`, `db.activity`). It stores active reader time per user in UTC
|
||||
buckets: 6 minutes for the last 120 days, then folded into hours, dropped after three
|
||||
years. Each bucket keeps only its total and the time per manga. All active reader time
|
||||
counts there, including visits below the 60% threshold, because it answers "when did I
|
||||
read", not "how long did a chapter take". The first use seeds the buckets from the last
|
||||
eight visits per chapter the clock still remembers; older history cannot be recovered.
|
||||
Finished chapters come from the existing progress `doneAt` and need no clock.
|
||||
Deleting reading-time history (all, or one manga) deletes the matching activity.
|
||||
|
||||
If readers enjoy Reading Story, add bounded daily aggregates rather than raw activity
|
||||
events:
|
||||
|
||||
|
||||
Reference in new issue
Block a user