Best posts made by MrMazda

We do have an RSS feed, which can be brought into a number of programs in order to download certain torrents automatically.

@magician This appears to be a database issue. I have alerted our system admin to the problem so that they can solve it. Please be patient while we get to fixing this.

@frostycab As far as I am aware, it is. The owner just recently did some fixes to it to make it work right again.

@raphjd This is correct..... PIA is something different. They're based in the United States if I recall correctly which can be considered a red flag. Now.... That being said, they do support port forwarding, however they will randomize the port on each connection, so every time you connect, you must change the port settings in your torrent client.

PrivateVPN on the other hand from https://privatevpn.com/ will do the same on all servers, however for some servers, they support port forwarding for ALL ports, so you don't have to keep changing settings in your torrent client every time you connect.

As for ExpressVPN, they do support port forwarding, however in order to take advantage of this, you must install the VPN service on your router and setup the port forwarding within the router. Not all routers support this option, and by the same token, not all routers that support a VPN connection support ExpressVPN. This potentially makes it more expensive by having to upgrade your home network equipment and get into way more complicated setup to get it going.

@Harribal-0 I see your problem.... You're using the .rent domain over HTTP.

To fix this, you need to either change it to https and remove the :2710 OR you need to change the domain to gaytorrent.tw

This is why it is not working for you. You will still get a scrape error from the tracker as we do not support the scrape feature, but this should not affect your ability to download and seed torrents. It will only affect things when the torrent is not active in your torrent client.

@flozen Sadly, some people just like to whine.... So I'll leave you with this...

Youtube Video

@MrMazda By default, when no port is specified, HTTPS uses the standard port 443

@john32123666 We have specific straight and bi categories. By default, they are turned off. If a user wishes to upload straight or bi content, it must go into one of these categories so as to keep it away from and out of reach from users who may wish not to see it.

That said, sometimes straight porn does get uploaded into the wrong category, usually because the uploader either hasn't read the rules, or because they have not turned on the straight/bi categories. When this happens, we encourage users to report the offending torrents so that they can be moved to the appropriate category and out of view from users who wish not to see it.

@nancledra53 There is no notification given to any seeders or leechers of the torrent, however the uploader is notified when a torrent is taken down. This is an automatic process for the most part.

@eobox91103 Yes... Uploading a lot of garbage torrents can get your upload ability revoked, at the very least temporarily. We encourage you to report such torrents for being garbage torrents that in no way follow the intended rules and requirements.

@eobox91103 After looking things over, I do not think the problem is with your uTorrent settings. The issue is that there are next to no leechers actively downloading any of the torrents that you are seeding. I can see what I can do to help with this, but the lack of leechers alone will have a lot to do with your issue.

Also, for our tracker, you need to make sure that the port that your torrent client uses is forwarded through your home router to your computer, both in TCP and UDP for things to work properly.

@homomatik-0 In order to download torrents, you need a torrent client such as uTorrent (3.5.5 or earlier), BitTorrent (before 7.11), transmission, vuze, qBitTorrent, or flox.

You get little .torrent files from torrent sites like this, which tell your torrent client where to look to get a list of where to download the content from.

@eobox91103 I did... It's a great way to revive dying torrents, and many of the torrents you are seeding were dying and had no leechers. This is where the sudden increase in traffic came from.

As a side note, it may be worth putting a limit (throttle) on your upload speed in uTorrent. The reason for this is that in order to browse websites or really do much of anything online, you need to have at least a certain amount of upload ability available. When the connection is fully maxed out, it can create difficulties with other devices trying to use the internet normally.

If your internet speed caps out at about 25 mbit (3,051.75 KB), I would recommend capping your upload speed at about 2,450 KB/s. This will ensure that other devices on your home network have a sufficient upload capacity to be able to work on the internet without causing issues. It's a bit of a reduction, however if you have more than one device on the network, it will ensure that all devices will be able to function consistently on your network over the internet.

Just for reference, the speed calculations can be derived as follows:

1 bit = 1 bit
1 kbit = 1000 bits
1 mbit = 1000 kbits = 1,000,000 bits
1 Byte = 8 bits
1 KByte = 1024 Bytes
1 MByte = 1024 KBytes
1 GByte = 1024 MBytes

So the formula would work as follows

25 mbit x (1,000,000 bits/mbit) = 25,000,000 bits
25,000,000 bits / (8 bits/Byte) = 3,125,000 Bytes
3,125,000 Bytes / (1024 Bytes/KByte) = 3,051.75 KBytes

@flozen While SlamRush wasn't really my thing (mainly because the guys were all too young for my liking), I couldn't necessarily knock it either.

I'm a big believer in a person's right to choose what is right for them. That said, I am NOT a fan of someone trying to take the stand that because it's not right for me, YOU can't do it either.

Having once been a bit of a party pig myself, I get the appeal of letting loose and letting what happens happen. For me, that used to be part of the thrill. If you know what you're going in for and you get what you want, is it really that bad? Now, that being said, this is a very different thing than going in blind and not knowing what's going to happen or what has been planned until it's too late to consent or object. In my case, I knew what I was going in for and I let it happen. I don't know where SlamRush fell in that regard.

It appears that you may have caught some sort of a system glitch. That's the only explanation that I can think of.

@tlkoss501 It's because the old domain is still being used in the PM it sends you, and signing in on .rent will not sign you in on .ru as well. You need to either change the domain in the URL when you get the 404 error, or you need to sign in on the .ru domain as well to see the torrent.

@Symphonia-0 Actually, yes... It does. It's not free, but it's a one time purchase of an app called iTransmission, which is available in the Apple App Store.

For an Android device, I would be inclined to recommend Vuze.

Now, that being said... Power settings among other things need to be tweaked to make it work in the background, otherwise the app stops when it's not active and up front.

@Darekins-0 Yes and no.... No it's not "normal" on the most part, however I see that you are running uTorrent 3.6.0, which has many known compatibility issues with our system. The issue you are having is one of the "normal" things about uTorrent 3.6.0 with our system. There are also a number of other issues that often come up with this version

If you uninstall uTorrent 3.6.0, then install uTorrent 3.5.5 or earlier in its place, you can get around this issue and have your data and active torrents reported properly.

FWIW: There seems to be one thing in common with all these cases... uTorrent 3.6.0, BitTorrent 7.11, qBitTorrent 4.6.2, and a few others that are based on the same Libtorrent base as qBitTorrent is.

I think you may find that rolling back your torrent client to a previous version will help with this.

@john32123666 Based on the user's history, I don't think there's much of an issue there. The issue in their case is likely squarely on uTorrent 3.6.0. It does many strange things when working with our tracker. Some of these include showing that the tracker is working and seeding, however the site doesn't see this on our end. Sometimes no data at all is reported, so you can be seeding actively all day and have nothing to show for it. This is why I recommended rolling back to uTorrent 3.5.5 or earlier, which does not have this problem.