Poop! I’ve just followed a link to a slashdot article only to discover that ‘my’ IP has been banned!
Either your network or ip address has been banned from Slashdot
…due to script flooding that originated from your network or ip address — or this IP might have been used to post comments designed to break web browser rendering. Or you crawled us with a rude robot, especially one that doesn’t understand RFCs very well…
I know that NTL, my ISP, recently changed their transparent proxies so that they stopped giving out originating IP addresses. So a quick check, by pointing my browser’s proxy setting to another NTL proxy, had slashdot’s server give me the page. So I know that it is the transparent NTL proxy server that has been banned not me!
I’ll have to email NTL and see if they will contact slashdot.
Update: It’s seemed to be resolved now, without me getting round to contacting NTL. I guess there were a few people affected and someone else got in touch before me.