summaryrefslogtreecommitdiff
path: root/net-proxy/bfilter/metadata.xml
diff options
context:
space:
mode:
Diffstat (limited to 'net-proxy/bfilter/metadata.xml')
-rw-r--r--net-proxy/bfilter/metadata.xml21
1 files changed, 0 insertions, 21 deletions
diff --git a/net-proxy/bfilter/metadata.xml b/net-proxy/bfilter/metadata.xml
deleted file mode 100644
index ad49eeed7a03..000000000000
--- a/net-proxy/bfilter/metadata.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
-<pkgmetadata>
- <!-- maintainer-needed -->
- <longdescription>BFilter is a filtering web proxy. It was originally intended for removing banner ads only, but at some point
-it has been extended to remove popups and webbugs. It can't be used as a general purpose filtering proxy
-because it was never intended this way.
-
-For example you can't just block an arbitrary object, you can only hint the ad detector in its decision making.
-The main advantage BFilter has over the similar tools is its heuristic ad detection algorithm. The traditional
-blocklist-based approach is also implemented, but it's mostly used for dealing with false positives. Unlike
-other tools that require constant updates of their blocklists, BFilter manages to remove over 90% of ads
-even with an empty blocklist!
-
-The javascript generated ads are not a problem for BFilter, as it has a javascript engine to combat them.
-BFilter is expected work with any browser that supports proxies (nearly any browser does), and can forward
-requests to another HTTP proxy.</longdescription>
- <upstream>
- <remote-id type="sourceforge">bfilter</remote-id>
- </upstream>
-</pkgmetadata>