Automation

Getting started with Usenet is fiddlier than it needs to be, mostly because nobody writes down the whole pipeline in one place. This is that one place. Follow it top to bottom and you’ll go from knowing nothing to having a fully automated Usenet setup that runs itself — and stays stable when you start pulling hundreds of gigabytes a week. A quick honesty note up front: two of the four pieces of this pipeline cost money (a provider and, usually, an indexer). I’ve written the cheapest providers guide separately because “cheapest” and “how to set it up” are different questions. Here, we’re setting things up the right way first — including the UK-specific decisions that trip people up. ...

Once you’ve got a Usenet provider and an indexer (see the setup guide), the next decision is which downloader to run: SABnzbd or NZBGet. These are the two giants of the binaries world, and people argue about them like sports teams. Let me settle it for you with actual reasoning instead of tribal loyalty. Short version: most people should use SABnzbd. NZBGet is only clearly better in two narrow situations. Here’s why — and at the end I’ll dig into the large-transfer stability question, because on modern UK fibre that’s often the deciding factor nobody mentions. ...

You can buy the fastest, deepest Usenet provider on earth and still find nothing, because Usenet has no built-in search. Providers store articles; they don’t catalogue them in a way you can browse. Finding the specific binaries you want is the job of an indexer — and choosing the right one is often the difference between a setup that “just works” and one that’s forever missing files. This guide explains how indexers actually work, why paid and free ones differ by a mile, and — in the NZB quality and PAR2 section below — how the indexer’s output quietly decides whether your downloads repair cleanly or fail. If you’re brand new, read what is Usenet first, then come back. ...