Filtering needs to be done on a website pages level not just top level website level.
For example http://www.friendfinder.com if I have the nudity filter on will get blocked because some of the pages have nudity. You should be able to visit pages within the friendfinder.com website that don't have nudity and see them and move around the website and not have a page blocked until it has nudity. The problem stems from just having an overall top level categorization (bikinis, nudity, etc...) that applies to full website. The category is useful to know a summary of what the full website has. But OpenDNS users (me) should be able to say block on top level down for a website so would function as OpenDNS does now or block on a page level so could visit pages that e.g. don't have nudity but when hit a nudity subpages maybe 5 pages into website then blocked.
I love OpenDNS but the way you currently have filtering forces blocking all access to a website that may have 2 web pages with nudity. If I realize this I need to add the website to the do not block white list or take nudity out of the filtering so shows the website and now those nude or porn (whatever) pages can be seen my me or my family.
This needs to be fixed as increasing there is content where the all or nothing does not work. Also videos or photos are totally missed by OpenDNS. Great service but OpenDNS 2.0 is needed as I can easily cause porn websites for example that I have blocked in filters, to be displayed. A crack has opened!
Additionally there needs to be an OpenDNS solution for mobile devices -- even worse!!!
-
Duplicate of https://support.opendns.com/entries/98538157
Please sign in to leave a comment.
Comments
1 comment