New answers tagged google
I think you were on the right track with your watermarking option, but you left too much of the original image in tact. Here are two images I tried that Google was unable to find: Checkerboard Reverse image search results Mosaic Reverse image search results Another example Reverse image search results The first image returns a lot of "checkered ...
Google may use a different system but a large number of such services (tineye included) use perceptual hashes where the overall hash is close enough to be a match, rather than exact. A whitepaper showed up a few years back which detailed the process. I haven't been able to find a link to it, but the basic system relies on a action chain to generate the ...
Try switching the file format you're saving in. Reverse image searches start by using some data that gets logged intrinsically into the image, which is probably why your obfuscation techniques haven't been working. JPEGs are particularly bad about this, PNGs not so much. With especially popular images, this might not work, however. Ideally, find a way to ...
You can do something like this: It is not 100% bulletproof, but it should throw off most image identification engines. What I did was add black and white noise to the image as well as some displacement. Messing with the colors eg. only displacing one or two color channels would be even more effective, but complex to implement.
Per Google after a little search: Things not permitted: Don't copy or imitate Google's trade dress, including the look and feel of Google web design properties or Google brand packaging, distinctive color combinations, typography, graphic designs, product icons, or imagery associated with Google. Source
Top 50 recent answers are included