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.
As a person who is not an advanced pirate, I’m reading the Jackett page and I have no idea what it is or how it works.
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
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.
IPv6 torrenting for the most part goes unchecked by the companies who send threat letters to your ISP. I have a US seedbox which doesn’t have IPv4 and it’s been working great with a lot of public torrents
Docker, if you can run it on your hardware (either your normal system or on dedicated hardware) is a Swiss army knife that can help level up your acquisitions, and provides you with an isolated application environment if you don’t want to install the applications directly to your device. For media specifically, there is a suite of applications under the same *arr naming scheme that allows you to index, monitor for releases of, and acquire different television shows, movies, music, and books.
Some container maintainers build in different capabilities into their torrent client containers, such as Binhex’s qBittorrent and Deluge applications, that have VPN connectivity built in, so any network traffic running through that container will automatically use your VPN provider’s WireGuard or OpenVPN capabilities, depending on who you use. Once you have that running and your tags tuned in the *arr apps, you have a headless, mostly independent machine constantly working on acquiring and upgrading your media.
Sidenote: the *arr apps can be controlled by mobile apps like LunaSea on iOS, and nzb360 on Android. The latter can also integrate with your torrent clients.
Get into private trackers if you can and then you won’t have to worry much about any of this.
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
