<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: The network is the keyboard: Patterns of scalable communication</title>
	<atom:link href="http://blog.jonudell.net/2010/06/29/the-network-is-the-keyboard-patterns-of-scalable-communication/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jonudell.net/2010/06/29/the-network-is-the-keyboard-patterns-of-scalable-communication/</link>
	<description>Strategies for Internet citizens</description>
	<lastBuildDate>Mon, 13 Feb 2012 06:40:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Jon Udell</title>
		<link>http://blog.jonudell.net/2010/06/29/the-network-is-the-keyboard-patterns-of-scalable-communication/#comment-137268</link>
		<dc:creator><![CDATA[Jon Udell]]></dc:creator>
		<pubDate>Thu, 30 Sep 2010 15:32:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/?p=2517#comment-137268</guid>
		<description><![CDATA[&lt;i&gt;This is broadcasting, not something I would call communication between people.&lt;/i&gt;

Fair point. At Sal&#039;s level, you&#039;re right, it&#039;s broadcasting. But there aren&#039;t many at that level. For the rest of us, communication can scale, albeit imperfectly.]]></description>
		<content:encoded><![CDATA[<p><i>This is broadcasting, not something I would call communication between people.</i></p>
<p>Fair point. At Sal&#8217;s level, you&#8217;re right, it&#8217;s broadcasting. But there aren&#8217;t many at that level. For the rest of us, communication can scale, albeit imperfectly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Stapfer</title>
		<link>http://blog.jonudell.net/2010/06/29/the-network-is-the-keyboard-patterns-of-scalable-communication/#comment-137243</link>
		<dc:creator><![CDATA[Christian Stapfer]]></dc:creator>
		<pubDate>Wed, 29 Sep 2010 16:47:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/?p=2517#comment-137243</guid>
		<description><![CDATA[Having 60&#039;000 subscribers on youtube is &quot;communication&quot;? - Are you kidding? - This is broadcasting, not something I would call communication between people: it is a very one-sided thing.

It&#039;s like saying that having 60&#039;000 friends on facebook is scaling friendship by a factor of about 10&#039;000. - Those are friends, I mean real friends?]]></description>
		<content:encoded><![CDATA[<p>Having 60&#8217;000 subscribers on youtube is &#8220;communication&#8221;? &#8211; Are you kidding? &#8211; This is broadcasting, not something I would call communication between people: it is a very one-sided thing.</p>
<p>It&#8217;s like saying that having 60&#8217;000 friends on facebook is scaling friendship by a factor of about 10&#8217;000. &#8211; Those are friends, I mean real friends?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Leeke</title>
		<link>http://blog.jonudell.net/2010/06/29/the-network-is-the-keyboard-patterns-of-scalable-communication/#comment-137071</link>
		<dc:creator><![CDATA[John Leeke]]></dc:creator>
		<pubDate>Mon, 20 Sep 2010 11:00:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/?p=2517#comment-137071</guid>
		<description><![CDATA[I get a lot of questions from readers about restoring historic buildings. For 15 years I have been selecting some of my email responses and posting them at my discussion Forum:

http://historichomeworks.com/forum/index.php

So, I can refer similar queries to that response. In this way &quot;narrow-cast&quot; becomes &quot;broadcast.&quot; They are often viewed by 10 or 100 more people than my original correspondent. Often the response develops into a full discussion that is viewed by tens of thousands of people.

My forum system gives me a count of viewers. Here&#039;s an example:
http://historichomeworks.com/forum/viewforum.php?f=16
You will see one near the top with 90,000 viewers, some with thousands of viewers and some with hundreds.

When I see a discussion drifting up into the tens of thousands I select it to edit and add to my original response at the top of the discussion by summarizing the discussion beneath, and adding more recent material. As this body of text develops I add illustrations in form of photos, sketches and videos.

Here is an example on removing paint with steam (92,000 views):
http://historichomeworks.com/forum/viewtopic.php?t=133

and another on glazing windows with putty (32,000 views):
http://historichomeworks.com/forum/viewtopic.php?t=955

When a topic has matured and has between 50,000 and 100,000 views I published in my little series of booklets and books:

http://www.historichomeworks.com/hhw/reports/reports.htm

I might add it to an existing title (which I publish with Print On Demand services and can easily update), or create a new title.

This bumps the readership of my response to that original query up into the hundreds of thousands.

This approach is definitely saving me keystrokes. And, helping a lot of people along the way, too.

John
by hammer and hand great works do stand
by pen and thought best words are wrought]]></description>
		<content:encoded><![CDATA[<p>I get a lot of questions from readers about restoring historic buildings. For 15 years I have been selecting some of my email responses and posting them at my discussion Forum:</p>
<p><a href="http://historichomeworks.com/forum/index.php" rel="nofollow">http://historichomeworks.com/forum/index.php</a></p>
<p>So, I can refer similar queries to that response. In this way &#8220;narrow-cast&#8221; becomes &#8220;broadcast.&#8221; They are often viewed by 10 or 100 more people than my original correspondent. Often the response develops into a full discussion that is viewed by tens of thousands of people.</p>
<p>My forum system gives me a count of viewers. Here&#8217;s an example:<br />
<a href="http://historichomeworks.com/forum/viewforum.php?f=16" rel="nofollow">http://historichomeworks.com/forum/viewforum.php?f=16</a><br />
You will see one near the top with 90,000 viewers, some with thousands of viewers and some with hundreds.</p>
<p>When I see a discussion drifting up into the tens of thousands I select it to edit and add to my original response at the top of the discussion by summarizing the discussion beneath, and adding more recent material. As this body of text develops I add illustrations in form of photos, sketches and videos.</p>
<p>Here is an example on removing paint with steam (92,000 views):<br />
<a href="http://historichomeworks.com/forum/viewtopic.php?t=133" rel="nofollow">http://historichomeworks.com/forum/viewtopic.php?t=133</a></p>
<p>and another on glazing windows with putty (32,000 views):<br />
<a href="http://historichomeworks.com/forum/viewtopic.php?t=955" rel="nofollow">http://historichomeworks.com/forum/viewtopic.php?t=955</a></p>
<p>When a topic has matured and has between 50,000 and 100,000 views I published in my little series of booklets and books:</p>
<p><a href="http://www.historichomeworks.com/hhw/reports/reports.htm" rel="nofollow">http://www.historichomeworks.com/hhw/reports/reports.htm</a></p>
<p>I might add it to an existing title (which I publish with Print On Demand services and can easily update), or create a new title.</p>
<p>This bumps the readership of my response to that original query up into the hundreds of thousands.</p>
<p>This approach is definitely saving me keystrokes. And, helping a lot of people along the way, too.</p>
<p>John<br />
by hammer and hand great works do stand<br />
by pen and thought best words are wrought</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Internet Traffic Monitoring &#124; Generate Website Traffic</title>
		<link>http://blog.jonudell.net/2010/06/29/the-network-is-the-keyboard-patterns-of-scalable-communication/#comment-136115</link>
		<dc:creator><![CDATA[Internet Traffic Monitoring &#124; Generate Website Traffic]]></dc:creator>
		<pubDate>Tue, 29 Jun 2010 23:25:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/?p=2517#comment-136115</guid>
		<description><![CDATA[[...] The network is the keyboard: Patterns of scalable communication &#8230; [...]]]></description>
		<content:encoded><![CDATA[<p>[...] The network is the keyboard: Patterns of scalable communication &#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Udell</title>
		<link>http://blog.jonudell.net/2010/06/29/the-network-is-the-keyboard-patterns-of-scalable-communication/#comment-136097</link>
		<dc:creator><![CDATA[Jon Udell]]></dc:creator>
		<pubDate>Tue, 29 Jun 2010 20:02:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/?p=2517#comment-136097</guid>
		<description><![CDATA[Really? 

I would say that the point is to practice what in another context is called open notebook science.

As, by the way, you are doing very effectively at http://zvolkov.com/blog/.]]></description>
		<content:encoded><![CDATA[<p>Really? </p>
<p>I would say that the point is to practice what in another context is called open notebook science.</p>
<p>As, by the way, you are doing very effectively at <a href="http://zvolkov.com/blog/" rel="nofollow">http://zvolkov.com/blog/</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: zvolkov</title>
		<link>http://blog.jonudell.net/2010/06/29/the-network-is-the-keyboard-patterns-of-scalable-communication/#comment-136074</link>
		<dc:creator><![CDATA[zvolkov]]></dc:creator>
		<pubDate>Tue, 29 Jun 2010 17:01:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/?p=2517#comment-136074</guid>
		<description><![CDATA[The point was, we will all die, dummy :)]]></description>
		<content:encoded><![CDATA[<p>The point was, we will all die, dummy :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

