Twitter, Flickr, Bing, *.live.com, Hotmail blocked in China
uk.techcrunch.com
uk.techcrunch.com
Well, this is the first compelling reason to switch to Bing I've seen to date. Maybe I'll give it a spin later.
They gain popularity in China to the point that the country is reliant on it, and the government is comfortable with Google because they're given some control. Then, at some point in the future once enough of a fuss has been made about Google helping China, Google gives China an ultimatum, either they end the censorship or Google leaves China. Google can claim it's bad for their business to help China censor, when in reality they were planning it all along...
Unlikely, but who knows?
Maybe we should write letters, wherein we express that we are pleased that MS's search engine division isn't cooperating with China, and that we've started using Bing for this reason.
Fat lot of good it's doing them. I expect that some, probably most, of these blocks will stay in effect for a while. The 60th anniversary of the founding of the People's Republic is coming up this fall, so the authorities are busy creating a "harmonious society" in preparation.
FWIW, the mood here in Beijing is increasingly tense. Not a lot of fun.
It would be cool if someone could make an open source project deployable on GAE or heroku to proxy twitter. It could self redirect daily to another instance of the app, making it unblockable. I don't know much about blocking btw.
Currently Google's services could be accessed with simple technics, just modify your browsers PAC (proxy auto config) to this http://gfwtf.googlecode.com/svn/gfwtf.pac
And just curious: does anyone happens to know an Akamai node within China that could deliver contents over GFW?
I observed twitter has been trying to change IP for at least three times, but it's a URL block. Any port 80 TCP request that has a twitter.com between GET and HTTP/1.1 will be blocked.
Just checked and twitter.com will accept an HTTP/1.0 request (which doesn't require a host to be specified). So one way to get around this block might be to set up a local proxy that uses HTTP/1.0 to connect remotely.
the GFW will RST your again and again even if you Google for twitter.com