<?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: The softer side of Tom</title>
	<atom:link href="http://www.rockmycar.net/2004/09/26/the-softer-side-of-tom/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rockmycar.net/2004/09/26/the-softer-side-of-tom/</link>
	<description>Rants from San Diego journalist &#038; bartender Tom Chambers</description>
	<lastBuildDate>Tue, 07 Feb 2012 04:07:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Andrew Phelps</title>
		<link>http://www.rockmycar.net/2004/09/26/the-softer-side-of-tom/comment-page-1/#comment-140</link>
		<dc:creator>Andrew Phelps</dc:creator>
		<pubDate>Sun, 17 Oct 2004 05:20:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.rockmycar.com/index.php/archives/2004/09/26/the-softer-side-of-tom/#comment-140</guid>
		<description>Layla,

MT-Blacklist. TRUST ME.

http://www.jayallen.org/projects/mt-blacklist/</description>
		<content:encoded><![CDATA[<p>Layla,</p>
<p>MT-Blacklist. TRUST ME.</p>
<p><a href="http://www.jayallen.org/projects/mt-blacklist/" rel="nofollow">http://www.jayallen.org/projects/mt-blacklist/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Layla</title>
		<link>http://www.rockmycar.net/2004/09/26/the-softer-side-of-tom/comment-page-1/#comment-139</link>
		<dc:creator>Layla</dc:creator>
		<pubDate>Fri, 15 Oct 2004 15:45:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.rockmycar.com/index.php/archives/2004/09/26/the-softer-side-of-tom/#comment-139</guid>
		<description>OK, so I&#039;m commenting long after the fact, but I&#039;ll echo Stephen and say that I like the indented paragraphs, too. Maybe it&#039;s a newspaper thing... I&#039;m also interested in seeing how WordPress works over the long-term. Movable Type is fine for me, except for the fact that deleting spam comments is a pain in the ass, because I have to rebuild the entire site just to make one change.</description>
		<content:encoded><![CDATA[<p>OK, so I&#8217;m commenting long after the fact, but I&#8217;ll echo Stephen and say that I like the indented paragraphs, too. Maybe it&#8217;s a newspaper thing&#8230; I&#8217;m also interested in seeing how WordPress works over the long-term. Movable Type is fine for me, except for the fact that deleting spam comments is a pain in the ass, because I have to rebuild the entire site just to make one change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen</title>
		<link>http://www.rockmycar.net/2004/09/26/the-softer-side-of-tom/comment-page-1/#comment-127</link>
		<dc:creator>Stephen</dc:creator>
		<pubDate>Thu, 30 Sep 2004 23:51:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.rockmycar.com/index.php/archives/2004/09/26/the-softer-side-of-tom/#comment-127</guid>
		<description>I too would like a comment tally (I tried saying this earlier at work yesterday, but my comment got eaten mysteriously).

And I like the indented paragraphs, personally.</description>
		<content:encoded><![CDATA[<p>I too would like a comment tally (I tried saying this earlier at work yesterday, but my comment got eaten mysteriously).</p>
<p>And I like the indented paragraphs, personally.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Phelps</title>
		<link>http://www.rockmycar.net/2004/09/26/the-softer-side-of-tom/comment-page-1/#comment-125</link>
		<dc:creator>Andrew Phelps</dc:creator>
		<pubDate>Thu, 30 Sep 2004 21:14:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.rockmycar.com/index.php/archives/2004/09/26/the-softer-side-of-tom/#comment-125</guid>
		<description>Plus, I would like to see a comment tally attached to each entry on the front page, rather than having to click the permalink and scrolling down,</description>
		<content:encoded><![CDATA[<p>Plus, I would like to see a comment tally attached to each entry on the front page, rather than having to click the permalink and scrolling down,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Phelps</title>
		<link>http://www.rockmycar.net/2004/09/26/the-softer-side-of-tom/comment-page-1/#comment-123</link>
		<dc:creator>Andrew Phelps</dc:creator>
		<pubDate>Tue, 28 Sep 2004 22:31:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.rockmycar.com/index.php/archives/2004/09/26/the-softer-side-of-tom/#comment-123</guid>
		<description>Congratulations on the redesign. I used to design in the mindset of a Print Person -- with perfect boxes, to the pixel. But the Web doesn&#039;t work that way, with the number of varying browsers and resolutions and systems out there. I&#039;m learning to create more clean, open designs that focus on content -- and that&#039;s the way this redesign looks. No more popups, either. I really like it.

Nice job with the comments feed in RSS. Nice job having your picture and description underneath so the reader understands what he&#039;s looking at right away. However, I suggest keeping this consistent throughout the site. When someone on another blog permalinks one of your posts, a foreign reader would like to see that description text to know where he is. You could put data relating to the post in the area that actually contains the content.

I admire the indented paragraph approach, but it doesn&#039;t work. No indents.

Also, while your weblog is relatively young, I highly suggest you future-proof your permanent links and take out PHP code like &quot;p=140&quot;. If you use headlines for links and organize them by date (like I do), your links won&#039;t change in two weeks or two years when you change your CMS or ditch PHP. Plus, headlines and dates don&#039;t change in two weeks or two years.

I love the one-image approach. Besides the webcam image, my weblog&#039;s base design is the same way. It&#039;s amazing what you can do with two colors (black and white) and all the shades thereof. You take advantage of that.

Finally, I am confused by your &quot;keep reading&quot; link. I think cuts, as they&#039;re sometimes called in blogs, should be reserved for only very long posts. It was weird to have to click a link to read the remaining nine words of your Zell Miller post.

I hope all my suggestions make sense,</description>
		<content:encoded><![CDATA[<p>Congratulations on the redesign. I used to design in the mindset of a Print Person &#8212; with perfect boxes, to the pixel. But the Web doesn&#8217;t work that way, with the number of varying browsers and resolutions and systems out there. I&#8217;m learning to create more clean, open designs that focus on content &#8212; and that&#8217;s the way this redesign looks. No more popups, either. I really like it.</p>
<p>Nice job with the comments feed in RSS. Nice job having your picture and description underneath so the reader understands what he&#8217;s looking at right away. However, I suggest keeping this consistent throughout the site. When someone on another blog permalinks one of your posts, a foreign reader would like to see that description text to know where he is. You could put data relating to the post in the area that actually contains the content.</p>
<p>I admire the indented paragraph approach, but it doesn&#8217;t work. No indents.</p>
<p>Also, while your weblog is relatively young, I highly suggest you future-proof your permanent links and take out PHP code like &#8220;p=140&#8243;. If you use headlines for links and organize them by date (like I do), your links won&#8217;t change in two weeks or two years when you change your CMS or ditch PHP. Plus, headlines and dates don&#8217;t change in two weeks or two years.</p>
<p>I love the one-image approach. Besides the webcam image, my weblog&#8217;s base design is the same way. It&#8217;s amazing what you can do with two colors (black and white) and all the shades thereof. You take advantage of that.</p>
<p>Finally, I am confused by your &#8220;keep reading&#8221; link. I think cuts, as they&#8217;re sometimes called in blogs, should be reserved for only very long posts. It was weird to have to click a link to read the remaining nine words of your Zell Miller post.</p>
<p>I hope all my suggestions make sense,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen</title>
		<link>http://www.rockmycar.net/2004/09/26/the-softer-side-of-tom/comment-page-1/#comment-122</link>
		<dc:creator>Stephen</dc:creator>
		<pubDate>Tue, 28 Sep 2004 04:09:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.rockmycar.com/index.php/archives/2004/09/26/the-softer-side-of-tom/#comment-122</guid>
		<description>I dig especially that I&#039;m not reading the Log in a little box.  For those of us running at higher resolutions, it&#039;s very nice.

One thing: this post is truncated on the main page, and it wasn&#039;t obvious to me how to read all of it.  I realize now that if you click the post title, it&#039;s a link to the whole thing, but since the post title is black and not underlined, it doesn&#039;t look like a link.  If you added a &quot;Read More...&quot; button or something, it would probably help a lot.

P.S. Also, if my e-mail address is required to comment (why?), you should note that on the comment form.</description>
		<content:encoded><![CDATA[<p>I dig especially that I&#8217;m not reading the Log in a little box.  For those of us running at higher resolutions, it&#8217;s very nice.</p>
<p>One thing: this post is truncated on the main page, and it wasn&#8217;t obvious to me how to read all of it.  I realize now that if you click the post title, it&#8217;s a link to the whole thing, but since the post title is black and not underlined, it doesn&#8217;t look like a link.  If you added a &#8220;Read More&#8230;&#8221; button or something, it would probably help a lot.</p>
<p>P.S. Also, if my e-mail address is required to comment (why?), you should note that on the comment form.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

