-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Search more trackers for screenshots #292
Comments
I'm not keen on this idea. It's robbing Peter (strain on sites) to pay Paul (arguably less strain img hosts). On my windows box, I see the same time to capture/optimise/upload images as it takes to snatch/verify the images from ptp. |
I disagree. Querying sites once causes minimal strain but hosting unnecessary images indefinitely is an ongoing cost to hosts. I think it should be an option. |
Hosts, whose business is to host images. Sites (run entirely on volunteering btw), who are not here to serve up image links to be used elsewhere, or more accurately, are not here to potentially serve up clean links because the last site that was pinged didn't have valid liinks. There's nothing stopping the use of correct id's to ensure you get the actual content you want, without pinging sites and praying. If I had of implemented pooling of the screenshot process (and to some extent ptpimg had expressed their concerns) before having the idea of parsing image links from descriptions, I likely would not have even bothered with the image links at all. The more I think about this, the more I just want to close the issue. I'm hearing rumors of potential changes in the works for ptpimg. Hence why I refactored the process to make it significantly easier to define approved hosts per site: #272 |
I also don't think using images that might be deleted by another uploader are a good thing, best to control the images uploaded for your uploads. |
I didn’t think about this. This solves it. Thanks! |
If you're scripting with qbit v5, pass |
If it searches tracker 1 and finds a release but no valid screenshots, instead of uploading new screenshots it should instead check other trackers if they have valid screenshots available
The text was updated successfully, but these errors were encountered: