<?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: Musings on open-ness, extensibility and the writeable web</title>
	<atom:link href="http://www.theequitykicker.com/2008/03/11/musings-on-open-ness-extensibility-and-the-writeable-web/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.theequitykicker.com/2008/03/11/musings-on-open-ness-extensibility-and-the-writeable-web/</link>
	<description>Nic Brisbourne's view from London on venture capital and exploiting change in technology and media</description>
	<lastBuildDate>Sat, 11 Feb 2012 20:08:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: paulpod</title>
		<link>http://www.theequitykicker.com/2008/03/11/musings-on-open-ness-extensibility-and-the-writeable-web/#comment-1509</link>
		<dc:creator>paulpod</dc:creator>
		<pubDate>Tue, 11 Mar 2008 16:20:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.theequitykicker.com/2008/03/11/musings-on-open-ness-extensibility-and-the-writeable-web/#comment-1509</guid>
		<description>I think the more recent changes to making software more accessible have been in the degrees of involvement. Previously it was picking a template style - or - hacking one together from scratch. No inbetween, no learning curve, just high level or low level involvement.

Now, you can pick a style, tinker with the elements, add widgets, dig into the style sheet (much easier to tweak than editing ALL the templates for example), connect to other data feeds, re-use the outputted content in other software or sites  ...all the way to digging into code.

This smooth transition from shallow to deep involvement, even if you break things and have to reinstall on the way, is really enabling many more people to &#039;do their thing&#039; now. It&#039;s great!</description>
		<content:encoded><![CDATA[<p>I think the more recent changes to making software more accessible have been in the degrees of involvement. Previously it was picking a template style &#8211; or &#8211; hacking one together from scratch. No inbetween, no learning curve, just high level or low level involvement.</p>
<p>Now, you can pick a style, tinker with the elements, add widgets, dig into the style sheet (much easier to tweak than editing ALL the templates for example), connect to other data feeds, re-use the outputted content in other software or sites  &#8230;all the way to digging into code.</p>
<p>This smooth transition from shallow to deep involvement, even if you break things and have to reinstall on the way, is really enabling many more people to &#8216;do their thing&#8217; now. It&#8217;s great!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: paulpod</title>
		<link>http://www.theequitykicker.com/2008/03/11/musings-on-open-ness-extensibility-and-the-writeable-web/#comment-11182</link>
		<dc:creator>paulpod</dc:creator>
		<pubDate>Tue, 11 Mar 2008 16:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.theequitykicker.com/2008/03/11/musings-on-open-ness-extensibility-and-the-writeable-web/#comment-11182</guid>
		<description>I think the more recent changes to making software more accessible have been in the degrees of involvement. Previously it was picking a template style - or - hacking one together from scratch. No inbetween, no learning curve, just high level or low level involvement.

Now, you can pick a style, tinker with the elements, add widgets, dig into the style sheet (much easier to tweak than editing ALL the templates for example), connect to other data feeds, re-use the outputted content in other software or sites  ...all the way to digging into code.

This smooth transition from shallow to deep involvement, even if you break things and have to reinstall on the way, is really enabling many more people to &#039;do their thing&#039; now. It&#039;s great!</description>
		<content:encoded><![CDATA[<p>I think the more recent changes to making software more accessible have been in the degrees of involvement. Previously it was picking a template style &#8211; or &#8211; hacking one together from scratch. No inbetween, no learning curve, just high level or low level involvement.</p>
<p>Now, you can pick a style, tinker with the elements, add widgets, dig into the style sheet (much easier to tweak than editing ALL the templates for example), connect to other data feeds, re-use the outputted content in other software or sites  &#8230;all the way to digging into code.</p>
<p>This smooth transition from shallow to deep involvement, even if you break things and have to reinstall on the way, is really enabling many more people to &#8216;do their thing&#8217; now. It&#8217;s great!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Open Social How To &#187; Musings on open-ness, extensibility and the writeable web</title>
		<link>http://www.theequitykicker.com/2008/03/11/musings-on-open-ness-extensibility-and-the-writeable-web/#comment-1508</link>
		<dc:creator>Open Social How To &#187; Musings on open-ness, extensibility and the writeable web</dc:creator>
		<pubDate>Tue, 11 Mar 2008 14:19:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.theequitykicker.com/2008/03/11/musings-on-open-ness-extensibility-and-the-writeable-web/#comment-1508</guid>
		<description>[...] Original post by The Equity Kicker [...]</description>
		<content:encoded><![CDATA[<p>[...] Original post by The Equity Kicker [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.228 seconds -->

