It doesn't seem to be an upload rule that you can't upload upscales right now, so the first order of business seems to be that the rules should be changed to allow downscales for people who don't wanna spend the bandwidth, but it should be against the rules to upscale.

Then you still can't detect em all, but it is fair to warn users not to post upscales.

Another thing you can do is make people declare whether the torrent post is a rip at the original resolution, downscale or upscale, and if they submit with upscale selected you just eat their submission and time them out. ( you don't just want them to go back and lie, so giving them a 3 week freeze on download and upload will probably make the point)

@raphjd Some people have started to upload videos that they expressly describe as upscaled [using AI algorithm].

e.g.
https://www.gaytorrent.ru/details.php?id=5a2c29ad41949825f6f173fab17e904808343b88d638e944

https://www.gaytorrent.ru/search.php?search=upscaled&incldead=0&inname=1&indesc=1&infn=1&orderby=added&sort=desc

You can't really stop people who want to stealthily upload a crappy upscale, but if they are fool enough to put the keywords about it in the description, the system should drop the post into limbo pending moderator review. It should be trivial to scan the upload for a couple of properties

• Video file extension with unreasonable large size (4k video is 7.4GiB per hour so the max reasonable size of a director cut 8 hours DVDRIP is 60GiB
• Descriptions or titles containing "upscaled" and similar keywords
• Filenames containing those keywords

Fundamentally there is no way to recover lost data from video of lower resolution and this form of upscaling is just generating a larger file by adding in fake data. In principle this is at best a stupid idea because someone could just download the original files and perform the exact same upscaling routine, and it takes up additional bandwidth.

As you can see from this post in particular, the upscaling also makes the size terrible because the act of lossy compression actually introduces noise into the sample that is part of the compression, but which actually amplifies the size when resampled because the next compression cannot distinguish the compression artifacts from useful data.

@mrmazda Thanks this worked and I never would have guessed that was the problem.

This problem has been solved thanks to technology.
http://mojoupgrade.com/

You're welcome.

Oh never mind, I see it probably means that my session dropped out at some point over night.  You probably should fix rationator to keep stuff around for a day or two in case of such a thing.  Although if oyu're just using it out of the box, and that's beyond your control short of delving into source, that's understandable.

So I'm seeding a rather large torrent right now to the tune of about 23GB, but if I look at my profile page under my seeding torrents, it claims I've been credited for 11GB while my client says I've uploaded 23.7GB (which must be accurate as I am the seed).  How exactly is 11GB calculated, and what is producing such a huge drift in that number?  Does that mean someone is trying to cheat rationator, or is that value just not updated frequently?

If I download a duplicate torrent( I was on a binge for this particular studio) and don't notice until much later, is there a way I can get that download credit back for the duplicate(bad) torrent?

I don't know if this already happens, but it probably should.

If there is a benevolent admin somewhere that would be nice enough to refund me some ratio, that would be appreciated–although I understand if that is either difficult or impossible.

It seems the site is undergoing some changes so while you're in there you might want to make the duplicate removal mechanism do it automatically.(you know if it doesn't already, again I don't know, certainly the system doesn't PM me if it does).

Attached are the two duplicate torrent files.  One of them seems to have been hunted down and removed.

2014-01-27 Popper: Removed the torrent files, as they contained the personal secrete passkey