<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Much is technically wrong</title>
	<atom:link href="http://blogs.law.harvard.edu/doc/2009/03/17/much-is-technically-wrong/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/doc/2009/03/17/much-is-technically-wrong/</link>
	<description>Same old blog, brand new place</description>
	<lastBuildDate>Fri, 04 Dec 2009 20:29:45 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Doc Searls</title>
		<link>http://blogs.law.harvard.edu/doc/2009/03/17/much-is-technically-wrong/comment-page-1/#comment-144661</link>
		<dc:creator>Doc Searls</dc:creator>
		<pubDate>Wed, 18 Mar 2009 10:19:06 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/2009/03/17/much-is-technically-wrong/#comment-144661</guid>
		<description>Thanks, Phil.

I always bring my own access point. Helps when they have Ethernet. The OMNI didn&#039;t. And its problem was something else. What mattered is that they knew they had a problem, during a major Internet-related trade show, and blew it off. I&#039;ll avoid staying there again.

As for the Skype problem, it was a bad file in a library on my wife&#039;s laptop. No blockage involved. This time, at least.</description>
		<content:encoded><![CDATA[<p>Thanks, Phil.</p>
<p>I always bring my own access point. Helps when they have Ethernet. The OMNI didn&#8217;t. And its problem was something else. What mattered is that they knew they had a problem, during a major Internet-related trade show, and blew it off. I&#8217;ll avoid staying there again.</p>
<p>As for the Skype problem, it was a bad file in a library on my wife&#8217;s laptop. No blockage involved. This time, at least.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Wolff</title>
		<link>http://blogs.law.harvard.edu/doc/2009/03/17/much-is-technically-wrong/comment-page-1/#comment-144448</link>
		<dc:creator>Phil Wolff</dc:creator>
		<pubDate>Wed, 18 Mar 2009 02:23:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/2009/03/17/much-is-technically-wrong/#comment-144448</guid>
		<description>Many of the ISPs that serve hotels block Skype. 

Two reasons. 

First is the &quot;Enterprise Overkill&quot; approach. Very aggressive security systems perceive Skype&#039;s p2p-ness and wily attempts to connect to other users as some sort of attack or the initiation of bandwidth-consuming bittorrents or file sharing. I&#039;ve sometimes fixed this with a call to the hotel&#039;s ISP&#039;s help desk and get some temporary policy exceptions. 

Second is the &quot;Emirates Protectionist&quot; strategy. Some hotels block Skype for commercial reasons. It cuts into their telephone surcharge revenue, especially if they cater to international business travelers. No joy if this is their motive. 

The counter meme is hotels that charge as much as the market will tolerate [bear or bare?] but that open up the pipes and leave you to a darwinian fight for bandwidth with your fellow tenants. 

My other bit of grief is that hotels say they offer wi-fi to all their rooms. They do. But your experience is vastly different if you are at the other end of the hall from a router. Tip 1: ask for rooms near a router if they don&#039;t have in-room ethernet. Tip 2: bring your own portable wireless access point and run it off of in-room ethernet.</description>
		<content:encoded><![CDATA[<p>Many of the ISPs that serve hotels block Skype. </p>
<p>Two reasons. </p>
<p>First is the &#8220;Enterprise Overkill&#8221; approach. Very aggressive security systems perceive Skype&#8217;s p2p-ness and wily attempts to connect to other users as some sort of attack or the initiation of bandwidth-consuming bittorrents or file sharing. I&#8217;ve sometimes fixed this with a call to the hotel&#8217;s ISP&#8217;s help desk and get some temporary policy exceptions. </p>
<p>Second is the &#8220;Emirates Protectionist&#8221; strategy. Some hotels block Skype for commercial reasons. It cuts into their telephone surcharge revenue, especially if they cater to international business travelers. No joy if this is their motive. </p>
<p>The counter meme is hotels that charge as much as the market will tolerate [bear or bare?] but that open up the pipes and leave you to a darwinian fight for bandwidth with your fellow tenants. </p>
<p>My other bit of grief is that hotels say they offer wi-fi to all their rooms. They do. But your experience is vastly different if you are at the other end of the hall from a router. Tip 1: ask for rooms near a router if they don&#8217;t have in-room ethernet. Tip 2: bring your own portable wireless access point and run it off of in-room ethernet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mic Edwards</title>
		<link>http://blogs.law.harvard.edu/doc/2009/03/17/much-is-technically-wrong/comment-page-1/#comment-143896</link>
		<dc:creator>Mic Edwards</dc:creator>
		<pubDate>Tue, 17 Mar 2009 14:34:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/doc/2009/03/17/much-is-technically-wrong/#comment-143896</guid>
		<description>Did you see this then?

http://heartbeat.skype.com/2009/03/planned_maintenance_on_tuesday.html</description>
		<content:encoded><![CDATA[<p>Did you see this then?</p>
<p><a href="http://heartbeat.skype.com/2009/03/planned_maintenance_on_tuesday.html" rel="nofollow">http://heartbeat.skype.com/2009/03/planned_maintenance_on_tuesday.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
