TG and 1337 are pretty good and have me covered. I also have a copy of the RARBG database that has the hashes that I use if I want to find something from there. Pretty easy to get the magnets from Qbit and then save the magnet back as a .torrent and then check if there are already cached in a debrid service. Pretty easy and simple
I’ve sometimes found that 1337x torrents show bigger seed leech numbers but don’t really match up when downloading (May be it’s something to do with my vpn setup). I’ve found magnetdl to be more accurate with seed leech numbers
if you have TCP only and decentralized peers/peer exchange/local peers turned off in qbittorrent (a good security idea if you’re using a VPN to torrent already), you’ll get added security at the cost of less peers. Not to say that’s for sure what’s going on for you, but if you have sane settings for security, it could well be the cause of the discrepancy.
Thanks for the advice. It looks like I already have those settings turned on. Would you recommend I turn them off? I know it’s gonna result in even fewer peers, and I haven’t had any security issues over the past couple of years while it’s been running, but is it something that needs to be done on servers like mine? (I have windscribe that I turn on along with qbittorrent, and when I turn it off, I turn them both off at the same time)
If you forward a port on your network (or VPN) and point your torrent software towards that port, you are now an “active” node. You can communicate with anyone else, forwarded or not.
If you leave it closed (passive node), you can only communicate with active nodes. With large torrents, this isn’t an issue because there’s more than enough active nodes to send the data.
Port forwarded: talk to anyone, even closed
Port closed: only talk to port forwarded people and hope that small torrents have someone with a forwarded port.
Not typically but it can vary depending on which protocol and which provider you use. Best to check yourself using something like ipleak.net and see if there’s any identifying info on there while you’re connected.
A lot of torrent sites do not regularly update the seed/peer count on torrents listed there. Or they only do it on some sort of daily/weekly schedule. In other words the older the torrent is the more likely the seed count is going to be wrong.
I’m not sure about 1337x specifically but you could probably tell by comparing numbers for new torrents vs old torrents listed there.
Just use qBittorrent and integrate Jackett search into it. You can search all your favourite torrent sites within seconds. The best casual setup out there
Not really. From what I understand we wouldn’t need to encode a link to a torrent website, see the other post https://lemmy.dbzer0.com/post/18438
Mainly you’d want to avoid linking anything directly (say a direct link to something possibly copyright/pirated) or at the very least do the base64 encode thing for that.
(of course the above can change if the current policy causes issues with federation with other Lemmy instances)
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Nyaa.si is good for manga and anime
You can just go to https://torrentio.strem.fun/configure and use all their trackers.
btdig dot org is pretty decent.
TG and 1337 are pretty good and have me covered. I also have a copy of the RARBG database that has the hashes that I use if I want to find something from there. Pretty easy to get the magnets from Qbit and then save the magnet back as a .torrent and then check if there are already cached in a debrid service. Pretty easy and simple
Will you share that raring database or is it easily available elsewhere? First time heading of this!
Help us seed them :) See the earlier posts
https://lemmy.dbzer0.com/post/260450
and
https://lemmy.dbzer0.com/post/372879
I think I used this one. I have a few I downloaded from links on reddit around the time RARBG went down and people were trying to find backups
https://old.reddit.com/r/Piracy/comments/13yknky/tutorial_keeping_rarbg_alive_how_to_access/
I’ve sometimes found that 1337x torrents show bigger seed leech numbers but don’t really match up when downloading (May be it’s something to do with my vpn setup). I’ve found magnetdl to be more accurate with seed leech numbers
if you have TCP only and decentralized peers/peer exchange/local peers turned off in qbittorrent (a good security idea if you’re using a VPN to torrent already), you’ll get added security at the cost of less peers. Not to say that’s for sure what’s going on for you, but if you have sane settings for security, it could well be the cause of the discrepancy.
Thanks for the advice. It looks like I already have those settings turned on. Would you recommend I turn them off? I know it’s gonna result in even fewer peers, and I haven’t had any security issues over the past couple of years while it’s been running, but is it something that needs to be done on servers like mine? (I have windscribe that I turn on along with qbittorrent, and when I turn it off, I turn them both off at the same time)
you dont need to turn them off.
If you don’t have port forwarding and the seeder doesn’t then you won’t see them.
A lot of casual torrent users won’t know about this so it’s a common issue on public trackers.
Did you mean if there is no port forwarding at my end and also at seeder’s end ?
Yes, to communicate at least one peer needs to be port forwarded.
Could you elaborate? Never heard of this aspect
If you forward a port on your network (or VPN) and point your torrent software towards that port, you are now an “active” node. You can communicate with anyone else, forwarded or not.
If you leave it closed (passive node), you can only communicate with active nodes. With large torrents, this isn’t an issue because there’s more than enough active nodes to send the data.
Port forwarded: talk to anyone, even closed
Port closed: only talk to port forwarded people and hope that small torrents have someone with a forwarded port.
Thank you. Does this create any considerable vulnerabilities?
Not typically but it can vary depending on which protocol and which provider you use. Best to check yourself using something like ipleak.net and see if there’s any identifying info on there while you’re connected.
That’s great. I’ll do some more research on the hardware I have also
A lot of torrent sites do not regularly update the seed/peer count on torrents listed there. Or they only do it on some sort of daily/weekly schedule. In other words the older the torrent is the more likely the seed count is going to be wrong.
I’m not sure about 1337x specifically but you could probably tell by comparing numbers for new torrents vs old torrents listed there.
I think it’s because 1337x updates the seeds count periodically, and sometimes it doesn’t get updated for a while
“Best” is probably going to be private torrent trackers.
But if you meant public torrent indexers then the top ones in terms of web traffic are 1337x, ruTracker, TPB, Rutor, & TorrentGalaxy.
Most people that were using RARBG have ended up at 1337x and TorrentGalaxy.
For what it’s worth if you just need a website to search the old RARBG torrents https://rarbg.best might be a good fit.
PS A lot of these sites are also linked at the other torrent site community !torrent_trackers@lemmy.ml
Just use qBittorrent and integrate Jackett search into it. You can search all your favourite torrent sites within seconds. The best casual setup out there
How do you integrate Jakett search, do you have to install Jackett separately?
Yes. Follow the relevant Jackett installation instructions. Set it up as you wish.
Then configure it to work inside qBittorrent.
But don’t you need the rest of the *arr apps for Jackett as well?
I just want to search the damn public torrent sites without having to install a dozen of applications.
No you don’t. Infact, most people would recommend using Prowlarr instead if you want integration with *arr apps.
It supports hundreds of public trackers (as well as private & semi-private ones). Up to you which you enable.
Jackett integrates directly into qBittorrent. You don’t need anything else. All you need is 1) Jackett 2) qBittorrent.
Thanks, I’ll give it a try
Prowlarr is better if you have Sonarr and Radarr set up
aHR0cHM6Ly8xMzM3eC50by8=
aHR0cHM6Ly9yZW50cnkuY28vbWVnYXRocmVhZA==
Use https://www.base64decode.org/
This is the best way of posting links. I agree. Let’s all get used to this. Also DMCA bots can’t get it.
Is there a firefox plugin to automatically decode them?
Edit: to answer my own question https://addons.mozilla.org/en-GB/firefox/addon/base64-decoder/
Wow! Thanks. Appreciate it.
But do we still need this?
Not really. From what I understand we wouldn’t need to encode a link to a torrent website, see the other post https://lemmy.dbzer0.com/post/18438
Mainly you’d want to avoid linking anything directly (say a direct link to something possibly copyright/pirated) or at the very least do the base64 encode thing for that.
(of course the above can change if the current policy causes issues with federation with other Lemmy instances)
Get jackett, add all of the public trackers, plus any other trackers you may be a part of, and just search really.