Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

I am no expert but I learned enough to set it up with my *arr stack and it's my primary ship for sailing the seas. My use case is English language popular content. So YMMV.

Search for the Usenet backbone map or usenet provider map. You will see that there are only a handful of companies providing different "backbones". Content may be different on different backbones and the copyright takedown notices may be different (DMCA or NTD).

I pay for an unlimited subscription from a provider on one backbone and purchased a couple of 500gb blocks (on sale) on another backbone. (A block is a one-time fee that allows me to download a specified amount of data, from a provider, and they don't expire).

My understanding is that content on Usenet is broken into multiple parts and the file names are obfuscated, making it more difficult to take down. If they are taken down, it might only be a few parts. Your download client can be configured to download the missing parts from multiple servers (in my case the blocks).

I don't recall finding something in my indexers that wouldn't download because of takedowns.

My recommendation would be to try it with blocks or the cheap €2 providers to see if you are happy. If you struggle to find content branch out.

I don't use VPN with Usenet. I don't want to bottleneck those sweet 500/600 Mbps download speeds. Never had an issue. Edit: because I setup the SSL servers)

Usenet is not the WWW. It operates on a different protocol and methods. It's not over HTTP(s) like this or standard web sites. Thus, your typical web user won't even ever see or notice anything on or about usenet. This is why you would need a usenet provider or access. You cannot access usenet with a web browser. One notable difference between the web and Usenet is the absence of a central server and dedicated administrator. Usenet is distributed among a large, constantly changing conglomeration of servers that store and forward messages to one another in so-called news feeds. Individual users may read messages from and post messages to a local servers.

Usenet is literally just a collection of text files on various servers or locations. There really isn't an index builtin or a way to just 'click to the next page'. This is why you need an indexer. An indexer crawls and scrapes usenet headers to allow searching and finding of specific content or posts. It automatically builds releases and indexes them like google indexes the internet.

When someone uploads files to usenet, it's just text. Very large files such as videos, aren't easily represented as text and don't "fit" in one post. It is spread over many different posts, sometimes hundreds. In text format. You could find all those posts, combine the text, and end up with an actual video or music file. But that file doesn't "exist" on usenet as a specific, single, item. Indexers find all posts associated with something you may be searching for, and other news reader software (like NZBGet or SABNZB) combine all those text files into one, giving you the file you actually expect after downloading all the different posts/parts.

Using a VPN account with usenet is beneficial, but not required. It is ideal to have access to multiple different indexers to find the posts you want.

For dutch content on Usenet, I can strongly recommend Spotnet. If you are familiar with docker, you will find a turnkey solution here to get you going with spotnet.

Short explanation (from Wikipedia): "Spotnet is a protocol on top of Usenet, providing a decentralized alternative to usenet indexing websites, and the NZB format in general. Spotnet allows users to create and browse private 'newsservers', or decentralized repositories of files and information. Members share spots (file sharing) with one another, similar to the seeding process in torrent sharing".

It has been a while since I used Usenet, so instead of giving you possibly out of date info I will just link to this FYFM section which has way more info than I can give.

In particular I found this guide to be fairly easy to follow.

As for using a VPN: it can't hurt!

Watching this post. I still don't fully understand how Usenet works.

Edit: deleting most of my comment because it's a duplicate from the person who answered hours ago, leaving my indexers comment.

Something that you didn't mention, but needs addressing - indexers. Yes, there are free indexers but they're often capped at a certain number of grabs per day. Expect to pay for access to these as well - but some have lifetime memberships at a reasonable price. Get more than one and sabnzbd can prioritize by user-assigned weight. (By the way,these are typically what gets hit by content protection/LE). Indexers provide the nzb files that tell you download client where in the providers' server to find the download bits/bytes.

The *arr stack works wonderfully with Usenet, I think if you go this route, you'll be surprised how little you have to fall back to torrents.

A VPN won't be useful because you'll have to login to the Usenet server. But (someone please tell me if I'm wrong) I've never heard of anyone getting busted downloading stuff from newsgroups.

Preface: I don't use Usenet

1. I've heard its a federated network, but you're paying for a subscription to a specific set of servers...as far as I understand.

2. People have been migrating to Usenet for a long time on top of being a very old protocol, so probably quite a bit. Worth a quick shot, right? As I understand, rights holders try pretty often but they can't really because the protocol breaks the data up so much that it can't be discovered from the outside.

3. Its not a requirement, but it doesn't hurt. Many providers bundle a VPN.

Hope that helps. I've never used it, but I always read posts about it and ask questions