Is there a way to get original Pixiv images searched by harry.lu?

Harry.lu is reverse image search, it searches similar looking images, so it doesn't matter image is lower res or compressed. At that point, just use urls that work, e.g. pixiv generated preview images.

If you want to search for exact images, use e6 sites MD5: search function with images MD5 hash.

Mario69 said:
Harry.lu is reverse image search, it searches similar looking images, so it doesn't matter image is lower res or compressed. At that point, just use urls that work, e.g. pixiv generated preview images.

If you want to search for exact images, use e6 sites MD5: search function with images MD5 hash.

Yes, I considered comparing preview iamges, but it makes no point in the end because I want to upload original images and I need them to be compared. Comparing previews is actually worse than not comparing.

(P.S. Why does the image I compare with show up as a result with 99-98%? (image being compared to itself and not 100% accuracy and being shown?))

Edit : So I can compare with Pixiv's MD5?

There is no such thing as a 100% match, from all I've done with Harry.lu. Harry.lu is just a reverse image search engine, it lets you find images that are on here and link them to you so you can compare edits, resolution sizes, or even see if it was previously deleted and why. It works for any standard type of image and doesn't care about the source or how it was uploaded, just so long as the image is on the site.

Siral_Exan said:
There is no such thing as a 100% match, from all I've done with Harry.lu. Harry.lu is just a reverse image search engine, it lets you find images that are on here and link them to you so you can compare edits, resolution sizes, or even see if it was previously deleted and why. It works for any standard type of image and doesn't care about the source or how it was uploaded, just so long as the image is on the site.

What I was asking is why the image,for example post #1010355 when being compared shows itself as a result and only 96% match. Shouldn't the image that x is being compared with be excluded from the result?

DelurC said:
What I was asking is why the image,for example post #1010355 when being compared shows itself as a result and only 96% match. Shouldn't the image that x is being compared with be excluded from the result?

There is never a 100% match. Sometimes images get excluded, others get 99, my speculation is that it just checks every little thing, and rechecks the similar image and stutters up. Normally lower percentages are attributed to monochrome or limited colors on white background, but it also takes kind to MLP simple imagery.

DelurC said:
Yes, I considered comparing preview iamges, but it makes no point in the end because I want to upload original images and I need them to be compared. Comparing previews is actually worse than not comparing.

(P.S. Why does the image I compare with show up as a result with 99-98%? (image being compared to itself and not 100% accuracy and being shown?))

Edit : So I can compare with Pixiv's MD5?

Well in theory, it should give exact same results, wheter you used generated preview or original image. Because it looks at the image, not at the file.

That's also why it never gives 100% match, because it compares how they look and the alghorithms for that aren't 100% certain. When there's less details or specific features e.g. image uses grayscale, the certainty lowers further. Usually stuff above 90% is most likely match.

That's where the MD5 comes in. If the MD5 matches, that means the image is 1:1 exactly the same. So yes, what you do is take MD5 of the image you want to search and put the MD5 in the search. e.g. for post #1010355 MD5 would be 7a80ddef1e3915ea4d8a4974e58e3413 so you find it with searching MD5:7a80ddef1e3915ea4d8a4974e58e3413.

So if you want to search that did someone upload original version instead of preview, you can just search both MD5 sums to check that out. Site also makes images URL their MD5 (earlier examples filename is 7a80ddef1e3915ea4d8a4974e58e3413.jpg) so if you find image trough harry.lu, you can just check posts MD5 and compare the hash locally on your computer.

I guess I'm a little unclear on what you're trying to do. Are you trying to check if a picture is on pixiv? You can just use saucenao, then. If you're trying to find images from pixiv on e6, searching source:pixiv* should get you those results. Otherwise we need more clarification

rezi said:
I guess I'm a little unclear on what you're trying to do. Are you trying to check if a picture is on pixiv? You can just use saucenao, then. If you're trying to find images from pixiv on e6, searching source:pixiv* should get you those results. Otherwise we need more clarification

I'm almost certain they want to use original image url from pixiv directly with harry.ly (format: http://i1.pixiv.net/img-original/img/... and similar) instead of preview images used on site (format: http://i1.pixiv.net/c/1200x1200/img-master/img/.... and similar).

Thing is you can't access original images directly, they give 403 error. You need to specify refer or access it from the sites page.

....btw, if this is the case, why not just download the original image to local memory and upload to harry.lu then?

rezi said:
I guess I'm a little unclear on what you're trying to do. Are you trying to check if a picture is on pixiv? You can just use saucenao, then. If you're trying to find images from pixiv on e6, searching source:pixiv* should get you those results. Otherwise we need more clarification

I want to know if image from pixiv is on e621.

Mario69 said:
....btw, if this is the case, why not just download the original image to local memory and upload to harry.lu then?

Because there is no way to programmatically interact with filebrowserdialog, at least not that I know off.

DelurC said:
I want to know if image from pixiv is on e621.

Because there is no way to programmatically interact with filebrowserdialog, at least not that I know off.

Yeah, so at this point simply just use pixiv preview image with harry.lu. You get exact same results with both versions of image anyway. That's the one of the main points of that service, looking up does your low quality version have higher quality variation on site. As e6 will block upload if the MD5 matches.

If comparing MD5 hash or uploading image here, then you do need the original image to handle with.