zib/Veskslop-t
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Resume paused scrapes from their cursor

Browse Source
This commit is contained in:
Fisto
2026-09-17 00:14:57 +02:00
parent 089bca0d4f
commit 0664b54241
10 changed files with 110 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CURRENT.md
+5
View File
@@ -40,6 +40,11 @@ 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] C34 Resume from cursor. A paused scrape can continue where it stopped instead of
re-walking the top: `POST /api/media/scrape/resume`, MCP `resume_media_scrape`, and a Resume
button in History. Previews never needed the walk — backfill fetches them straight from the
stored URLs; the walk is only for discovery. Live: the paused `gernal_chut` scrape resumed at
cursor `365256427247239181`, fetched its final page, and entered the preview pass.
- [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