<?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: Why We Need a Next Generation RSS</title>
	<atom:link href="http://www.chrisg.com/why-we-need-a-next-generation-rss/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/</link>
	<description>Build your business by sharing what you know</description>
	<lastBuildDate>Wed, 08 Feb 2012 23:51:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Chris Garrett</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-629</link>
		<dc:creator>Chris Garrett</dc:creator>
		<pubDate>Fri, 09 Mar 2007 09:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-629</guid>
		<description>There are a few ways to skin this cat. My preferred solution would be &quot;vanilla feed / personalised feed&quot; with the latter taking you to a form where you can add your name, perhaps email address, then some checkboxes for what you want to see. The feed would then look like /feed/ or /feed/?user=5678ghjdsa6y23 (for e.g.)

Main challenge is getting the platform vendors (drupal, wordpress, MT, ...) and feed/reader developers (google, blogbridge, feedburner) to agree on a decent standard that will enable additional features consistently</description>
		<content:encoded><![CDATA[<p>There are a few ways to skin this cat. My preferred solution would be &#8220;vanilla feed / personalised feed&#8221; with the latter taking you to a form where you can add your name, perhaps email address, then some checkboxes for what you want to see. The feed would then look like /feed/ or /feed/?user=5678ghjdsa6y23 (for e.g.)</p>
<p>Main challenge is getting the platform vendors (drupal, wordpress, MT, &#8230;) and feed/reader developers (google, blogbridge, feedburner) to agree on a decent standard that will enable additional features consistently</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Garrett</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14477</link>
		<dc:creator>Chris Garrett</dc:creator>
		<pubDate>Fri, 09 Mar 2007 09:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14477</guid>
		<description>There are a few ways to skin this cat. My preferred solution would be &quot;vanilla feed / personalised feed&quot; with the latter taking you to a form where you can add your name, perhaps email address, then some checkboxes for what you want to see. The feed would then look like /feed/ or /feed/?user=5678ghjdsa6y23 (for e.g.)

Main challenge is getting the platform vendors (drupal, wordpress, MT, ...) and feed/reader developers (google, blogbridge, feedburner) to agree on a decent standard that will enable additional features consistently</description>
		<content:encoded><![CDATA[<p>There are a few ways to skin this cat. My preferred solution would be &#8220;vanilla feed / personalised feed&#8221; with the latter taking you to a form where you can add your name, perhaps email address, then some checkboxes for what you want to see. The feed would then look like /feed/ or /feed/?user=5678ghjdsa6y23 (for e.g.)</p>
<p>Main challenge is getting the platform vendors (drupal, wordpress, MT, &#8230;) and feed/reader developers (google, blogbridge, feedburner) to agree on a decent standard that will enable additional features consistently</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ankesh Kothari</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-622</link>
		<dc:creator>Ankesh Kothari</dc:creator>
		<pubDate>Fri, 09 Mar 2007 06:07:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-622</guid>
		<description>Thanks Chris.

I&#039;m not a programmer, but have to work with several programmers - and so have caught on some of the logic.

How RSS+ would work is simple:

Create unique RSS links.  

For example:

www.site.com/rss-00012.rss

If some one places that RSS feed in their reader, the database automatically creates a new RSS link:

www.site.com/rss-00013.rss

If some one places that RSS feed in their reader, the database creates another new RSS link - and so on.

But here is the personalization problem - to personalize, you have to get the name and other values.  Your dentist can&#039;t send you a personalized postcard without knowing your name.  Most people use RSS because they can be anonymous.  They won&#039;t fill forms and give you their names just to access the RSS feed.  Because that would then be just like email.

Even though RSS+ idea may not be the best for personalization, its a good idea for tracking.  You could keep a track as to which &quot;number&quot; clicks on the links from which post...</description>
		<content:encoded><![CDATA[<p>Thanks Chris.</p>
<p>I&#8217;m not a programmer, but have to work with several programmers &#8211; and so have caught on some of the logic.</p>
<p>How RSS+ would work is simple:</p>
<p>Create unique RSS links.  </p>
<p>For example:</p>
<p><a href="http://www.site.com/rss-00012.rss" rel="nofollow">http://www.site.com/rss-00012.rss</a></p>
<p>If some one places that RSS feed in their reader, the database automatically creates a new RSS link:</p>
<p><a href="http://www.site.com/rss-00013.rss" rel="nofollow">http://www.site.com/rss-00013.rss</a></p>
<p>If some one places that RSS feed in their reader, the database creates another new RSS link &#8211; and so on.</p>
<p>But here is the personalization problem &#8211; to personalize, you have to get the name and other values.  Your dentist can&#8217;t send you a personalized postcard without knowing your name.  Most people use RSS because they can be anonymous.  They won&#8217;t fill forms and give you their names just to access the RSS feed.  Because that would then be just like email.</p>
<p>Even though RSS+ idea may not be the best for personalization, its a good idea for tracking.  You could keep a track as to which &#8220;number&#8221; clicks on the links from which post&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ankesh Kothari</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14476</link>
		<dc:creator>Ankesh Kothari</dc:creator>
		<pubDate>Fri, 09 Mar 2007 06:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14476</guid>
		<description>Thanks Chris.

I&#039;m not a programmer, but have to work with several programmers - and so have caught on some of the logic.

How RSS+ would work is simple:

Create unique RSS links.  

For example:

www.site.com/rss-00012.rss

If some one places that RSS feed in their reader, the database automatically creates a new RSS link:

www.site.com/rss-00013.rss

If some one places that RSS feed in their reader, the database creates another new RSS link - and so on.

But here is the personalization problem - to personalize, you have to get the name and other values.  Your dentist can&#039;t send you a personalized postcard without knowing your name.  Most people use RSS because they can be anonymous.  They won&#039;t fill forms and give you their names just to access the RSS feed.  Because that would then be just like email.

Even though RSS+ idea may not be the best for personalization, its a good idea for tracking.  You could keep a track as to which &quot;number&quot; clicks on the links from which post...</description>
		<content:encoded><![CDATA[<p>Thanks Chris.</p>
<p>I&#8217;m not a programmer, but have to work with several programmers &#8211; and so have caught on some of the logic.</p>
<p>How RSS+ would work is simple:</p>
<p>Create unique RSS links.  </p>
<p>For example:</p>
<p><a href="http://www.site.com/rss-00012.rss" rel="nofollow">http://www.site.com/rss-00012.rss</a></p>
<p>If some one places that RSS feed in their reader, the database automatically creates a new RSS link:</p>
<p><a href="http://www.site.com/rss-00013.rss" rel="nofollow">http://www.site.com/rss-00013.rss</a></p>
<p>If some one places that RSS feed in their reader, the database creates another new RSS link &#8211; and so on.</p>
<p>But here is the personalization problem &#8211; to personalize, you have to get the name and other values.  Your dentist can&#8217;t send you a personalized postcard without knowing your name.  Most people use RSS because they can be anonymous.  They won&#8217;t fill forms and give you their names just to access the RSS feed.  Because that would then be just like email.</p>
<p>Even though RSS+ idea may not be the best for personalization, its a good idea for tracking.  You could keep a track as to which &#8220;number&#8221; clicks on the links from which post&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashish Mohta</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-478</link>
		<dc:creator>Ashish Mohta</dc:creator>
		<pubDate>Sun, 04 Mar 2007 15:03:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-478</guid>
		<description>Thats a good suggestion.We can talk more to our readers and get some info.Wish i can add comment box in my feed.They can send comment from the feed itself</description>
		<content:encoded><![CDATA[<p>Thats a good suggestion.We can talk more to our readers and get some info.Wish i can add comment box in my feed.They can send comment from the feed itself</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashish Mohta</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14475</link>
		<dc:creator>Ashish Mohta</dc:creator>
		<pubDate>Sun, 04 Mar 2007 15:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14475</guid>
		<description>Thats a good suggestion.We can talk more to our readers and get some info.Wish i can add comment box in my feed.They can send comment from the feed itself</description>
		<content:encoded><![CDATA[<p>Thats a good suggestion.We can talk more to our readers and get some info.Wish i can add comment box in my feed.They can send comment from the feed itself</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Garrett</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-477</link>
		<dc:creator>Chris Garrett</dc:creator>
		<pubDate>Sun, 04 Mar 2007 15:02:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-477</guid>
		<description>Imagine if publishers could know what an individual is reading or ignoring. Then picture on the bottom of posts small links so readers would be able to say &quot;more like this please&quot; &quot;no more of this&quot;.

Not terribly hard to do, but it would take RSS feed reader developers to get on board.

Anyone worried about privacy could still subscribe to vanilla RSS.</description>
		<content:encoded><![CDATA[<p>Imagine if publishers could know what an individual is reading or ignoring. Then picture on the bottom of posts small links so readers would be able to say &#8220;more like this please&#8221; &#8220;no more of this&#8221;.</p>
<p>Not terribly hard to do, but it would take RSS feed reader developers to get on board.</p>
<p>Anyone worried about privacy could still subscribe to vanilla RSS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Garrett</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14474</link>
		<dc:creator>Chris Garrett</dc:creator>
		<pubDate>Sun, 04 Mar 2007 15:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14474</guid>
		<description>Imagine if publishers could know what an individual is reading or ignoring. Then picture on the bottom of posts small links so readers would be able to say &quot;more like this please&quot; &quot;no more of this&quot;.

Not terribly hard to do, but it would take RSS feed reader developers to get on board.

Anyone worried about privacy could still subscribe to vanilla RSS.</description>
		<content:encoded><![CDATA[<p>Imagine if publishers could know what an individual is reading or ignoring. Then picture on the bottom of posts small links so readers would be able to say &#8220;more like this please&#8221; &#8220;no more of this&#8221;.</p>
<p>Not terribly hard to do, but it would take RSS feed reader developers to get on board.</p>
<p>Anyone worried about privacy could still subscribe to vanilla RSS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marjolein Hoekstra</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-476</link>
		<dc:creator>Marjolein Hoekstra</dc:creator>
		<pubDate>Sun, 04 Mar 2007 14:02:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-476</guid>
		<description>Personalization from publisher to subscriber is one thing, but is that really what you are looking for? I mean, even if I&#039;d address you as Dear {Whatever Your Name}, or would be able to splice in items that are of particular interest to you as my fan, it&#039;s still a one-way street. The most value in my opinion would come from obtaining feedback, comments, ratings, votes from people who are actually consuming the stuff you push out to them and who care to show their involvement with it. Then you&#039;d effectively know the difference between subscribers and readers.</description>
		<content:encoded><![CDATA[<p>Personalization from publisher to subscriber is one thing, but is that really what you are looking for? I mean, even if I&#8217;d address you as Dear {Whatever Your Name}, or would be able to splice in items that are of particular interest to you as my fan, it&#8217;s still a one-way street. The most value in my opinion would come from obtaining feedback, comments, ratings, votes from people who are actually consuming the stuff you push out to them and who care to show their involvement with it. Then you&#8217;d effectively know the difference between subscribers and readers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marjolein Hoekstra</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14473</link>
		<dc:creator>Marjolein Hoekstra</dc:creator>
		<pubDate>Sun, 04 Mar 2007 14:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14473</guid>
		<description>Personalization from publisher to subscriber is one thing, but is that really what you are looking for? I mean, even if I&#039;d address you as Dear {Whatever Your Name}, or would be able to splice in items that are of particular interest to you as my fan, it&#039;s still a one-way street. The most value in my opinion would come from obtaining feedback, comments, ratings, votes from people who are actually consuming the stuff you push out to them and who care to show their involvement with it. Then you&#039;d effectively know the difference between subscribers and readers.</description>
		<content:encoded><![CDATA[<p>Personalization from publisher to subscriber is one thing, but is that really what you are looking for? I mean, even if I&#8217;d address you as Dear {Whatever Your Name}, or would be able to splice in items that are of particular interest to you as my fan, it&#8217;s still a one-way street. The most value in my opinion would come from obtaining feedback, comments, ratings, votes from people who are actually consuming the stuff you push out to them and who care to show their involvement with it. Then you&#8217;d effectively know the difference between subscribers and readers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-471</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Sun, 04 Mar 2007 10:29:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-471</guid>
		<description>Yes Chris (or, if you wish, Mr. Garrett :) ), I think that is a good idea, and it would work, but more in theory than in practice. 

I do agree with the other commentators, that RSS works quite well because it is fairly easy to use. Time has become such a precious denominator that people cut corners whenever they can. And when you make up your list of priorities, filling out an RSS-Customization form is probably not on the top of the list. 

Could you develop a little more in what way you would personalize something like that if you had a chance to do it?

Thanks for the good thoughts.</description>
		<content:encoded><![CDATA[<p>Yes Chris (or, if you wish, Mr. Garrett <img src='http://www.chrisg.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  ), I think that is a good idea, and it would work, but more in theory than in practice. </p>
<p>I do agree with the other commentators, that RSS works quite well because it is fairly easy to use. Time has become such a precious denominator that people cut corners whenever they can. And when you make up your list of priorities, filling out an RSS-Customization form is probably not on the top of the list. </p>
<p>Could you develop a little more in what way you would personalize something like that if you had a chance to do it?</p>
<p>Thanks for the good thoughts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14472</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Sun, 04 Mar 2007 10:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14472</guid>
		<description>Yes Chris (or, if you wish, Mr. Garrett :) ), I think that is a good idea, and it would work, but more in theory than in practice. 

I do agree with the other commentators, that RSS works quite well because it is fairly easy to use. Time has become such a precious denominator that people cut corners whenever they can. And when you make up your list of priorities, filling out an RSS-Customization form is probably not on the top of the list. 

Could you develop a little more in what way you would personalize something like that if you had a chance to do it?

Thanks for the good thoughts.</description>
		<content:encoded><![CDATA[<p>Yes Chris (or, if you wish, Mr. Garrett <img src='http://www.chrisg.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  ), I think that is a good idea, and it would work, but more in theory than in practice. </p>
<p>I do agree with the other commentators, that RSS works quite well because it is fairly easy to use. Time has become such a precious denominator that people cut corners whenever they can. And when you make up your list of priorities, filling out an RSS-Customization form is probably not on the top of the list. </p>
<p>Could you develop a little more in what way you would personalize something like that if you had a chance to do it?</p>
<p>Thanks for the good thoughts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Garrett</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-470</link>
		<dc:creator>Chris Garrett</dc:creator>
		<pubDate>Sun, 04 Mar 2007 09:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-470</guid>
		<description>@Bes, It was tracking usage I had in mind but if you think about it a bot would probably have an abnormal pattern of behaviour that could be spotted. A human being would probably not read everything you write, and would maybe revisit posts they found interesting. Bots more than likely would read every post just once?</description>
		<content:encoded><![CDATA[<p>@Bes, It was tracking usage I had in mind but if you think about it a bot would probably have an abnormal pattern of behaviour that could be spotted. A human being would probably not read everything you write, and would maybe revisit posts they found interesting. Bots more than likely would read every post just once?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Garrett</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14471</link>
		<dc:creator>Chris Garrett</dc:creator>
		<pubDate>Sun, 04 Mar 2007 09:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14471</guid>
		<description>@Bes, It was tracking usage I had in mind but if you think about it a bot would probably have an abnormal pattern of behaviour that could be spotted. A human being would probably not read everything you write, and would maybe revisit posts they found interesting. Bots more than likely would read every post just once?</description>
		<content:encoded><![CDATA[<p>@Bes, It was tracking usage I had in mind but if you think about it a bot would probably have an abnormal pattern of behaviour that could be spotted. A human being would probably not read everything you write, and would maybe revisit posts they found interesting. Bots more than likely would read every post just once?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronalfy</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-463</link>
		<dc:creator>Ronalfy</dc:creator>
		<pubDate>Sat, 03 Mar 2007 22:45:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-463</guid>
		<description>Thanks for the mention Bes.  Chris, if you&#039;re curious, the plugin&#039;s location is at &lt;a href=&quot;http://www.devlounge.net/extras/feed-styler&quot; rel=&quot;nofollow&quot;&gt;Devlounge&lt;/a&gt;.  I noticed several searches on my personal site.</description>
		<content:encoded><![CDATA[<p>Thanks for the mention Bes.  Chris, if you&#8217;re curious, the plugin&#8217;s location is at <a href="http://www.devlounge.net/extras/feed-styler" rel="nofollow">Devlounge</a>.  I noticed several searches on my personal site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronalfy</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14470</link>
		<dc:creator>Ronalfy</dc:creator>
		<pubDate>Sat, 03 Mar 2007 22:45:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14470</guid>
		<description>Thanks for the mention Bes.  Chris, if you&#039;re curious, the plugin&#039;s location is at &lt;a href=&quot;http://www.devlounge.net/extras/feed-styler&quot; rel=&quot;nofollow&quot;&gt;Devlounge&lt;/a&gt;.  I noticed several searches on my personal site.</description>
		<content:encoded><![CDATA[<p>Thanks for the mention Bes.  Chris, if you&#8217;re curious, the plugin&#8217;s location is at <a href="http://www.devlounge.net/extras/feed-styler" rel="nofollow">Devlounge</a>.  I noticed several searches on my personal site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashish Mohta</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-462</link>
		<dc:creator>Ashish Mohta</dc:creator>
		<pubDate>Sat, 03 Mar 2007 21:22:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-462</guid>
		<description>Thats really a great idea.May be it can have the email id of the user which can be sent if the user has missed the feed or havent read it for long.That might work</description>
		<content:encoded><![CDATA[<p>Thats really a great idea.May be it can have the email id of the user which can be sent if the user has missed the feed or havent read it for long.That might work</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ashish Mohta</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14469</link>
		<dc:creator>Ashish Mohta</dc:creator>
		<pubDate>Sat, 03 Mar 2007 21:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14469</guid>
		<description>Thats really a great idea.May be it can have the email id of the user which can be sent if the user has missed the feed or havent read it for long.That might work</description>
		<content:encoded><![CDATA[<p>Thats really a great idea.May be it can have the email id of the user which can be sent if the user has missed the feed or havent read it for long.That might work</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bes Zain</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-458</link>
		<dc:creator>Bes Zain</dc:creator>
		<pubDate>Sat, 03 Mar 2007 18:25:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-458</guid>
		<description>You raise an important point Chris. Personalization will probably be brought to RSS sometime, though right now RSS feeds are easy to use because of requiring no registration whatsoever. You find a feed, copy its url and paste it into your rss reader. That&#039;s it. Maybe that is one of the reasons it is getting popular?

I think many people are simply considering RSS to be a concept that should never be fancy. Ronald from http://www.ronalfy.com created a plugin that adds custom css styling to feeds, and some users did not like the idea. They said they love RSS feeds because of them being simple and the same like any other RSS feed, both visually and in actual implementation.

I like your example of the dentist and the catalogue; I think adding a personal name really adds value to a message: &quot;Wow, this message is intended solely for me. I am a human being in their view, and not just another business transaction.&quot;

Sorry, but I got a bit confused about something you wrote, maybe I need to reread it a few times. You said:

&quot;How do you know on your blog, especially if you publish full feeds, if your subscribers are readers? Are they getting more involved or are you leaving them cold?&quot;

If you have time please, could you explain this a bit more if possible? Do you mean personalization allows us to know if we have real humans reading feeds or if it&#039;s only bots accessing our feeds? Or do you mean a way to track their personal usage of our feeds since we would know who they are if your ideas were implemented?

Thanks again for such a nice concept. RSS is wonderful, but it still isn&#039;t something that has changed everything [I mentioned this latter part a while back on my site]. I myself still prefer e-mail newsletters, as they are easier to manage on some levels, and I can see updates on sites like yours while reading other important emails also.</description>
		<content:encoded><![CDATA[<p>You raise an important point Chris. Personalization will probably be brought to RSS sometime, though right now RSS feeds are easy to use because of requiring no registration whatsoever. You find a feed, copy its url and paste it into your rss reader. That&#8217;s it. Maybe that is one of the reasons it is getting popular?</p>
<p>I think many people are simply considering RSS to be a concept that should never be fancy. Ronald from <a href="http://www.ronalfy.com" rel="nofollow">http://www.ronalfy.com</a> created a plugin that adds custom css styling to feeds, and some users did not like the idea. They said they love RSS feeds because of them being simple and the same like any other RSS feed, both visually and in actual implementation.</p>
<p>I like your example of the dentist and the catalogue; I think adding a personal name really adds value to a message: &#8220;Wow, this message is intended solely for me. I am a human being in their view, and not just another business transaction.&#8221;</p>
<p>Sorry, but I got a bit confused about something you wrote, maybe I need to reread it a few times. You said:</p>
<p>&#8220;How do you know on your blog, especially if you publish full feeds, if your subscribers are readers? Are they getting more involved or are you leaving them cold?&#8221;</p>
<p>If you have time please, could you explain this a bit more if possible? Do you mean personalization allows us to know if we have real humans reading feeds or if it&#8217;s only bots accessing our feeds? Or do you mean a way to track their personal usage of our feeds since we would know who they are if your ideas were implemented?</p>
<p>Thanks again for such a nice concept. RSS is wonderful, but it still isn&#8217;t something that has changed everything [I mentioned this latter part a while back on my site]. I myself still prefer e-mail newsletters, as they are easier to manage on some levels, and I can see updates on sites like yours while reading other important emails also.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bes Zain</title>
		<link>http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14468</link>
		<dc:creator>Bes Zain</dc:creator>
		<pubDate>Sat, 03 Mar 2007 18:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrisg.com/why-we-need-a-next-generation-rss/#comment-14468</guid>
		<description>You raise an important point Chris. Personalization will probably be brought to RSS sometime, though right now RSS feeds are easy to use because of requiring no registration whatsoever. You find a feed, copy its url and paste it into your rss reader. That&#039;s it. Maybe that is one of the reasons it is getting popular?

I think many people are simply considering RSS to be a concept that should never be fancy. Ronald from http://www.ronalfy.com created a plugin that adds custom css styling to feeds, and some users did not like the idea. They said they love RSS feeds because of them being simple and the same like any other RSS feed, both visually and in actual implementation.

I like your example of the dentist and the catalogue; I think adding a personal name really adds value to a message: &quot;Wow, this message is intended solely for me. I am a human being in their view, and not just another business transaction.&quot;

Sorry, but I got a bit confused about something you wrote, maybe I need to reread it a few times. You said:

&quot;How do you know on your blog, especially if you publish full feeds, if your subscribers are readers? Are they getting more involved or are you leaving them cold?&quot;

If you have time please, could you explain this a bit more if possible? Do you mean personalization allows us to know if we have real humans reading feeds or if it&#039;s only bots accessing our feeds? Or do you mean a way to track their personal usage of our feeds since we would know who they are if your ideas were implemented?

Thanks again for such a nice concept. RSS is wonderful, but it still isn&#039;t something that has changed everything [I mentioned this latter part a while back on my site]. I myself still prefer e-mail newsletters, as they are easier to manage on some levels, and I can see updates on sites like yours while reading other important emails also.</description>
		<content:encoded><![CDATA[<p>You raise an important point Chris. Personalization will probably be brought to RSS sometime, though right now RSS feeds are easy to use because of requiring no registration whatsoever. You find a feed, copy its url and paste it into your rss reader. That&#8217;s it. Maybe that is one of the reasons it is getting popular?</p>
<p>I think many people are simply considering RSS to be a concept that should never be fancy. Ronald from <a href="http://www.ronalfy.com" rel="nofollow">http://www.ronalfy.com</a> created a plugin that adds custom css styling to feeds, and some users did not like the idea. They said they love RSS feeds because of them being simple and the same like any other RSS feed, both visually and in actual implementation.</p>
<p>I like your example of the dentist and the catalogue; I think adding a personal name really adds value to a message: &#8220;Wow, this message is intended solely for me. I am a human being in their view, and not just another business transaction.&#8221;</p>
<p>Sorry, but I got a bit confused about something you wrote, maybe I need to reread it a few times. You said:</p>
<p>&#8220;How do you know on your blog, especially if you publish full feeds, if your subscribers are readers? Are they getting more involved or are you leaving them cold?&#8221;</p>
<p>If you have time please, could you explain this a bit more if possible? Do you mean personalization allows us to know if we have real humans reading feeds or if it&#8217;s only bots accessing our feeds? Or do you mean a way to track their personal usage of our feeds since we would know who they are if your ideas were implemented?</p>
<p>Thanks again for such a nice concept. RSS is wonderful, but it still isn&#8217;t something that has changed everything [I mentioned this latter part a while back on my site]. I myself still prefer e-mail newsletters, as they are easier to manage on some levels, and I can see updates on sites like yours while reading other important emails also.</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
Object Caching 652/656 objects using apc

Served from: chrisg.com @ 2012-02-09 05:45:13 -->
