I need to tread carefully in this introduction.<\/p>\n\n\n\n
If you found this article by looking for a beginners guide to Usenet, chances are you already know what it can be used for.<\/p>\n\n\n\n
In case you don’t, well: think of Usenet as a fast and reliable way of finding and downloading files from the internet. These files could<\/em> include copyrighted movies, TV shows and music files…but of course, don’t necessarily.<\/p>\n\n\n\n If you know what BitTorrent is, the end result is very similar \u2013 even though the mechanics behind it are different.<\/p>\n\n\n\n The difficulty with Usenet is understanding how on earth to get set up in the first place<\/strong>. Most guides are written for people with a technical background, you need to combine at least three different tools, and the websites of the tools themselves look like they’re from another era.<\/p>\n\n\n\n So: In this article, I’ll give you a totally practical and non-technical guide to getting started with Usenet. <\/p>\n\n\n\n By the time you’re halfway through, you’ll have it all set up for what you want to do \u2013 but have no understanding of why<\/em> it works or what’s going on. In the second half, I’ll give you that background and context in case you care.<\/p>\n\n\n\n Warning: This is totally non-technical, but you’ll still need to be a confident computer user<\/strong>. I’m not going to give you every last click-this-click-that, so you need to know how to install software and be able to Google anything that trips you up.<\/p>\n\n\n\n (Another warning: There are explanations here that I know<\/em> to be technically wrong or incomplete, and there will be other parts that are wrong without me even knowing. The point here is to get it working, not to be strictly accurate or comprehensive.)<\/p>\n\n\n\n What gives Usernet a bit of learning curve is it’s not a case of “download this and away you go”. You need to choose and combine three different services before you can do anything useful:<\/p>\n\n\n\n Let’s go through each and find out what they are, and where to get them from.<\/p>\n\n\n\n Your Provider owns the servers where the files you want are actually hosted. <\/p>\n\n\n\n All Providers require you to pay, because there’s a real cost to them in storing all the data. You can expect to pay somewhere from $10-20 per month, although many offer a free trial first. There are also lots of good annual deals available around Black Friday. <\/p>\n\n\n\n There are multiple different Providers, each owned by different companies, each with their own servers \u2013 and therefore each with a different set of files.<\/p>\n\n\n\n In theory, they all download each other’s files so every Provider will end up with the same set. In practice though, a particular file might get corrupted on one server or be taken down from another \u2013 so there are<\/em> differences.<\/p>\n\n\n\n For this reason, many people recommend signing up with two Providers:<\/p>\n\n\n\n To make life a bit more confusing, there are lots of different Providers — but many are just resellers (a bit like how Giffgaff ultimately runs off o2’s network, even though you seem to be dealing with a different company). If you’re not careful, this means you could sign up with two Providers that both actually access exactly the same underlying servers \u2013 which leaves you no further ahead.<\/p>\n\n\n\n This handy page<\/a> has a list of all the actually<\/em> different sets of servers (there are 13 at the time of writing), along with all their resellers. So just choose a different two from the 13, and you’re good to go.<\/p>\n\n\n\n I use:<\/p>\n\n\n\n The Provider hosts all the files…but they don’t give you an easy way of searching for the files you want. This is where the Indexer<\/strong> comes in.<\/p>\n\n\n\n Think of an Indexer as “Google for Usenet”. You type in what you’re looking for, and the Indexer gives you a list of results.<\/p>\n\n\n\n Just like there are multiple search engines that each return slightly different results, there are different Indexers too \u2013 although unlike Google, there’s no single dominant Indexer. For that reason, just like with Providers, it can be useful to have two or more Indexers to call on.<\/p>\n\n\n\n The best Indexers come at a cost. Very roughly speaking, they’ll charge an annual fee of $10-$20 or a lifetime fee of $30-$70.<\/p>\n\n\n\n There are also free Indexers, but these are sometimes closed for registration to control the number of users.<\/p>\n\n\n\n This page has a list of all the main Indexers<\/a>, both free and paid.<\/p>\n\n\n\n I use:<\/p>\n\n\n\n You have a Provider that has<\/em> the files. You have an Indexer so you can find<\/em> the files. Now we’re on the home straight: you just need to download<\/strong> those files.<\/p>\n\n\n\n For this, you use a free (finally!) piece of software called a Newsreader<\/strong>. The two most popular are SABnzbd<\/a> (which I use) and NZBget<\/a>.<\/p>\n\n\n\n (Their weird names will start making more sense in just a moment.)<\/p>\n\n\n\n The job of the Newsreader is to grab files from the Provider, so once you’ve downloaded the Newsreader you’ll need to plug in the details of the Providers you’ve decided to use. (You’ll also set an order of priority, so it’ll try your main Provider first and only try your “backup” provider if there’s something it can’t find.)<\/p>\n\n\n\n So, the workflow is:<\/p>\n\n\n\n Once you’ve set this up, you’re good to go: you have all the pieces in place to find whatever you want and download it.<\/p>\n\n\n\n You can also take things to the next level and add an “automation” step…<\/p>\n\n\n\n If you were<\/em> to use Usenet to download TV shows and movies, you could make life easier by automating the process of downloading new episodes \u2013 or in the case of movies, by downloading new ones from your “watchlist” when they become available.<\/p>\n\n\n\n To do this, you can use:<\/p>\n\n\n\n Taking Sonarr as an example, you basically just:<\/p>\n\n\n\n Sonarr then regularly checks the Indexers to see if something new has become available. If it has, it automatically downloads the NZB file and passes it over to the Newsreader. <\/p>\n\n\n\n Radarr works the same way for movies. However, it’s earlier in development so you need to be a bit more technically confident to install it successfully.<\/p>\n\n\n\n To have accomplished all this, you’ve not needed any technical understanding of what on earth is going on behind the scenes. However, having a basic knowledge of what’s really happening (which is all I have) will make certain things make more sense and will make it easier to troubleshoot when something goes wrong.<\/p>\n\n\n\n So feel free to stop reading here if you’ve got everything working and you don’t really care how<\/em>. But if you do want to read on, I promise it won’t be too intimidating.<\/p>\n\n\n\n Usenet actually predates the internet as we know it. Usenet hosts newsgroups<\/em>, which were the original online forums \u2013 places where people could post messages to discuss shared topics of interest.<\/p>\n\n\n\n As well as posting text messages, people started using Usenet to post files called binaries<\/em> as a way of sharing photos, videos and music rather than just text. <\/p>\n\n\n\n Binaries are files that are readable by computers rather than people. Binary files actually underlie everything we see online: for example, what we see as a photo of a puppy is actually a set of binary instructions that tell a computer how to display<\/em> a photo of a puppy.<\/p>\n\n\n\n The technical challenge is that the complete set of binary instructions needed to display a photo is long \u2013 so the file needs to be very big. A movie is vastly bigger again, as it’s basically tens of thousands of images stitched together.<\/p>\n\n\n\n Big files are hard to upload and download because they can easily fail in the middle of the process or become corrupted. So to upload a photo or movie to Usenet, people would split it into lots of separate binaries<\/em>.<\/p>\n\n\n\n To see it, you’d need to download each binary file separately \u2013 then use a special piece of software to stitch them all together again.<\/p>\n\n\n\n An NZB file removes all the manual work of finding thousands of component binaries, downloading them all, and stitching them back together.<\/p>\n\n\n\n It’s this NZB file that you download from your Indexer and give to your Newsreader.<\/p>\n\n\n\n So an NZB file is not<\/em> the movie, photo or whatever else you want. It’s more like a set of instructions for where to find the parts of that thing and put it together<\/em>. It tells your Newsreader where it needs to go, and what it needs to do.<\/p>\n\n\n\n You could think an NZB file as being like a set of instructions for building a bookcase. It might say “go to this store and find two big planks of wood in this section, six smaller planks in that section, and sixteen screws from this other section \u2013 then put them together like this”.<\/p>\n\n\n\n So when you plug this analogy into our three components:<\/p>\n\n\n\n Now you know what’s actually going on behind the scenes, you’ll have a better understanding of the most common problem when using Usenet to grab big files: missing pieces.<\/p>\n\n\n\n Just like a store can be out of stock of certain pieces you need for your bookshelf, a Provider can be missing some pieces of a bigger file too \u2013 either because they’ve been taken down, or have become corrupted.<\/p>\n\n\n\nPutting together the three parts of your Usenet setup<\/h2>\n\n\n\n
1: A Provider<\/h3>\n\n\n\n
2: An Indexer<\/h3>\n\n\n\n
3: A Newsreader<\/h3>\n\n\n\n
Putting it all together<\/h2>\n\n\n\n
Automating your Usenet downloads<\/h2>\n\n\n\n
The (semi)-technical bit<\/h2>\n\n\n\n
What is Usenet anyway?<\/h2>\n\n\n\n
What is an NZB file?<\/h2>\n\n\n\n
What can go wrong?<\/h2>\n\n\n\n