I’ll start. Did you know you can run a headless version of JD2 on a raspberry pi? It’s not the greatest thing in the world, but sometimes its nice to throw a bunch of links in there and go to sleep.
stop manually browsing torrent sites! You’re wasting your time.
Download qBittorrent. Download Jackett. Configure Jackett to work inside qBittorrent. You now have a way to search hundreds of trackers all at once within seconds and find literally anything you want.
You should check out Prowlarr, its like jackett, but integrates better into sonarr/radarr
Prowlarr has a prettier UI but the torrent sites they support are maintained by Jackett. It noone gives credit, at some point Jackett won’t be maintained and Prowlar neither.
Disclaimer: I’m qBittorrent, Jackett, Flaresolverr and Bazarr developer.
Hey thanks for your work. QBT and Jackett are super stable and well done.
Damn, I’m huge fan of yours. Using qBbittorent, Jacket, Flarsolverr and Bazarr in docker. Thanks for your work.
But I never managed to get Jackett plugin to work x)
https://github.com/qbittorrent/search-plugins/wiki/How-to-configure-Jackett-plugin
It has limitations, but qBittorrent is used by 40M users aprox and we are only 3-5 active developers. Managing the open issues don’t let us time to work on new features…
I was looking into this like last week but paused it because I’m an idiot who can’t figure out which package to grab off their git lol. I think it is amdx64 but I have intel everything, I know it isn’t arm though.
It’s called amd64 because AMD invented the x86-64 processor instruction set, it works both on Intel and AMD
type
uname -min your terminal
What I really want to know is what you guys use for getting torrents for entire seasons of shows, or even the entire show at once. I’m not new to piracy, I’m just new to talking about it with people.
Omg… i wish I knew about this 2 weeks ago…
Wireguard creates a new network interface that accepts, encrypts, wraps, and ships packets out your typical network interface.
If you were to create a kernel network namespace and move the wireguard interface into that new namespace, the connection to your existing nic is not broken.
You can then use some custom systemd units to start your *rr software of choice in said namespace, rendering you immune to dns leaks, and any other such vpn failures.
If you throw bridge interfaces into the mix, you can create gateways to tor / i2p / ipfs / Yggdrasil / etc as desired. You’ll need a bridge anyway to get your requester software interface exposed to your reverse proxy.
Wireguard also allows multiple peers, so you could multi-nic a portable personal device, and access all your admin interfaces while traveling, with the same vpn-failure-free peace of mind.
I know some of these words
Usenet is worth every penny
