@serebryakov said in AT RISK torrent thread - "official":
https://www.gaytor.rent/details.php?id=a229c51eba789f64d0e2d08eea6b6d2c06a638d0b213ad01
https://www.gaytor.rent/details.php?id=815ad0fbbcee02e6d0e2d08eea6b6d2c53343d332bb0324d
https://www.gaytor.rent/details.php?id=a5d803039106204dd0e2d08eea6b6d2c2ca7d768aef2f857
Done
@mdx8472 said in AT RISK torrent thread - "official":
REQUEST:
Three more critically low-seeded torrents...
https://www.gaytor.rent/details.php?id=18cc1cec5ca5f1a1081dd0290b53ff345f87583503531075
https://www.gaytor.rent/details.php?id=51123f8a280afa7a081dd0290b53ff34e2c594cf0b49400e
https://www.gaytor.rent/details.php?id=539d85d6668a0ea1081dd0290b53ff34b08e474b68fb43a0
Done!
@mdx8472 said in AT RISK torrent thread - "official":
REQUEST:
And the next round of critically low-seeded torrents...
https://www.gaytor.rent/details.php?id=185a3bc5b6d19e04081dd0290b53ff341010f8822b032de8
https://www.gaytor.rent/details.php?id=dc62022c07918a0f081dd0290b53ff34e3a00ee7b505f60f
https://www.gaytor.rent/details.php?id=714b8924e1a77aae081dd0290b53ff34dfbee3e9632e32b5
Done!
@mdx8472 said in AT RISK torrent thread - "official":
REQUEST:
And another group of critically low-seeded torrents...
https://www.gaytor.rent/details.php?id=75ac968aef9d64bb081dd0290b53ff34aacbd39ca2d03d70
https://www.gaytor.rent/details.php?id=72f53bf50d7447e5081dd0290b53ff34f2c71ce7b032f4a1
https://www.gaytor.rent/details.php?id=fe6e1798823c2315081dd0290b53ff345a46d8e1ba54d3e1
Done!
@mdx8472 said in AT RISK torrent thread - "official":
REQUEST:
Some more critically low-seeded torrents...
https://www.gaytor.rent/details.php?id=8f1a1509615de93e081dd0290b53ff348109ccc929992801
https://www.gaytor.rent/details.php?id=5b38c260ea568a90081dd0290b53ff34f274cb33063bc50e
https://www.gaytor.rent/details.php?id=4e8f5c05de594680081dd0290b53ff347d3cb74ea8cbde4c
Done!
@KryptoKnight This will be a scrape error, which is usually related to torrents that are NOT active. Try starting the torrent, as the tracker seems to be working just fine on my end.
The discrepancy is often a combination of two things
Your torrent client only updates with the tracker once every 30 minutes on each torrent, so there's a delay in the stats updating from the get go.
The stats in your tracker will reflect all data transferred since the time the torrent was added, which includes overhead traffic like tracker announces, and peer connections, whereas the stats against the individual torrents in your profile only reflect the amount of actual torrent content data that has been transferred for the current session. Stopping the torrent, then restarting it starts a new session, which resets the amount in your profile against the torrent to zero.
@Gasparzinho Such issues are usually torrent specific. The usual culprit is that there is a lack of quality seeders actively seeding the torrent. If you had examples of torrents that are currently not working, I could look into it further for you.
No... Your torrent client only updates with the tracker once every 30 minutes on each torrent. For this reason, there is a delay of up to 30 minutes for the stats to be updated.
@DonnyDuzDick In the case of this torrent, there are no shatchers on the torrent, so the system doesn't have any information on who to PM about the reseed request. Sadly, this torrent will have to be deleted, as there's no hope of it ever coming back.
@frostycab Not a collection according to the rules
@galwaybiguy The points go into the void so to speak, but anyone downloading the torrent in the time that it is freeleech do not get dinged for downloading it.
@ianfontinell-0 Well, there's a few things at play here. The rules for a collection require that collections have a well defined common theme. The general rule to this is that the content must all be of the same performer, or must be from the same site/studio.
The unwritten exception here is with fan sites like OF, JFF, etc. Since these sites are an independent site so to speak, such collections must be from the same performer or same account. As a general rule, mixing different creators of the same site (such as OF, JFF, etc) does not constitute a collection, so these torrents would end up being removed for not having a clearly defined theme.
The only time where we would consider it being acceptable to re-up content like this is if the collection that already exists goes to say November 2024 (just as an example), but the collection that is being uploaded has all the same content, but also extends the collection to say September 2025.
Also, the only other exception to the duplicate issue is if the two collections are the same content, however are in a different format container (i.e. one is in AVI, the other is in MP4). If they're of the same format container, they are considered a duplicate unless the file size difference for each video in the collection is greater than 10%, unless there is a technical difference between the two, such as one is 1080p and the other is only 720p, or if one is 4k and the other is 1080p.
So... When it comes to these collections, I would encourage you to bring such cases to my attention, and I'd be happy to review them on a case by case basis and handle them accordingly. We try to keep things fair for all users, so I'd be more than happy to dig deeper into this if you can give me examples of what you're referring to.
@pornoaf-0 Sometimes it is possible to find out why, but it all depends on what was done when they were removed, and if the staff has access to the right parts of the system to dig for that information.
@darkheart This is a common issue on Android devices. The easiest way to get things going from my experience is to use Vuze on an Android device instead.
@spiffyweasel-0 Usually, clearing the cache and cookies, then doing a force reload will fix the issue.
This was explained to you by staff in several PM's. The issue is that you keep uploading random collections with no common theme, as per the requirements of our rules for a collection.
There was an issue with the site that I raised to the appropriate channels. The issue has now been resolved.
There was an issue with the site that I raised to the appropriate contacts. The issue has now been resolved. Things should now work as expected again.
@frostycab I have attempted contact with the user many times in the past, and at least as far as my messages go, they have never responded. Usually, before just yanking a user's rights, I'll give them a warning and reach out to help them understand what they've done wrong, so as to give them a fair chance to understand the expectation, and make the necessary corrections.
In the case of this user, I have never received a response from any of my attempts to make contact with them, so I have to assume that either there is a language barrier and they can't understand, or that they simply do not care. If they won't respond or engage with me to help resolve the issue, there's not a whole lot of other options it leaves me with unfortunately.