Usenet is generally better for 0-day and recent releases, but it doesn't hold a candle to P2P when it comes to older stuff. What's the max retention you get with the most premium plan with reputable providers these days? I think it was 13 years last time I checked. But aside from that, it's almost always faster than P2P (unless you have a bad connection to the server from your location) and certainly more convenient in certain categories like movies and TV shows. I still use P2P for games, software, and music though.

Edit: Forgot we were talking primarily about security. Of course Usenet is better in that regard as well. The other replies explain why that's the case.

Didn't try it for software, only Movies, Shows, Games, Audiobooks

I am on houseofusenet and the "should not be named" partner indexer that allows API access for *arr Software.
Also i have drunkenslug

I rarely search for something manually, only games as there is no "gamearr" or something like that.

I have also heard that you can bind your hypothetical torrent client to your hypothetical VPN network interface meaning it would be unable to even send out any data if the VPN was not connected.

Or in the case of docker use a prepackaged VPN+Torrent container or pipe all container network traffic through a VPN container like gluetun

I have also heard uploading (seeding) is where you really get in trouble

Which is interesting since modern web standards make it possible to exchange data peer to peer in browser. Isn't PeerTube working this way? So you might not even know you are sharing. How does it work in such situation?

So there’s… Uhh… Quite a bit wrong with this.

I have heard people use reputable VPN’s like Mullvad, Proton, etc. for daily usage to obscure their traffic/IP… protect ourselves from malware (a side benefit many VPN’s).

A VPN won’t protect you from malware. The only thing it does is encrypt your traffic to/from the VPN server, and mask your WAN IP address. The encryption will help protect you from a hostile network, (like your work WiFi spying on what sites your phone is accessing) but it won’t stop you from downloading malware. The largest reason to use a reputable VPN is because you’re running all of your traffic through their servers. You want to know that they’re not just selling all of that data to the highest bidder; If you’re not the customer, you are the product. When searching for a VPN, you’ll want to find one that supports port forwarding, because a torrent can only connect if at least one of you has an open port. You don’t want to rely on random seeders to have open ports, so forwarding your own port ensures you can connect.

I have also heard uploading (seeding) is where you really get in trouble with the law in many jurisdictions, as opposed to downloading (leeching), so it’s important to know the laws that apply to you.

This part is largely correct, though it will depend on where you live. Generally speaking, uploaders are penalized more heavily than downloaders. The issue is that you can’t torrent without inevitably doing both. The torrent protocol literally doesn’t allow you to block all seeding. You can restrict it down to a tiny amount of bandwidth in your torrent client, but you can’t just outright disable it.

Killswitches are important as well whenever using a VPN. This helps prevent leaks. I have never seen a major VPN that did not have this feature baked in.

This is where things veer into the “dangerously untrue” territory. A VPN kill switch will not protect you from IP leaks. A VPN simply creates its own network interface, and tells programs to use it. But when that connection drops, there’s nothing stopping programs from just using your regular interface before the kill switch kicks in. You need to bind the torrent client to the VPN directly. This must be done directly in the torrent program, not from the VPN’s kill switch option. By binding the torrent program directly to the VPN’s network interface, the VPN won’t be able to connect unless the VPN is enabled.

You can check for IP leaks using a few different websites (Google it).

So there’s… Uhh… Quite a bit wrong with this

That's because it's garbage that was shit out by a LLM. The constant "I have heard..." for every statement is a thing deepseek does, and it's bloody annoying.

Could you explain please why the killswitch feature is insufficient? I'm very interested technically in why that might be the case.

I read the article but it doesn't mention about that in there.

Also, is there any difference in this case between using the regular killswitch, and the advanced? As I understand it the regular one would definitely not be sufficient, but the advanced should be?

Today i have a torrenting server. A headless ubuntu server with qbittorrent-nox tjat i acccess via a webbroswer.
I have trouble setting up the same with i2p (haven't looked at it super much). I get torrenting over ipsnark on my PC to work but the headless webui i2p torrenting I don't get to work. Especially when I whant to surf i2p with the same router that I torrenting over. The goal is to have it in docker.

One more problem I always get is that I am always "firewalled" when I search some people say open ports in router and other say don't.

I have that exact setup working. qbittorrent (and -nox) are a lot more involved to set up with I2P, but there is some material on how and once you get it running it works quite well at this point.

I don't use docker for it, but that should work too. For browsing I use a maintained fork of proxy switchy omega, which allows to choose a proxy profile based on the url, making it easy to pipe i2p pages into the i2pd socks port (I use I2Pd not I2P, don't think it matters much). qbittorrent can be configured in the same way to statically use the the local (4447 on i2pd) port as a proxy to prevent any clearnet communication. In addition it needs the dedicated I2P host 127.0.0.1 and port 7656 (the sam bridge, giving deeper access to I2P).

Don't expect to do anything on the clearnet over I2P, the exits are not good and it's not what I2P is meant for. For that reason don't set I2P up as something like a system proxy/vpn, instead pipe the specific programs you want using I2P into the proxy ports using their proxy settings.

To get rid of the firewalled status in the I2P daemon, you will need to forward ports. Maybe you have seen advice for servers that are not behind a firewall and nat, so that effectively have all ports "forwarded" already. The mythical dedicated IPv4 address.
In your case you need to pick the port your I2P daemon uses for host to host communication randomly, then forward both TCP and UDP for it on IPv4. Also make sure you even can forward ports, depending on region ISPs no longer hand out dedicated IPv4 even per router, so you might have to specifically ask your ISP for one (I had to). But that is all generic hosting, if you can set up a minecraft server you can make I2P have full connectivity.

ZeroOmega--Proxy SwitchyOmega V3 – Get this Extension for 🦊 Firefox (en-US)

Download ZeroOmega--Proxy SwitchyOmega V3 for Firefox. Manage and switch between multiple proxies quickly & easily.

^{addons.mozilla.org}

The market is very volatile.
For example my plan is a grandfathered plan which is unmetered and allows public trackers.

i'd suggest looking on r/seedboxes or similar subreddits as they have a very broad table of many providers.