[PR #133] [MERGED] [docs] Explain why the download walk uses small listing pages #138

New issue

Closed

opened 2026-10-13 19:47:52 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-13 19:47:52 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/Glitchy-Sheep/boosty-downloader/pull/133
Author: @Glitchy-Sheep
Created: 8/9/2026
Status: ✅ Merged
Merged: 8/9/2026
Merged by: @Glitchy-Sheep

Base: main ← Head: fix/listing-page-size

📝 Commits (1)

8c2d547 docs: 📝 Explain why the download walk uses small listing pages

📊 Changes

2 files changed (+12 additions, -0 deletions)

View changed files

📝 boosty_downloader/src/infrastructure/boosty_api/core/client.py (+4 -0)
📝 docs/concepts/boosty/download-flow.md (+8 -0)

📄 Description

Summary

Signed media links live 24 hours from the listing fetch (measured live), so the sequential download walks in small pages of 5 to keep links fresh, while metadata-only walks (check, post search) use pages of 100. This was undocumented and one comment away from a well-meaning "optimization" that would multiply link expiry failures on big video channels. A new section in docs/concepts/boosty/download-flow.md and a comment on the client default capture the reasoning.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/Glitchy-Sheep/boosty-downloader/pull/133 **Author:** [@Glitchy-Sheep](https://github.com/Glitchy-Sheep) **Created:** 8/9/2026 **Status:** ✅ Merged **Merged:** 8/9/2026 **Merged by:** [@Glitchy-Sheep](https://github.com/Glitchy-Sheep) **Base:** `main` ← **Head:** `fix/listing-page-size` --- ### 📝 Commits (1) - [`8c2d547`](https://github.com/Glitchy-Sheep/boosty-downloader/commit/8c2d54713b8d577b7ae7fcce0e8a472567f82326) docs: :memo: Explain why the download walk uses small listing pages ### 📊 Changes **2 files changed** (+12 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `boosty_downloader/src/infrastructure/boosty_api/core/client.py` (+4 -0) 📝 `docs/concepts/boosty/download-flow.md` (+8 -0) </details> ### 📄 Description ## Summary Signed media links live 24 hours from the listing fetch (measured live), so the sequential download walks in small pages of 5 to keep links fresh, while metadata-only walks (`check`, post search) use pages of 100. This was undocumented and one comment away from a well-meaning "optimization" that would multiply link expiry failures on big video channels. A new section in `docs/concepts/boosty/download-flow.md` and a comment on the client default capture the reasoning. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-13 19:47:52 +00:00