That being said, I think I better understand your point.

What there needs to be is a universal way, built into the RSS standard, to allow people to give the OK for content reuse or to deny it. Ideally, such a system would be able to set flexible rules such as no images, only 250 words or only one article at a time.

I think the reason Google is stripping out these things is because they aren’t in the RSS standard. Still, I do agree they should keep the header information in, it’s just clear that improvement is needed on both sides of the fence here.

That being said, I think I better understand your point.

What there needs to be is a universal way, built into the RSS standard, to allow people to give the OK for content reuse or to deny it. Ideally, such a system would be able to set flexible rules such as no images, only 250 words or only one article at a time.

I think the reason Google is stripping out these things is because they aren’t in the RSS standard. Still, I do agree they should keep the header information in, it’s just clear that improvement is needed on both sides of the fence here.

On my article what I did (and still have in operation) is I used Feedburners own tool to add the no sharing with Yahoo Pipes and no index information, but the Bloglines code would be added in the same place.

I then shared my own feed contents and linked to it.

In that shared feed the information is stripped out.

You can still have information added to your posts with a plugin, but that is not machine readable as I don’t believe there is any proposed standard that works with individual feed items (though I could be wrong)

I understand some of the technology in this, but not like the real technology geeks.

I think the most dangerous aspect of this isn’t text, but licensed images which class as a complete work. You could get away with publishing to subscribers, but not free distribution and reuse elsewhere.

I know you are not into “marketing” stuff the same way I am, but there was a free report by Mike Filsaime that I encouraged people to download (yes it costs an email address and Mike does send occasional email promotions)

He has actually experienced a couple of costly legal problems with copyright which are enough to scare people which is why whilst so many bloggers don’t agree with me, I keep fighting this uphill battle.

On my article what I did (and still have in operation) is I used Feedburners own tool to add the no sharing with Yahoo Pipes and no index information, but the Bloglines code would be added in the same place.

I then shared my own feed contents and linked to it.

In that shared feed the information is stripped out.

You can still have information added to your posts with a plugin, but that is not machine readable as I don’t believe there is any proposed standard that works with individual feed items (though I could be wrong)

I understand some of the technology in this, but not like the real technology geeks.

I think the most dangerous aspect of this isn’t text, but licensed images which class as a complete work. You could get away with publishing to subscribers, but not free distribution and reuse elsewhere.

I know you are not into “marketing” stuff the same way I am, but there was a free report by Mike Filsaime that I encouraged people to download (yes it costs an email address and Mike does send occasional email promotions)

He has actually experienced a couple of costly legal problems with copyright which are enough to scare people which is why whilst so many bloggers don’t agree with me, I keep fighting this uphill battle.

I read your great article on the topic but that wasn’t completely clear to me.

Also, just a heads up, your site has a bug in Safari 3 that’s causing the sidebar to appear below the text. It could be a glitch with Safari, but I wanted to let you know.

I read your great article on the topic but that wasn’t completely clear to me.

Also, just a heads up, your site has a bug in Safari 3 that’s causing the sidebar to appear below the text. It could be a glitch with Safari, but I wanted to let you know.