<?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: FeedFlare? No Thank You.</title>
	<atom:link href="http://johnlamansky.com/tech/feedflare-no-thank-you/feed/" rel="self" type="application/rss+xml" />
	<link>http://johnlamansky.com/tech/feedflare-no-thank-you/#utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=feedflare-no-thank-you</link>
	<description></description>
	<lastBuildDate>Fri, 18 May 2012 16:58:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: John Lamansky &#187; Blog Archive &#187; Blogosphere Trend: Customer Service Comments</title>
		<link>http://johnlamansky.com/tech/feedflare-no-thank-you/comment-page-1/#comment-147</link>
		<dc:creator>John Lamansky &#187; Blog Archive &#187; Blogosphere Trend: Customer Service Comments</dc:creator>
		<pubDate>Fri, 21 Jul 2006 02:47:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnlamansky.com/?p=147#comment-147</guid>
		<description>[...] It seems that it&#8217;s becoming more and more common for company representatives to post comments on blog posts related to that company or its products. For example, so far on this blog I&#8217;ve had comments from FeedBurner, Dell, and Microsoft employees, plus a comment from the CEO of FeedBlitz. [...] </description>
		<content:encoded><![CDATA[<p>[...] It seems that it&#8217;s becoming more and more common for company representatives to post comments on blog posts related to that company or its products. For example, so far on this blog I&#8217;ve had comments from FeedBurner, Dell, and Microsoft employees, plus a comment from the CEO of FeedBlitz. [...] </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Lamansky</title>
		<link>http://johnlamansky.com/tech/feedflare-no-thank-you/comment-page-1/#comment-146</link>
		<dc:creator>John Lamansky</dc:creator>
		<pubDate>Mon, 30 Jan 2006 03:01:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnlamansky.com/?p=147#comment-146</guid>
		<description>Thanks John Z. For my desired feature set, I chose to use HTML rather than FeedFlare because I figured HTML would be much easier than creating a universally-compatible CSS customization solution for FeedFlare. I still do think custom HTML is better for simple links like &quot;email this post&quot; or &quot;add to del.icio.us.&quot; But thanks to your explanations and tips, I&#039;ll probably consider utilizing FeedFlare again if I want to incorporate features that I cannot easily create myself, such as displaying the number of incoming Technorati links.

Thanks for all your work with FeedBurner! It&#039;s a great service.</description>
		<content:encoded><![CDATA[<p>Thanks John Z. For my desired feature set, I chose to use HTML rather than FeedFlare because I figured HTML would be much easier than creating a universally-compatible CSS customization solution for FeedFlare. I still do think custom HTML is better for simple links like &#8220;email this post&#8221; or &#8220;add to del.icio.us.&#8221; But thanks to your explanations and tips, I&#8217;ll probably consider utilizing FeedFlare again if I want to incorporate features that I cannot easily create myself, such as displaying the number of incoming Technorati links.</p>
<p>Thanks for all your work with FeedBurner! It&#8217;s a great service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Zeratsky</title>
		<link>http://johnlamansky.com/tech/feedflare-no-thank-you/comment-page-1/#comment-145</link>
		<dc:creator>John Zeratsky</dc:creator>
		<pubDate>Sun, 29 Jan 2006 21:02:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.johnlamansky.com/?p=147#comment-145</guid>
		<description>Thanks for your comments, John. I&#039;d like to chime in here on a couple of the things you mentioned...

I definitely feel your Javascript pain -- it&#039;s just not as flexible or transparent as good ol&#039; HTML. We decided to go with Javascript so we could:

a) make enhancements and improvements to the code we are delivering, and 
b) never force you to edit your template more than once. 

With a Javascript include, you can go back to FeedBurner.com at any time and change your FeedFlare settings -- we&#039;ll instantly update the code that gets sent to your web site.

As for CSS, trust me -- no CSS3 is required. You might have to get a little inventive, but you can do pretty much anything you want with basic (and well-supported) CSS 1 and 2. 

Want to replace the bullets? &lt;a href=&quot;http://phark.typepad.com/phark/2003/08/accessible_imag.html&quot; rel=&quot;nofollow&quot;&gt;Hide them&lt;/a&gt;, then place a background image as your separator. Want to list the links vertically? Set display:block on the &lt;a&gt; elements. Don&#039;t like the &lt;p&gt;? It&#039;s a block-level element just like &lt;div&gt; and you can do whatever you like with it.

We tried to balance our publishers&#039; desire to customize FeedFlare&#039;s look with our desire to make it easy and to make it work &quot;out of the box&quot; for our publishers. I think we&#039;ve done a good job of that, but we&#039;re always open to feedback. Thank you for yours!</description>
		<content:encoded><![CDATA[<p>Thanks for your comments, John. I&#8217;d like to chime in here on a couple of the things you mentioned&#8230;</p>
<p>I definitely feel your Javascript pain &#8212; it&#8217;s just not as flexible or transparent as good ol&#8217; HTML. We decided to go with Javascript so we could:</p>
<p>a) make enhancements and improvements to the code we are delivering, and<br />
b) never force you to edit your template more than once. </p>
<p>With a Javascript include, you can go back to FeedBurner.com at any time and change your FeedFlare settings &#8212; we&#8217;ll instantly update the code that gets sent to your web site.</p>
<p>As for CSS, trust me &#8212; no CSS3 is required. You might have to get a little inventive, but you can do pretty much anything you want with basic (and well-supported) CSS 1 and 2. </p>
<p>Want to replace the bullets? <a href="http://phark.typepad.com/phark/2003/08/accessible_imag.html" rel="nofollow">Hide them</a>, then place a background image as your separator. Want to list the links vertically? Set display:block on the &lt;a&gt; elements. Don&#8217;t like the &lt;p&gt;? It&#8217;s a block-level element just like &lt;div&gt; and you can do whatever you like with it.</p>
<p>We tried to balance our publishers&#8217; desire to customize FeedFlare&#8217;s look with our desire to make it easy and to make it work &#8220;out of the box&#8221; for our publishers. I think we&#8217;ve done a good job of that, but we&#8217;re always open to feedback. Thank you for yours!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced

Served from: johnlamansky.com @ 2012-05-21 08:16:42 -->
