<?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: Placing Blame Where Blame Deserves to Be Placed</title>
	<atom:link href="http://www.blogherald.com/2007/03/08/placing-blame-where-blame-deserves-to-be-placed/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blogherald.com/2007/03/08/placing-blame-where-blame-deserves-to-be-placed/</link>
	<description>The leading source of news covering social media and the blogosphere.</description>
	<lastBuildDate>Mon, 13 Feb 2012 09:18:59 +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: WordPress Wednesday News: WordCamp South Africa, World of WordCamps, Blaming WordPress, and Crazyhorse Gallops &#124; The Blog Herald</title>
		<link>http://www.blogherald.com/2007/03/08/placing-blame-where-blame-deserves-to-be-placed/comment-page-1/#comment-579676</link>
		<dc:creator>WordPress Wednesday News: WordCamp South Africa, World of WordCamps, Blaming WordPress, and Crazyhorse Gallops &#124; The Blog Herald</dc:creator>
		<pubDate>Wed, 27 Aug 2008 17:34:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/03/08/placing-blame-where-blame-deserves-to-be-placed/#comment-579676</guid>
		<description>[...] blaming the WordPress team for problems they have no control over, specifically, WordPress Plugins. I&#8217;ve written on this subject before and I agree. WordPress is an ongoing product in constant development and will undergo changes. For [...]</description>
		<content:encoded><![CDATA[<p>[...] blaming the WordPress team for problems they have no control over, specifically, WordPress Plugins. I&#8217;ve written on this subject before and I agree. WordPress is an ongoing product in constant development and will undergo changes. For [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bloggers Who Blame Don&#8217;t Change Things : The Blog Herald</title>
		<link>http://www.blogherald.com/2007/03/08/placing-blame-where-blame-deserves-to-be-placed/comment-page-1/#comment-223382</link>
		<dc:creator>Bloggers Who Blame Don&#8217;t Change Things : The Blog Herald</dc:creator>
		<pubDate>Fri, 19 Oct 2007 11:17:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/03/08/placing-blame-where-blame-deserves-to-be-placed/#comment-223382</guid>
		<description>[...] Placing Blame Where Blame Deserves to Be Placed, I wrote about how many bloggers throw blame on the wrong personal or company and how we need to be [...]</description>
		<content:encoded><![CDATA[<p>[...] Placing Blame Where Blame Deserves to Be Placed, I wrote about how many bloggers throw blame on the wrong personal or company and how we need to be [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blog Herald Brags About Lorelle &#171; Lorelle on WordPress</title>
		<link>http://www.blogherald.com/2007/03/08/placing-blame-where-blame-deserves-to-be-placed/comment-page-1/#comment-174612</link>
		<dc:creator>Blog Herald Brags About Lorelle &#171; Lorelle on WordPress</dc:creator>
		<pubDate>Thu, 15 Mar 2007 18:27:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/03/08/placing-blame-where-blame-deserves-to-be-placed/#comment-174612</guid>
		<description>[...] Placing Blame Where Blame Deserves to Be Placed [...]</description>
		<content:encoded><![CDATA[<p>[...] Placing Blame Where Blame Deserves to Be Placed [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: engtech</title>
		<link>http://www.blogherald.com/2007/03/08/placing-blame-where-blame-deserves-to-be-placed/comment-page-1/#comment-173290</link>
		<dc:creator>engtech</dc:creator>
		<pubDate>Thu, 08 Mar 2007 16:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/03/08/placing-blame-where-blame-deserves-to-be-placed/#comment-173290</guid>
		<description>Hi Lorelle,

I have a &lt;a href=&quot;http://engtech.wordpress.com/tools/wordpress/findwideimages/&quot; rel=&quot;nofollow&quot;&gt;greasemonkey script for Firefox&lt;/a&gt; that gives you a big stinking warning if you break your box model. I created it for exactly that reason... breaking the box on IE6 but it looks fine on Firefox.</description>
		<content:encoded><![CDATA[<p>Hi Lorelle,</p>
<p>I have a <a href="http://engtech.wordpress.com/tools/wordpress/findwideimages/" rel="nofollow">greasemonkey script for Firefox</a> that gives you a big stinking warning if you break your box model. I created it for exactly that reason&#8230; breaking the box on IE6 but it looks fine on Firefox.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Neumann</title>
		<link>http://www.blogherald.com/2007/03/08/placing-blame-where-blame-deserves-to-be-placed/comment-page-1/#comment-173211</link>
		<dc:creator>Martin Neumann</dc:creator>
		<pubDate>Thu, 08 Mar 2007 10:12:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2007/03/08/placing-blame-where-blame-deserves-to-be-placed/#comment-173211</guid>
		<description>Yay, I think I recently fell for the easy way of blaming WP (in a ranty sort of post) when if thinking straight it was probably a database issue with my web host. :-)

... but then what if it was a WP issue that screwed with my database, hmmm...  Either way, when you loose an hour or so of work (even if after saving every 5 minutes or so) you gotta blame somebody. :-)</description>
		<content:encoded><![CDATA[<p>Yay, I think I recently fell for the easy way of blaming WP (in a ranty sort of post) when if thinking straight it was probably a database issue with my web host. :-)</p>
<p>&#8230; but then what if it was a WP issue that screwed with my database, hmmm&#8230;  Either way, when you loose an hour or so of work (even if after saving every 5 minutes or so) you gotta blame somebody. :-)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

