<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Home From China</title>
	<atom:link href="http://www.credoadvisors.com/blog/mba/home-from-china/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.credoadvisors.com/blog/mba/home-from-china/</link>
	<description>Credo Advisors Consulting Blog: Business Ethics &#038; Corporate Social Responsibility</description>
	<pubDate>Thu, 08 Jan 2009 12:11:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Peter Begley</title>
		<link>http://www.credoadvisors.com/blog/mba/home-from-china/#comment-1294</link>
		<dc:creator>Peter Begley</dc:creator>
		<pubDate>Tue, 04 Jul 2006 15:55:42 +0000</pubDate>
		<guid isPermaLink="false">http://credoadvisors.com/blog/?p=255#comment-1294</guid>
		<description>I found it interesting as well, though I can understand if the blocking was based simply on the appearance of choice keywords. What was confusing, however, was that it appeared that &lt;a href="http://www.google.cn/" rel="nofollow"&gt;google.cn&lt;/a&gt; (not ".com") successfully indexed this site, yet I was unable to click through, or view Google's cached version. Checking &lt;a href="http://www.google.cn/" rel="nofollow"&gt;google.cn&lt;/a&gt; this morning from California indeed shows that this site is indexed, and I was easily able to view the cached version of the site.

At times, it seemed that some of the filtration may have been occurring at the hotels we were staying at. For example, in Shenzhen, I was able to use iChat (Apple) to do a video conference with my wife and son, though the audio didn't work. In Shanghai, we were unable to use iChat for anything but text messaging, but were able to do a choppy video feed via Yahoo! Messenger. At all of our other destinations, we were only able to communicate through text messaging. 

I would chalk our difficulties up to connection speed but we supposedly had high-speed access at all of our hotels (and the performance of various sites seemed consistent at each). The more reasonable (though perhaps technically naïve) explanation is that our hotels, or their ISPs, were filtering content and certain data feeds. Regardless, not only was I unable to access this site (front and back-end) but all of the sites hosted on this server were blocked. I was also unable to access &lt;a href="http://www.technorati.com/" rel="nofollow"&gt;technorati.com&lt;/a&gt; or &lt;a href="http://www.nytimes.com/" rel="nofollow"&gt;nytimes.com&lt;/a&gt;.

On the upside, &lt;a href="http://www.jackyan.com/blog/" rel="nofollow"&gt;jackyan.com&lt;/a&gt; was accessible in every city!</description>
		<content:encoded><![CDATA[<p>I found it interesting as well, though I can understand if the blocking was based simply on the appearance of choice keywords. What was confusing, however, was that it appeared that <a href="http://www.google.cn/" rel="nofollow">google.cn</a> (not &#8220;.com&#8221;) successfully indexed this site, yet I was unable to click through, or view Google&#8217;s cached version. Checking <a href="http://www.google.cn/" rel="nofollow">google.cn</a> this morning from California indeed shows that this site is indexed, and I was easily able to view the cached version of the site.</p>
<p>At times, it seemed that some of the filtration may have been occurring at the hotels we were staying at. For example, in Shenzhen, I was able to use iChat (Apple) to do a video conference with my wife and son, though the audio didn&#8217;t work. In Shanghai, we were unable to use iChat for anything but text messaging, but were able to do a choppy video feed via Yahoo! Messenger. At all of our other destinations, we were only able to communicate through text messaging. </p>
<p>I would chalk our difficulties up to connection speed but we supposedly had high-speed access at all of our hotels (and the performance of various sites seemed consistent at each). The more reasonable (though perhaps technically naïve) explanation is that our hotels, or their ISPs, were filtering content and certain data feeds. Regardless, not only was I unable to access this site (front and back-end) but all of the sites hosted on this server were blocked. I was also unable to access <a href="http://www.technorati.com/" rel="nofollow">technorati.com</a> or <a href="http://www.nytimes.com/" rel="nofollow">nytimes.com</a>.</p>
<p>On the upside, <a href="http://www.jackyan.com/blog/" rel="nofollow">jackyan.com</a> was accessible in every city!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack Yan</title>
		<link>http://www.credoadvisors.com/blog/mba/home-from-china/#comment-1292</link>
		<dc:creator>Jack Yan</dc:creator>
		<pubDate>Tue, 04 Jul 2006 12:37:04 +0000</pubDate>
		<guid isPermaLink="false">http://credoadvisors.com/blog/?p=255#comment-1292</guid>
		<description>Amazing that your blog was blocked, considering there is nothing in it that I would consider in&#64258;ammatory to the Politburo in Beijing. It shows that the bans can be rather sweeping.</description>
		<content:encoded><![CDATA[<p>Amazing that your blog was blocked, considering there is nothing in it that I would consider in&#64258;ammatory to the Politburo in Beijing. It shows that the bans can be rather sweeping.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
