Ah, I see now.  So that makes the results appear and disappear and explains all the above.  Good, I just wanted to let you guys know in case you didn't already.

I'm not sure that these duplicates are the result of two separate people submitted, because when I look at them, the text descriptions and files and file hashes are exactly the same.  Two different people submitted a dvdr with the same content are still unlikely to make a torrent with exactly the same hash, unless they happen to have the exact same files with the same order and same block size.  Even then, their text descriptions would likely differ.  This makes me wonder about some bug on the web site reporting duplicate results.

You state that the several entries of 'fishing trip' are not true duplicates.  This is not true and suggest that you simply browsed the search results and nothing further. The 7 gb editions are both duplicates.  As I indicated, they have the same id.  If you look further, you will see that they also have the same hash.  This is what I am talking about.  The web server is listing duplicate entries, either from a true duplicate, or a bug.  I have seen this many times over the past few weeks-many duplicate torrents with the same ID and same hash.  I suggest you look further

someone upload 2nd Gear at:

https://www.gaytorrent.ru/details.php?id=585ec964b2a04f19fd4a32ba80a3f2a69edc910b906e69df&viewcomm=2377116#comm2377116

But at least one of the .vob files is missing (possibly other files).  There is a mechanism to report torrents that violate the rules,  but this doesn't apply to this guy.  He just missed some files on creating the torrent.  Because the uploader is 'anonymous' we can't contact him to fix it.  Is there a way to deal with this?

If you search for:

fishing trip

you will get 2 results with the same url and same Id.  this is just one example of multiple duplicates that I have been seeing.  these duplicates also come up when you browse.  I notice a torrent, a few hours later it will be listed again.  Are you guys aware of this?

It looks like you have changed the scraping internal for torrents to 90 minutes.  Well, I tried it again.  I stopped my torrents and restarted 100 of them; the same thing happened:  error 503, followed by timeouts on the trackers and the website.  So it's the same.  Not a big problem for the torrents; if you leave them running then after several hours they will scrape again successfully.  I still remember when gaytorrent.ru had a DOS attack, so I see why you guys are doing this. But I would hope that it is possible to change it so the timing out on the website does not occur.

Thank for looking into it.  The torrents eventually scrape successfully, but it took a few hours.  This might have something to do with my torrent client (transmission 2.75 (13675) taking a white to assemble the multiple scrapes into a single scrape

Thanks for the info Joker.  However, now I've noticed that twice when I started 113 torrents, I started having error 503, followed by timeouts on all 113 torrents.  I stopped the torrents, and the timeouts continued for 6 hours; I also experience timeouts on the web site.  After six hours, I started getting scrapes from the tracker again; it also took at least 6 hours to be able to access the website again.  This happened twice.  It's my impression that new settings on your DOS software bans me (my IP address) because it interprets starting so many seeding torrents as a DOS attack.  I've been manually starting the torrents, but this is monotonous.  Questions:

1.  Does your DOS software ban IP addresses with the behaviour described above?
2.  If it does, what are the settings ie 20 connections per second or what?  If I know then I could start the torrents faster.  I don't want to get banned
3.  If it does ban as above, could the settings be made more similar to what they were before?  I never had problems before

My dns ip has already been updated to 185.30.164.12 for tracker.gaytorrent.tw, starting torrents initially is fine (status code:working), but after a whilte changes to error code:

Tracker gave HTTP response code 503 (Service Unavailable)

This seems to be a problem with the tracker, not my computer.  I started seeding 100 torrents.  Is anyone else having this problem?  pinging of 185.30.164.12 times out as well, although I do get a reponse from scraping the tracker.

@junior:

Iptorrents also is tracking hit and runs, were not the only ones.  They show up on your  Iptorrents profile  which you are only allowed so many (i believe)   You can however make those hit and runs disappear by using your seed bonus or your  upload credit, either way you have to pay for hit and runs  :police:

Where can we view this web page on our profile?  I can't find it.  I haven't seed a definition of 'hit and run' so I would like to see what the page says so I can act accordingly