|
2010-03-28
, 18:12
|
Posts: 1,950 |
Thanked: 1,174 times |
Joined on Jan 2008
@ Seattle, USA
|
#2
|
|
2010-03-28
, 23:14
|
Posts: 422 |
Thanked: 244 times |
Joined on Feb 2008
|
#3
|
Do you find it much more helpful than just relying on a hosts file?
Are all your instructions equally applicable for Maemo 4 and Maemo 5?
The Following User Says Thank You to paulkoan For This Useful Post: | ||
|
2010-03-29
, 02:54
|
Posts: 422 |
Thanked: 244 times |
Joined on Feb 2008
|
#4
|
Setup Polipo
Polipo isn't available from app manager, it only seems to exist as a dependency for tor.. so:
The polipo app comes ready configured to work with tor. This post assumes you don't want to use tor, so we need to change the polipo config. Use leafpad or vi:
Set Up Blocking
Polipo uses a "forbidden" list in
First, get adblocktopolipo.py and save to /usr/bin
Then
To use it, all you need do is point the proxy settings for each internet connection to polipo. Open Internet Connections in Settings. You will need to modify each connection you want ad blocking for.
Open the connection and hit Next until you see Advanced. Click that, and go to the Proxy tab. Change the http proxy to:
Now Polipo will return a 403 error for any blocked connection, and these are displayed in place of blocked ads. Which isn't cool. Unless you are happy with that, we need to make some more changes. The idea here is that instead of the 403 error, we return a small empty gif which is displayed in its place.
Edit the /etc/polipo/config file again, and look for
The easylist.txt download and conversion had a line beginning with
Edit forbidden and change the line to:
The conversion script needs to be updated to account for this, but until then, this works as a workaround. You can run polipo from the command line to see if everything is happy:
Bad:
Paul
Servwise Advanced Hosting - Better, Faster, Smarter
Hum Consulting - IT and Marketing services to sing about
Last edited by paulkoan; 2010-03-28 at 22:59.