<?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/"
		>
<channel>
	<title>Comments on: Lessons from the Ice Storm</title>
	<atom:link href="http://redmonk.com/sogrady/2008/12/16/ice-storm-lessons/feed/" rel="self" type="application/rss+xml" />
	<link>http://redmonk.com/sogrady/2008/12/16/ice-storm-lessons/</link>
	<description>because technology is just another ecosystem</description>
	<lastBuildDate>Sun, 13 May 2012 00:23:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: mike</title>
		<link>http://redmonk.com/sogrady/2008/12/16/ice-storm-lessons/comment-page-1/#comment-501849</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Wed, 17 Dec 2008 07:44:38 +0000</pubDate>
		<guid isPermaLink="false">http://redmonk.com/sogrady/?p=2595#comment-501849</guid>
		<description>this gets back to the whole push/pull discussion for getting information out.

my 0.02€ on this; update the website with a link to a very light page (or change the home page for the duration) that details current status (locations without that resource and latest expected restoration) and the next update time. 
This &quot;next update time&quot; should at least initally have *big* time gaps (4-6 hours), along with the explanation that the time gap is big as everyone is busy mobilising and the situation is very fluid and they don&#039;t want to overload it with status reports, as time passes, this time gap i would expect to naturally come down as more information is natuarally flowing.

My preference for updateing a web-page is that:
 - stores/bars/cafes can, if they so desire, as a service publish this information
 - media services can re-broadcast it, without putting extra load on the utility company. The reduction of &quot;load on the utility that this provides should not be under-estimated. Also those media outlets (that are clever) can advertise the fact that they are *not* currently trying to talk to the utility company so that more effort can be put into the fix
 - people can contact relatives/friends outside the problem area and ask them to check the website for them.</description>
		<content:encoded><![CDATA[<p>this gets back to the whole push/pull discussion for getting information out.</p>
<p>my 0.02€ on this; update the website with a link to a very light page (or change the home page for the duration) that details current status (locations without that resource and latest expected restoration) and the next update time.<br />
This &#8220;next update time&#8221; should at least initally have *big* time gaps (4-6 hours), along with the explanation that the time gap is big as everyone is busy mobilising and the situation is very fluid and they don&#8217;t want to overload it with status reports, as time passes, this time gap i would expect to naturally come down as more information is natuarally flowing.</p>
<p>My preference for updateing a web-page is that:<br />
 &#8211; stores/bars/cafes can, if they so desire, as a service publish this information<br />
 &#8211; media services can re-broadcast it, without putting extra load on the utility company. The reduction of &#8220;load on the utility that this provides should not be under-estimated. Also those media outlets (that are clever) can advertise the fact that they are *not* currently trying to talk to the utility company so that more effort can be put into the fix<br />
 &#8211; people can contact relatives/friends outside the problem area and ask them to check the website for them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Object Caching 230/231 objects using xcache

Served from: redmonk.com @ 2012-05-26 18:09:24 -->
