• 0 Posts
  • 65 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2023

help-circle
  • All the loaded torrents in a torrent client already get stored somewhere in the torrent client’s own settings folders. e.g. if you look in qBittorrent’s settings folders you’ll find a folder full of .torrent files representing every single torrent currently in the torrent client.

    So if it’s a torrent I’m going to leave loaded in the torrent client then no, there’s no reason to save a second copy of the .torrent file. But I guess if it’s a torrent I’m not going to load in the torrent client, or will remove it from there, then maybe it’s worth saving depending how you do things.

    I’m undecided. I figure if I save them and back them up to an offline/offsite device, then I can (mostly/hopefully) recover from hardware failure by simply re-adding all the torrent files to my favorite client.

    It would be better just to back up your entire torrent client settings folders, you’ll save all the .torrent files along with the save folders and other information you have in the torrent client.


  • Nope, I prefer being able to run my own network router, open/close my own ports, block ads on the network, hopefully get as much bandwidth as I can, etc. so it’s usually better for me to subscribe to my own internet.

    … But since you bring it up, coincidentally I currently live on a street with shops/restaurants on the main floor under me. And all their wifi networks are visible from my apartment… so technically yeah, if I go through the trouble of collecting all their wifi passwords I could just hang out on their networks for free internet. Internet probably wouldn’t be great and not very private without a VPN but for free web browsing it should work.








  • Ah yeah I saw that one but I don’t think it does quite what OP wants. Seems more like it is designed to monitor a running qBittorrent client and then copy the .torrent file(s) to Transmission, with all torrent data in the same data folder. Might not help much for OP with all the different data folders they have in their current setup.

    My concept is as such: have a shared folder where everything is moved after download. I call this /mnt/torrents.

    The script provided that makes all of this happen is a python script. It queries the qBittorrent client for uploading or completed downloads, checks to see if they are private or public torrents, then copies the .torrent files to the respective “watched” directory of the public or private (transmission) client. It just copies the .torrent files to directories, so it should be usable with other torrent clients that have “watched” directories.

    But either way nice effort! I’m kind of surprised at the lack of scripts to import torrents into Transmission. The only related script I could find is to do Transmission --> qBittorrent but it doesn’t seem to do the reverse https://github.com/Mythologyli/transmission-to-qbittorrent


  • and even then, I tried one and for some reason it wouldn’t verify my downloaded files and insisted on redownloading the torrent from scratch. Even though I had made sure I was pointing to the correct directory. This may be because I’ve renamed files in the past

    That should work fine… I suspect that failed maybe because you renamed like you said. Make sure Transmission is adding torrents in paused mode, then do another test with a torrent you definitely didn’t rename. Maybe just do a test download in qBittorrent and then attempt to add it into Transmission e.g. a Linux Mint torrent or similar is usually a safe test https://www.linuxmint.com/edition.php?id=319

    Because of how you have your torrents organized it does sound like you’ll need to tough it out and add each torrent and configure it manually.

    It would be easier if you had all the torrent data saved in the same folder(s), in which case just configure Transmission to add torrents in pause mode, configure a watch folder, copy your qBittorrent’s .torrent files into that watch folder, and finally do a re-check in Transmission and start all the torrents. Then just hardlink the torrent data out into your own nested folders how you want them set up, that way the same data exists and is linked in two places (torrent data folder and your own folders). Maybe it’s something to consider for your future configuration but it’s not going to help you much right now.

    For now yeah, the best you could do is set Transmission to add torrents in paused mode, configure a watch folder, copy paste your current qBittorrent .torrent files, then afterwards in Transmission change each torrent’s data location and re-check one-by-one. Not sure if it’s any faster than just adding the torrents manually one-by-one :/

    You should be able to find the current .torrent files wherever MacOS saves your qBittorrent files, look for a folder that looks like qBittorrent / BT_backup, all the .torrent files in BT_backup are your loaded torrents inside qBittorrent.

    With some luck maybe you can find a tool that does qBittorrent --> Transmission migrations? I wasn’t sure if any exist, all I can find are tools to do Transmission --> qBittorrent e.g. https://github.com/undertheironbridge/transmission2qbt

    (note I’m not on MacOS so maybe someone else has more direct advice to offer)



  • The vast majority of private trackers do not have a “hard” ratio economy like you describe. Most private trackers are flexible to give users ways to increase their own upload ratio without requiring that ratio to be “paid” by another user doing the downloading. e.g. when torrents are freeleech the users get to download for free but can still upload to improve their own ratio. And when there’s bonus systems in place those bonus points can be used to add to the user’s own uploaded data count. And sometimes private trackers have events where they make the entire tracker, or entire categories of torrents, freeleech so a whole ton of users get to download for free and will still be able to seed those same torrents afterwards.

    does that mean that there are some users who will forever be below 1, and thus end up getting kicked out, thus resulting in the private tracker just… shrinking over time?

    Sure, that could happen too. Private trackers will always get some users that just aren’t going to cut it and eventually lose access to the tracker. In most cases the tracker will just end up adding new users and maintain the total user count. Each tracker is going to be different in how they approach this… I think over time the user churn doesn’t happen as much, at some point there’s enough users on the tracker that are doing fine with ratio and whatnot while the tracker hits its own maximum user count so actually needing to replace users with new signups becomes less of a priority.




  • How to block Stremio peers from qBittorrent?

    You can’t AFAIK.

    Disable DHT

    Don’t do that, DHT is one of the baseline methods of public torrenting. You’ll just end up cutting yourself off from tons of public torrent peers.

    Unclear why you think DHT is strictly something specific to Stremio (?)

    Use blocklists (I am also looking for suggestions, currently considering using this one)

    That doesn’t sound overly reliable, I’d guess if you want to go that route you probably want to install all their stuff including that peerbanhelper thing they are relying on. If you do all that feel free to report back to the community and let us know if it actually blocked Stremio clients for you.

    Some things you could try:

    • In qBittorrent you could try using a different Upload Choking Algorithm, it’s not a real solution but it does help. (Tools / Options / Advanced / Upload Choking Algorithm) There you can try setting it to Anti-Leech or Round-Robin.

      • Anti-Leech is an attempt to stop uploading to peers that seem to request data while trying to mask their activity (e.g. leeching clients), it’s not perfect but can help. See https://www.libtorrent.org/reference-Settings.html#enum-seed-choking-algorithm-t and https://github.com/arvidn/libtorrent/issues/4217 for more discussion.

      • Round-Robin isn’t blocking leeching, what it does is tell your torrent client to split the upload evenly between the requesting peers on a torrent. The result is that you will be uploading slower to a leeching client so those type of clients will prefer to get their upload from other faster peers rather than wait on yours.

    • If you’re desperate you could switch to an alternate torrent client, something like https://github.com/c0re100/qBittorrent-Enhanced-Edition it’s not an official qBittorrent client but rather qBittorrent with some anti-leech additions. They mainly focus on chinese leeching clients so I’m not sure that would help at all with Stremio but you could try opening an issue if it looks like Stremio clients are still leeching off it, maybe the devs can figure something out https://github.com/c0re100/qBittorrent-Enhanced-Edition/issues


    Me personally I don’t worry about this stuff, for public torrents qBittorrent along with Round-Robin or Anti-Leech is enough. Otherwise just stick to private trackers where this sort of leeching is a non-issue.

    PS - The more active piracy community is over at !piracy@lemmy.dbzer0.com you may want to subscribe there too.


  • Just did some quick testing, most are open trackers operating in I2P (meaning they will happily track and announce to any torrents/peers using them).

    Working I2P Trackers, these should work with any I2P public torrents:

    http://opentracker.bt.i2p/a
    http://opentracker.dg2.i2p/a
    http://opentracker.eeptorrent.i2p/a
    http://opentracker.fattydove.i2p/a
    http://opentracker.r4sas.i2p/a
    http://opentracker.simp.i2p/a
    http://w7tpbzncbcocrqtwwm3nezhnnsw4ozadvi2hmvzdhrqzfxfum7wa.b32.i2p/a
    

    Working I2P non-open trackers, meaning they only track torrents published at their own website.

    http://tracker2.postman.i2p/announce.php
    

    Currently Down I2P Trackers:

    http://ahsplxkbhemefwvvml7qovzl5a2b5xo5i7lyai7ntdunvcyfdtna.b32.i2p/announce.php
    http://atia42hvtnklmilskllirvl5e27letgqghyuvrlvtaktyg32kqwq.i2p/announce
    http://crs2nugpvoqygnpabqbopwyjqettwszth6ubr2fh7whstlos3a6q.b32.i2p
    http://lnQ6yoBTxQuQU8EQ1FlF395ITIQF-HGJxUeFvzETLFnoczNjQvKDbtSB7aHhn853zjVXrJBgwlB9sO57KakBDaJ50lUZgVPhjlI19TgJ-CxyHhHSCeKx5JzURdEW-ucdONMynr-b2zwhsx8VQCJwCEkARvt21YkOyQDaB9IdV8aTAmP~PUJQxRwceaTMn96FcVenwdXqleE16fI8CVFOV18jbJKrhTOYpTtcZKV4l1wNYBDwKgwPx5c0kcrRzFyw5~bjuAKO~GJ5dR7BQsL7AwBoQUS4k1lwoYrG1kOIBeDD3XF8BWb6K3GOOoyjc1umYKpur3G~FxBuqtHAsDRICkEbKUqJ9mPYQlTSujhNxiRIW-oLwMtvayCFci99oX8MvazPS7~97x0Gsm-onEK1Td9nBdmq30OqDxpRtXBimbzkLbR1IKObbg9HvrKs3L-kSyGwTUmHG9rSQSoZEvFMA-S0EXO~o4g21q1oikmxPMhkeVwQ22VHB0-LZJfmLr4SAAAA.i2p/announce.php
    http://omitracker.i2p/announce.php
    http://opendiftracker.i2p/a
    http://opentracker-actix.i2p/a
    http://opentracker.skank.i2p/a
    http://psi.i2p
    http://tracker.crypthost.i2p
    http://tracker.killyourtv.i2p
    http://tracker.thebland.i2p
    http://tracker.welterde.i2p
    http://tu5skej67ftbxjghnx3r2txp6fqz6ulkolkejc77be2er5v5zrfq.b32.i2p/announce.php
    http://uajd4nctepxpac4c4bdyrdw7qvja2a5u3x25otfhkptcjgd53ioq.b32.i2p
    

    Unsure if all the ones currently down are just down temporarily. Some I suspect will come back (e.g. skank.i2p has been around forever so I’d be surprised if they’re permanently gone).

    EDIT: Browse notbob, especially their tracker listing for hints on current I2P torrent trackers and sites http://notbob.i2p/cgi-bin/defcon.cgi?category=tracker


  • Your post title is a bit misleading, I think you’re talking more about trying to speed up the process of finding nodes/peers?

    All torrent clients including qBittorrent already have a built-in method of finding new DHT nodes and will find new nodes automatically. If the torrent client does not have any DHT nodes to contact yet (e.g. it’s the first run and hasn’t already compiled its own list of recent DHT node IP addresses) then what it does is reach out to DHT bootstrap node servers. Torrent clients usually have that coded in, sometimes you can change them - in qBittorrent you can go to Tools/Options/Advanced, under DHT Bootstrap Nodes you’ll see the current list of well known bootstrap nodes that qBittorrent uses by default

    dht.libtorrent.org:25401, dht.transmissionbt.com:6881, router.bittorrent.com:6881, router.utorrent.com:6881, dht.aelitis.com:6881
    

    I think most/all torrent clients use the same ones.

    Not sure how current this one is, the code to compile and run your own DHT bootstrap node server is on Github

    https://github.com/bittorrent/bootstrap-dht

    Back in 2016 Libtorrent launched its own bootstrap node server, it’s now one of the default bootstrap node servers for most/all torrent clients.

    https://blog.libtorrent.org/2016/09/dht-bootstrap-node


  • Agreed - I’ll also add that a lot of internet gateways/routers/firewalls also have a built-in feature to update a domain with your current public IP address. It definitely makes it easy, I haven’t thought about needing to update my dynamic IP in years since it just happens on the router.

    Not everyone can do it but it’s definitely worth a look especially for those planning to do any real self hosting.