Following your instruction, I have (re-)achieved some filtering. So maybe my configuration got messed over somewhere and I was not paying attention so proxy 3129 --> dansguardion --> 8080 ---> browser proxy on 8080 seems to be OK.
So this bug may be closed as my error. Problem now is bogging down reading of some sites which may be a newer bug. I see nothing in the configs saying how to recurs the increasingly complicated way sites are assembled now. Going through all the ads and images and references to other places make simply be causing the whole business to time out, but silently. It does not matter whether this is a site that should be blocked (one I tested that never loaded enough to give me the blocked screen), or a clean site. Some sites will simply never come up unless I exclude them from the proxy. Some on-line services are manually screening sites, blocking images in their internal proxy or mechanism, blocking certain ads, but doing this once. They serve the screened internet as a provider rather than a proxy. One such site here installs a windows program but claims this is not a proxy. No use to me, of course. While the use of ad-blockers may be unfair, it may be quicker than requiring a live dansguardian to step into all this material every time a site is loaded. It may be that an option of how many levels to go in might be needed, or some heuristic to prevent endless keyword searching. Some off-line list of blocked material, a la anti-spam lists like razor and such, may be another alternative. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
