<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"

	>
<channel>
	<title>Comments on: GitHub Has Been Unblocked, Maybe</title>
	<atom:link href="http://beijingcream.com/2013/01/github-has-been-unblocked-maybe/feed/" rel="self" type="application/rss+xml" />
	<link>http://beijingcream.com/2013/01/github-has-been-unblocked-maybe/</link>
	<description>A Dollop of China</description>
	<lastBuildDate>Tue, 22 Jan 2019 17:42:34 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: The Good Doctor</title>
		<link>http://beijingcream.com/2013/01/github-has-been-unblocked-maybe/#comment-216660</link>
		<dc:creator><![CDATA[The Good Doctor]]></dc:creator>
		<pubDate>Thu, 24 Jan 2013 08:15:07 +0000</pubDate>
		<guid isPermaLink="false">http://beijingcream.com/?p=9449#comment-216660</guid>
		<description><![CDATA[he said tea bag, he he he.]]></description>
		<content:encoded><![CDATA[<p>he said tea bag, he he he.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Johnson</title>
		<link>http://beijingcream.com/2013/01/github-has-been-unblocked-maybe/#comment-216656</link>
		<dc:creator><![CDATA[Martin Johnson]]></dc:creator>
		<pubDate>Thu, 24 Jan 2013 07:55:47 +0000</pubDate>
		<guid isPermaLink="false">http://beijingcream.com/?p=9449#comment-216656</guid>
		<description><![CDATA[As the founder of GreatFire.org, quoted above, let me clarify that GitHub was indeed fully unblocked (https://en.greatfire.org/github.com). The connection-reset as well as the DNS poisoning have both been lifted. When it comes to DNS poisoning, because of caching there&#039;s a delay before it works everywhere.

On the idea that the blocking may have been automatically triggered, I believe this is unlikely since GitHub was blocked using separate methods, introduced at different point in time. Generally, automatic blocking doesn&#039;t affect a whole website but certain URLs containing sensitive keywords.

The real challenge for the GFW authorities is HTTPS. GitHub is unblocked for now, but their temporary blocking of it didn&#039;t change anything. Because it&#039;s encrypted, they can&#039;t selectively block content. You can use GitHub to publish any content and the only thing they can do to stop you is to block the whole site. Which, as you point out, has commercial consequences and so they&#039;re reluctant to do it. Very interesting to follow.]]></description>
		<content:encoded><![CDATA[<p>As the founder of GreatFire.org, quoted above, let me clarify that GitHub was indeed fully unblocked (<a href="https://en.greatfire.org/github.com" rel="nofollow">https://en.greatfire.org/github.com</a>). The connection-reset as well as the DNS poisoning have both been lifted. When it comes to DNS poisoning, because of caching there&#8217;s a delay before it works everywhere.</p>
<p>On the idea that the blocking may have been automatically triggered, I believe this is unlikely since GitHub was blocked using separate methods, introduced at different point in time. Generally, automatic blocking doesn&#8217;t affect a whole website but certain URLs containing sensitive keywords.</p>
<p>The real challenge for the GFW authorities is HTTPS. GitHub is unblocked for now, but their temporary blocking of it didn&#8217;t change anything. Because it&#8217;s encrypted, they can&#8217;t selectively block content. You can use GitHub to publish any content and the only thing they can do to stop you is to block the whole site. Which, as you point out, has commercial consequences and so they&#8217;re reluctant to do it. Very interesting to follow.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
