3 Commits

Include renames

Author	SHA1	Message	Date
Daan MeijerandClaude Opus 5.5	41859636d3	Seed relay: nodes get their headers through the seed API ... The seed API keeps a pool of NNTP connections (SEED_NNTP_CONNECTIONS) and serves GET /api/v1/seed/ranges/:id/chunk?from=&to= for leased ranges: the gzip stream the news server sent, passed on unopened. seed:node fetches that way by default (SEED_FETCH=relay), so a node needs only a token and SEED_CONNECTIONS; SEED_FETCH=direct keeps its own NNTP connections. All fetching then comes from the indexer's IP (the account allows two). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-05 15:24:39 +02:00
Daan MeijerandClaude Opus 5.5	04f945055f	XoverClient times replies only, not idle time between commands ... A seeding node that waited over two minutes for the seed API (restarting) had its idle NNTP connection closed by its own timeout, and gave its range back. Now the timeout runs only while a reply is awaited. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-05 13:40:15 +02:00
Daan MeijerandClaude Opus 5.5	97bdf8e982	Seeding node: gzip overviews, batched SFV lookups, fragments beside fetching ... - lib/nntp/xover_client: a minimal one-connection client for seed:range with XFEATURE COMPRESS GZIP (a zlib stream after "224 … [COMPRESS=GZIP]", then a "." line; 420 for an empty range). About 6x less header traffic. Overviews come out with the field names nntp-js uses. - SfvService.claimAll: one sfv_entries lookup per stored batch. - Fragments go through the regular ingest path beside fetching (at most two batches in flight); a failure fails the run at the end. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-05 11:11:41 +02:00