Fetch message history through the client REST layer
This commit is contained in:
@@ -40,6 +40,13 @@ mobile draft at 390px.
|
||||
- [x] C11 preview caching: Discord-hosted image/GIF previews (WebP 320px, hash-addressed, 5 MiB
|
||||
cap, one attempt) run after every walk in both modes. Live run `...-20260916090722`:
|
||||
`previewed: 2`; thumbs served over `/api/media/<scrape>/<item>/thumb` (200).
|
||||
- [x] C33 Puppet history pagination. The core's `message.fetch` read the client store, which
|
||||
keeps only the newest messages plus the channel's first — every page was 10 messages and the
|
||||
walk stopped after one page (a 10-message, 4-media scrape of an ancient group with thousands
|
||||
of messages). It now fetches through the client's REST layer first (contiguous 100-message
|
||||
pages, `transport: "rest"`), store as fallback. Rebuilt and restarted the managed client;
|
||||
live re-run of channel `591000745164406784`: 21+ pages / 2,100+ messages and climbing, with
|
||||
hundreds of images/videos being indexed.
|
||||
- [x] C32 Group-chat clarity and puppet refresh. Group DM scrapes already worked (live-verified
|
||||
against the running daemon: `zıbb & fred` and a 1:1 DM, backend `puppet`, done, previews
|
||||
cached); the Group chat tab had shown an empty list while the core was offline. It now says so
|
||||
|
||||
Reference in New Issue
Block a user