This is adapted from http://rightfootin.blogspot.com/2009...th-polipo.html, and is aimed at Maemo 5. For Maemo 4, the main things you need to consider are auto-starting the app (upstart is not available), and if the polipo package is available, the default configuration may be different.

Setup Polipo

Polipo isn't available from app manager, it only seems to exist as a dependency for tor.. so:

Not sure which repository you'll need, and heed the "at your own risk" disclaimers mentioned a million times.

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:

Look for:

And comment:

Now we want polipo to begin at boot time, so create

Like this:

(any comments on how this should really be for this type of app, please let me know, I am new to upstart).

Set Up Blocking

Polipo uses a "forbidden" list in What we are going to do is download the standard adblock list, and convert it to something polipo understands.

First, get adblocktopolipo.py and save to /usr/bin

Then Create a backup copy of the default forbidden.list (not entirely necessary, but the script below expects it. Also, you can use this file to keep any custom blocks you want:

Then save this script somewhere sensible. Mine is in /etc/polipo/update which is not sensible:

Enable execute:

Now you can run the script as root to get a fresh copy of the block list, install into polipo and restart it.

Using Polipo AdBlocking

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:

Make it Better

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
Make sure it says:

Then add:

Now all we need is the gif image file:

Restart polipo:

Caveats

The easylist.txt download and conversion had a line beginning with

The initial + should be escaped, and polipo ignores the entire forbidden list because it fails to parse.

Edit forbidden and change the line to:

Or just delete it.

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:

Good:

Cheers,

Paul