(You may have to hit "Submit" on that page--it needs to set a cookie before it allows you to see the list) but I got tired of the unreliability, slowness and security risks of using someone else's proxy. I ended up setting up my own proxy server using CGIProxy.
All you need to do to use CGIProxy is find a web hosting service that provides cgi-bin access (unfortunately, not free... but I use my web host for many other services that make it well worth the few dollars per month) and then plop the CGIProxy script on the server.
I've been happily retrieving bone-headedly blocked sites quickly and reliably ever since. (And sorry, I will not reveal its address. I've learned the hard way that it's best to keep your personal proxies to yourself.)
Mike, security through obfuscation is very unreliable. Somebody will find your proxy, if they haven't already. I suggest setting up a .htaccess file for basic password protection. There are dozens of online tutorials on this, or contact your web host for help.
I actually do have a restrictive .htaccess set up (user/pass authentication), and I check my logs regularly to make sure no monkey-business is occurring. I keep the address of my proxy private as to avoid the thousands of hits I would otherwise incur when the address makes it way to one of the many "open proxies" lists (even though access is denied).
Believe me, once your address makes it to one of those lists, it never comes off (and is a good resource for filtering software to find "proxy avoidance" URLs for blocking).