<?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: Software constraints in blogging software</title>
	<atom:link href="http://www.annehelmond.nl/2006/12/01/software-constraints-in-blogging-software/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.annehelmond.nl/2006/12/01/software-constraints-in-blogging-software/</link>
	<description>Anne Helmond. New Media Research Blog</description>
	<lastBuildDate>Tue, 31 Jan 2012 18:43:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: anne</title>
		<link>http://www.annehelmond.nl/2006/12/01/software-constraints-in-blogging-software/comment-page-1/#comment-234</link>
		<dc:creator>anne</dc:creator>
		<pubDate>Wed, 13 Dec 2006 13:14:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.annehelmond.nl/2006/12/01/software-constraints-in-blogging-software/#comment-234</guid>
		<description></description>
		<content:encoded><![CDATA[<p>Dear Justin,</p>
<p>Thank you for your comments. My thesis should be ready and available for download somewhere during the summer of 2007 (if all goes well and according to planning of course ;) ) Right now I would consider plug ins an answer to the constraints WordPress imposes on its users. Unfortunately only programmers have the ability to work around these constraints because they have the technical wizz to actually build a custom solution to the posed constraint/problem. I think it would be also useful and interesting too look at the community that is creating and writing these plug ins. Also the larger trend of widgets is worth looking at. The â€œWidgetize Anythingâ€? WordPress plug in is a great example of this. Oi oi. It is time to get my scope narrowed down :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Shattuck</title>
		<link>http://www.annehelmond.nl/2006/12/01/software-constraints-in-blogging-software/comment-page-1/#comment-186</link>
		<dc:creator>Justin Shattuck</dc:creator>
		<pubDate>Mon, 04 Dec 2006 16:50:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.annehelmond.nl/2006/12/01/software-constraints-in-blogging-software/#comment-186</guid>
		<description>Anne,

First, good luck with your Thesis.  I am hoping to find a digital copy over time that I could read once you&#039;re finished with your research and writing.  

There exists numerous issues when trying to &quot;remove restrictions&quot; across Wordpress.  Some questions you might ask yourself, are we creating more restrictions with plugins.  Are plugins in themselves, restrictions?  Creating a system or framework such as wordpress that has hooks available for everything imagineable is nearly impossible, or would require a huge amount of time.

Plugins simply modify data, adjust output and display various levels of information based upon what a user wants.  You can&#039;t please everyone; unfortunately.</description>
		<content:encoded><![CDATA[<p>Anne,</p>
<p>First, good luck with your Thesis.  I am hoping to find a digital copy over time that I could read once you&#8217;re finished with your research and writing.  </p>
<p>There exists numerous issues when trying to &#8220;remove restrictions&#8221; across WordPress.  Some questions you might ask yourself, are we creating more restrictions with plugins.  Are plugins in themselves, restrictions?  Creating a system or framework such as wordpress that has hooks available for everything imagineable is nearly impossible, or would require a huge amount of time.</p>
<p>Plugins simply modify data, adjust output and display various levels of information based upon what a user wants.  You can&#8217;t please everyone; unfortunately.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

