Dramaticus,<p>I emailed the author. He contacted SURBL. They say that bit.ly is now using the SURBL black list but that they don't prevent shortening of black listed URLs; instead, they show the warning that you saw. He's changed his post.
Went to bit.ly.<p>Shortened <a href="http://blizzard.warcraft.info-management-review.net/securityconfirm.html" rel="nofollow">http://blizzard.warcraft.info-management-review.net/security...</a> to <a href="http://bit.ly/e61JJQ" rel="nofollow">http://bit.ly/e61JJQ</a>.<p>Went to <a href="http://cli.gs/" rel="nofollow">http://cli.gs/</a> (which blocked all in the article)
It happily shortened <a href="http://bit.ly/e61JJQ" rel="nofollow">http://bit.ly/e61JJQ</a> to <a href="http://cli.gs/qdbui1x" rel="nofollow">http://cli.gs/qdbui1x</a><p>When I clicked on it cli.gs kindly draws me a preview image of the bit.ly warning page that says<p>"STOP - there might be a problem with the requested link"<p>I have no idea who wins that round !