|
Hi, I've tried this (as in another post):
It's blocking the 2nd page of google images, but oddly enough the first page still comes in. Is there any better way to block images using this service? |
|
Not really, since the problem is that it doesn't understand the context of the image. You could add the hostname the images are coming from to your blacklist, but that is about all you can achieve. |
Yes, as I said in the other thread: Edit:
If you look at the source of the first page (or properties of images), you'll see image URLs like this: As you can see, this URL is not related to a domain name, therefore cannot be blocked by DNS methods. So you'll see this image, because it is presented as data within a HTML page, not really as image. This can happen also from page 2+ on, but just be chance it didn't happen to you. Clearer now? Only image URLs which come along with a domain name can be "blocked" (or better: poisoned) by a DNS service. |
|
I'll use http://scroogle.org. I still can't understand why it was blocking images on pages 2+ and not page 1. I understand why it doesn't know the difference between a good image and bad, but if it's blocking page 2 and on, why would it let 1 go through? |