• Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Torrents

    Whitelists?

    Rules and Information
    whitelist torrent clients
    4
    4
    85
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      nagatha95 last edited by

      Hello all! Forgive me if this has been already discussed but I cant find the post anywhere. I was having trouble seeding my uploads when I was using Transmission on MacOS, and then after using both Deluge and Folx I was seeding without any issue, even though I was following the same process to seed....

      My question is, is there a whitelist for acceptable torrent clients? Or will anything go, and its just whatever youre comfortable with?

      Thanks everyone! Stay horny!

      bi4smooth L LoopyD 3 Replies Last reply Reply Quote 0
      • bi4smooth
        bi4smooth @nagatha95 last edited by

        @nagatha95 said in Whitelists?:

        Hello all! Forgive me if this has been already discussed but I cant find the post anywhere. I was having trouble seeding my uploads when I was using Transmission on MacOS, and then after using both Deluge and Folx I was seeding without any issue, even though I was following the same process to seed....

        My question is, is there a whitelist for acceptable torrent clients? Or will anything go, and its just whatever youre comfortable with?

        Thanks everyone! Stay horny!

        It's unlikely the fact that you're using that client vs. another - at least on the tracker end. It is more likely that the other clients are using other ports or have other settings that are allowing them to work.

        Apple is, in general, very unfavorable to file sharing in general (unless you're using iCloud to do it). They ban torrent clients and the like from their "App Stores" (iTunes, etc) and have for decades now.

        It's not impossible that it's the client vs the tracker - I haven't looked in detail at it - but I would say its unlikely...

        Think of it this way: you're microwaving an aluminum ball (doh! YouTube video?), and after about 10 seconds of sparks flying there's the sound of thunder and at almost the same instant your microwave oven literally explodes.
        Was it caused by the aluminum ball and the sparks? Or, was it caused by the lightening a few miles away?
        From a purely scientific point of view, it could have been either... but, it's more likely that it was the aluminum ball that caused your microwave to explode...
        Either way, post the video! 🙂

        1 Reply Last reply Reply Quote 0
        • L
          lololulu19 @nagatha95 last edited by

          @nagatha95
          I strongly suggest Qbittorrent... and if you want an alternative, use Utorrent.

          The problem with a lot of clients is that they have not been updated in eons.
          Utorrent has been extremely buggy for quite a few years, and still has some nasty bugs... and is only available in 32 bit which has a 4gig memory restriction.

          Qbittorrent is quite up to date.. completely free.. and is 64 bit.

          1 Reply Last reply Reply Quote 0
          • LoopyD
            LoopyD @nagatha95 last edited by LoopyD

            @nagatha95 I have experienced the same issue with recent builds of Transmission. This is not only this tracker that the issue seems to affect, as my radarr grabs from another of many others for movies, too. I migrated to deluge, because at least it still works, and remains completely open source. People crap on it a lot because its written in python, and isn't the most efficient client, but it's worked reliably for 4 years after I made the transition, its really nice to be able to put the client into a virtualenv sandbox and I can't complain.

            1 Reply Last reply Reply Quote 0

            • 1 / 1
            • First post
              Last post