Homelab Academy / Modules
Orient, prior check, guided practice, required Feynman, reflect.
Module: Download Clients & Indexers
Activity type: Lesson (Orient → Recall → Learn → Explain → Reflect)
Learning objective: Describe the roles of a Usenet provider, an indexer, an NZB file, and SABnzbd.
Bloom level: Understand / Apply
Last reviewed: 2025-03-08
Describe the roles of a Usenet provider, an indexer, an NZB file, and SABnzbd.
Explain how SABnzbd processes NZB metadata, communicates securely with Usenet providers, verifies and repairs article sets, unpacks completed downloads, and hands categorized results to other homelab applications. The lab builds and validates an isolated SABnzbd deployment policy without contacting a provider, downloading external content, installing software, or modifying files outside the class workspace.
Complete the module reading first:
Explain the workflow to someone who thinks an NZB file contains the requested download.
An NZB is more like a manifest than a package. It lists identifiers for many Usenet articles. SABnzbd reads those identifiers, asks a provider for each article, decodes and joins the pieces in an incomplete workspace, checks whether the reconstructed data is intact, uses PAR2 recovery information if enough is available, and optionally extracts archives. Only after those stages succeed does the result move to a completed category directory. The indexer produced the map, the provider stores the pieces, and SABnzbd performs the retrieval and assembly.
Can you explain why an indexer and provider are different services?
Can you explain why retention does not guarantee completion?
Can you explain why incomplete and completed directories must remain separate?
Can you explain why a backup provider should normally have lower priority?
Can you explain why verification does not prove that a downloaded file is safe?
Answers save in this browser (localStorage). Completing all five fields is part of the mastery unlock.