Overview
| Comment: | merge feed paging with trunk |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
0b79646346b1a6e00b2e0c4219d9e2f3 |
| User & Date: | dmestas on 2026-08-23 02:18:44.679 |
| Other Links: | manifest | tags |
Context
|
2026-08-23
| ||
| 02:34 |
paging: numbered pages, GitHub's shape
Infinite scroll out, a real pager in: page numbers with both ends pinned, position, and every page a bookmarkable URL. The feed pages by offset now (a page is a position, not a place you arrived from) and says how far it reaches — 264K events is not a pager, it is an archive, and that lives on each repository's timeline. check-in: 98f77c8273 user: dmestas tags: trunk | |
| 02:25 | merge doc-dirs: directory documents resolve to their index check-in: 9848396ba4 user: dmestas tags: trunk | |
| 02:18 | merge feed paging with trunk check-in: 0b79646346 user: dmestas tags: trunk | |
| 02:18 |
dashboard: the feed pages
A fixed window is a dead end for anyone whose repositories are busy. Cursor is date~hash, so the merged stream cannot repeat or skip where two events share a timestamp. Sentinel
| |
| 02:17 | merge doc-measure: prose at the measure, wide content at the column check-in: 9426c24e62 user: dmestas tags: trunk | |
Changes
Modified internal/web/web.go
from [e3053770d6]
to [02e98293b4].
[diff]
Modified internal/web/web_test.go
from [6ef1938a35]
to [0af0f2a29f].
[diff]