Darkassassin07

You won't find a lot of popular, unencrypted content these days on usenet. It's all encrypted and obfuscated now to avoid the bots

That's not been my experience at all. Pretty much everything I've looked for has been available and I rarely come across encrypted files. I do regularly have to try 2 or 3 nzbs before I find a complete one, but I almost always find one.

2 main advantages:

• no hosting liability. Unlike torrents; you're not seeding ie hosting the files yourself. You're purely downloading. This moves you out of the crosshairs of copyright holders as they are only interested in the hosts (providers). This also means a VPN is not necessary for usenet downloading. (providers don't log who downloads what either)

• speed. As long as the content is available (hasn't been removed due to dmca/ntd), you are always downloading at the maximum connection speed between you and your provider. No waiting/hoping for seeds and whatever their connections can provide. I'm usually at around 70mb/s. Where as torrents very very rarely broke 10mb/s for me, usually struggling to reach 1mb/s.

As far as availability goes, stats from my usenet client: of 17m articles requested this month, 78% were available. I'm only using a single usenet provider. That availability percentage can be improved by using more than one in different jurisdictions (content is difficult to remove from multiple servers across different regions).

You'll need 3 things:

A usenet client such as SABnzbd. This is equivalent to a torrent client like qbittorrent.

An NZB indexer such as NZBGeek, again equivalent to torrent indexers, but for nzb files.

And finally a usenet provider such as FrugalUsenet. This is where you're actually downloading articles from. (there are other providers listed in the photo in my other comment here)

Articles are individual posts on usenet servers. NZB files contain lists of articles that together result in the desired files. There are also additional articles included so if some are lost (taken down due to dmca/ntd) they can be rebuilt from the remaining data. Your nzb client handles the process of reading nzb files, trying to download the articles from each of your configured usenet providers, then decompressing, rebuilding lost data, and finally stitching it all together into the files you wanted.

Yeah, pretty much.

They do receive takedown notices, however files uploaded to usenet are mirrored across many providers across many jurisdictions while also split into many parts as you noted. Usenets implementation of file sharing is quite robust; being able to rebuild a file that's missing a significant portion of it's data. To successfully take down a file, you need to remove many of these parts across almost all of the usenet backbones which requires cooperation across many nations/jurisdictions that are governed by varying laws. It's not an easy task.

Here's a somewhat limited map of usenet providers:

Who lets randos into their wedding?

It's real generous of these states to boost business for VPN companies like this

Was gonna say, I only use IMDB lists and I've got like 12 of them monitored. You can definitely use them in sonarr and radarr.

Sure there's occasionally issues with source media or how it was imported, but the big difference: I can fix problems with emby/plex. I can correct messed up metadata, or run a partially corrupted file through a converter to fix it, or just replace files entirely; all in a few minutes. (and none of these I have to do very often. Like one or two files a month, while constantly adding new content daily)

Most of the problems paid streaming services have, just have to be delt with until the provider gets around to fixing it, if they ever do at all. Then you add on content being scattered across 10 different services, artificial quality limitations, tracking, lack of or very poorly implemented offline playback, the inability to share with friends/family, advertising (now even being added to services built-on being 'ad-free'), the list goes on...

As a note: I use Emby and have never had an issue losing my watched position and have only had maybe 1 in 1000 items incorrectly identified (out of a library of 4k movies and 34k tv epps).

Been running openVPN as an always on VPN for stock Android for about 2 years now. Keeps it behind pihole and able to access my LAN only services.

The only issue I have is manually having to tell it to reconnect when the device restarts. Other than that it's been no different than no vpn.

Yes, typically the proxy will listen on 443/80 and all the services it proxies to just use their defaults.

For example: emby.example.tld, port 443 > cloudflare, port 443 > your reverse proxy, port 443 > emby, port 8096

All the client sees is emby.example.tld on port 443 and the resulting web application, everything in between is transparent.

Accessed from the same port.

Each service runs/listens on its own port, including the proxy (typically 80/443). When you connect to the proxy using its port, it will look at the domain name you used and proxy your connection to the port for the service that name is setup for.

So when you go to expose these to the network/internet, you only have to expose the port the proxy listens to and the clients only ever use that port regardless of how many services/domains you host.