<?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: Apologies to Everyone</title>
	<atom:link href="http://firedoglake.com/2006/03/14/apologies-to-everyone/feed/" rel="self" type="application/rss+xml" />
	<link>http://firedoglake.com/2006/03/14/apologies-to-everyone/</link>
	<description>Firedoglake weblog</description>
	<lastBuildDate>Wed, 25 Nov 2009 17:07:52 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Violet Socks</title>
		<link>http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52788</link>
		<dc:creator>Violet Socks</dc:creator>
		<pubDate>Wed, 15 Mar 2006 06:21:06 +0000</pubDate>
		<guid isPermaLink="false">http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52788</guid>
		<description>&lt;p&gt;It’s understandable that some regulars don’t like the new design.  People like the familiar.  &lt;/p&gt;
&lt;p&gt;Personally, I think the old design was holding FDL back, keeping it from growing even faster than it was. People coming from Daily Kos had to content themselves with great writing, and just endure the confusing site design and godawful haloscan comments. I know a few who gave up.  &lt;/p&gt;
&lt;p&gt;As fast as FDL has been growing, I’m positive it will grow even faster with a more robust design — which this is.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>It’s understandable that some regulars don’t like the new design.  People like the familiar.  </p>
<p>Personally, I think the old design was holding FDL back, keeping it from growing even faster than it was. People coming from Daily Kos had to content themselves with great writing, and just endure the confusing site design and godawful haloscan comments. I know a few who gave up.  </p>
<p>As fast as FDL has been growing, I’m positive it will grow even faster with a more robust design — which this is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ccmask</title>
		<link>http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52738</link>
		<dc:creator>ccmask</dc:creator>
		<pubDate>Wed, 15 Mar 2006 05:33:50 +0000</pubDate>
		<guid isPermaLink="false">http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52738</guid>
		<description>&lt;p&gt;testing smiley &lt;/p&gt;
&lt;p&gt; :evil:&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>testing smiley </p>
<p> :evil:</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bluelib</title>
		<link>http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52596</link>
		<dc:creator>bluelib</dc:creator>
		<pubDate>Wed, 15 Mar 2006 04:06:17 +0000</pubDate>
		<guid isPermaLink="false">http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52596</guid>
		<description>&lt;p&gt;I love FDL, but really dislike your new format.  In a word, it sucks. The old one was great, why change it if it isn’t broken.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>I love FDL, but really dislike your new format.  In a word, it sucks. The old one was great, why change it if it isn’t broken.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Violet Socks</title>
		<link>http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52587</link>
		<dc:creator>Violet Socks</dc:creator>
		<pubDate>Wed, 15 Mar 2006 04:02:52 +0000</pubDate>
		<guid isPermaLink="false">http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52587</guid>
		<description>&lt;p&gt;The new design of FDL is a template I recognize, since I use it at one of my websites.  It looks like FDL is using it straight out of the box.  It’s not poorly written code at all — actually it’s very well written.  No reason for Blue Host to have a problem with it.&lt;/p&gt;
&lt;p&gt;The backgrounds, margins, and various other settings can be easily changed by the user.  Comment preview and things like that are plugins that FDL will need to add in (as with any Wordpress template).&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>The new design of FDL is a template I recognize, since I use it at one of my websites.  It looks like FDL is using it straight out of the box.  It’s not poorly written code at all — actually it’s very well written.  No reason for Blue Host to have a problem with it.</p>
<p>The backgrounds, margins, and various other settings can be easily changed by the user.  Comment preview and things like that are plugins that FDL will need to add in (as with any Wordpress template).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: skippy</title>
		<link>http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52451</link>
		<dc:creator>skippy</dc:creator>
		<pubDate>Wed, 15 Mar 2006 02:50:51 +0000</pubDate>
		<guid isPermaLink="false">http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52451</guid>
		<description>&lt;p&gt;so, i’m no longer on your blogroll?&lt;/p&gt;
&lt;p&gt;gee, i remember a time when i got an email from someone named jane asking why some new blog called “firedoglake” was no longer linked to on skippy.&lt;/p&gt;
&lt;p&gt;how soon they forget.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>so, i’m no longer on your blogroll?</p>
<p>gee, i remember a time when i got an email from someone named jane asking why some new blog called “firedoglake” was no longer linked to on skippy.</p>
<p>how soon they forget.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PJB (UK)</title>
		<link>http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52423</link>
		<dc:creator>PJB (UK)</dc:creator>
		<pubDate>Wed, 15 Mar 2006 02:33:21 +0000</pubDate>
		<guid isPermaLink="false">http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52423</guid>
		<description>&lt;p&gt;Avid reader though I may be, Jane, I have to rain on your parade: the new layout is just plain horrible. &lt;/p&gt;
&lt;p&gt;* The ‘Read the rest of this entry’ links are clunky and slow. Compare with “expand/collapse post” links at &lt;a href=&quot;http://thinkprogress.org/&quot; title=&quot;Link to Think Progress&quot;&gt;Think Progress&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;* The background is straight out of M$ Frontpage - as used by every kewl 14 year-old. &lt;/p&gt;
&lt;p&gt;* The indents on quoted material are unnecessary and unattractive.  And you haven’t got room for them: for example, the fixed space occupied by the outer columns means that the user’s browser window must now be more than 900 pixels wide in order to accommodate the graphic in “How Much Do Senate Democrats Like the President?”; otherwise the graphic is truncated. (Pity those who use 800×600 resolution.)&lt;/p&gt;
&lt;p&gt;Oh, and as others have commented, you *really* need a preview button (God knows how the above thinkprogress.org link will appear).&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Avid reader though I may be, Jane, I have to rain on your parade: the new layout is just plain horrible. </p>
<p>* The ‘Read the rest of this entry’ links are clunky and slow. Compare with “expand/collapse post” links at <a href="http://thinkprogress.org/" title="Link to Think Progress">Think Progress</a>.</p>
<p>* The background is straight out of M$ Frontpage &#8211; as used by every kewl 14 year-old. </p>
<p>* The indents on quoted material are unnecessary and unattractive.  And you haven’t got room for them: for example, the fixed space occupied by the outer columns means that the user’s browser window must now be more than 900 pixels wide in order to accommodate the graphic in “How Much Do Senate Democrats Like the President?”; otherwise the graphic is truncated. (Pity those who use 800×600 resolution.)</p>
<p>Oh, and as others have commented, you *really* need a preview button (God knows how the above thinkprogress.org link will appear).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: travy</title>
		<link>http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52374</link>
		<dc:creator>travy</dc:creator>
		<pubDate>Wed, 15 Mar 2006 01:49:33 +0000</pubDate>
		<guid isPermaLink="false">http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52374</guid>
		<description>&lt;p&gt;i likes, but a narrower center column would be much easier to read…&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>i likes, but a narrower center column would be much easier to read…</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alank</title>
		<link>http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52315</link>
		<dc:creator>alank</dc:creator>
		<pubDate>Wed, 15 Mar 2006 01:05:56 +0000</pubDate>
		<guid isPermaLink="false">http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52315</guid>
		<description>&lt;p&gt;Yo, WordPress doesn’t include comment previewing, but you can easily install a plug-in that will allow this option for commenters.  Here’s an example: &lt;a href=&quot;http://dev.wp-plugins.org/wiki/LiveCommentPreview&quot;&gt;LiveCommentPreview&lt;/a&gt;&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Yo, WordPress doesn’t include comment previewing, but you can easily install a plug-in that will allow this option for commenters.  Here’s an example: <a href="http://dev.wp-plugins.org/wiki/LiveCommentPreview">LiveCommentPreview</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: shargash</title>
		<link>http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52219</link>
		<dc:creator>shargash</dc:creator>
		<pubDate>Tue, 14 Mar 2006 23:50:28 +0000</pubDate>
		<guid isPermaLink="false">http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52219</guid>
		<description>&lt;p&gt;The comment preview function is definitely needed. It is hard enough to get HTML tags right, even when you can see what you’re going to get. Also, there are some definite bugs in the posting. I had part of a post eaten earlier, possibly because of some mal-formed HTML, but I have no way of knowing for sure.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>The comment preview function is definitely needed. It is hard enough to get HTML tags right, even when you can see what you’re going to get. Also, there are some definite bugs in the posting. I had part of a post eaten earlier, possibly because of some mal-formed HTML, but I have no way of knowing for sure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mrs. K8</title>
		<link>http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52208</link>
		<dc:creator>Mrs. K8</dc:creator>
		<pubDate>Tue, 14 Mar 2006 23:40:19 +0000</pubDate>
		<guid isPermaLink="false">http://firedoglake.com/2006/03/14/apologies-to-everyone/#comment-52208</guid>
		<description>&lt;p&gt;Testing, 1-2-3, testing.&lt;/p&gt;
&lt;p&gt;Got here late in the day, and am not computer-savvy enough to understand lots of the lingo being used to describe different hosting scenarios.&lt;/p&gt;
&lt;p&gt;But I know how to be patient!  And maybe I’ll pick up some knowledge along the way.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Testing, 1-2-3, testing.</p>
<p>Got here late in the day, and am not computer-savvy enough to understand lots of the lingo being used to describe different hosting scenarios.</p>
<p>But I know how to be patient!  And maybe I’ll pick up some knowledge along the way.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
