Skip to content
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

Remove E6 IQDB #111

Open
faucetlol opened this issue Dec 29, 2023 · 3 comments
Open

Remove E6 IQDB #111

faucetlol opened this issue Dec 29, 2023 · 3 comments

Comments

@faucetlol
Copy link
Contributor

I've been getting a quite few false positives with the IQDB matching lately, I was previously just deleting the matches from the database manually but it's happening often enough to be time consuming at this point. While it's not an ideal fix, it would be nice to have an option in the UI to delete the IQDB result so the image can appear in the "Not Uploaded" filter.

It would probably fit well next to the existing "Update E6 IQDB" link.

Greyscale images are primarily the problem:
image

@mm12
Copy link

mm12 commented Jan 21, 2024

I agree - also adding a search filter for the opposite of the matches would be nice - ie 'only show non-exact' and such. Most of the ones with this issue could be found with "multiple matches" showing. Perhaps filter by % match?

@Earlopain
Copy link
Owner

Would adding a global score cutoff config work? Currently everything is done with 60 which means that a few false positives like above will be shown.

Setting that number arbitrarily higher, to say 70 or 80, would reduce the number of false positives. Though that would also remove some actual matches.

I'm not sure where I would put the functionality to remove/disable individual matches. The UI is already cluttered as is.

@faucetlol
Copy link
Contributor Author

Setting that number arbitrarily higher, to say 70 or 80, would reduce the number of false positives. Though that would also remove some actual matches.

4/10 of the false positives on the example I posted are 70% or higher confidence, I think it would probably end up doing more harm than good by filtering out actual matches. I don't know what it is with IQDB and greyscale images, but Danbooru does the exact same thing. 20 results on their reverse search for that same image, all between 68 and 78%.

I'm not sure where I would put the functionality to remove/disable individual matches. The UI is already cluttered as is.

It might be good on /submission_files/:id since it's not going to be something that needs to be used incredibly often.
image

Or maybe combining both buttons into one <li> to look a little cleaner:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants