Best argument against partial feeds yet

Steve Gillmor gives me a great argument against partial feeds. Heheh.

It’s funny, but I got a bunch of email whines from publishers about full text feeds. Here’s the deal. I’m not gonna be an arrogant a**h**e anymore on this issue. Go ahead and publish partial text if you’d like. But to read the rest of my thoughts on this issue you’ll …

Heheh.

29 thoughts on “Best argument against partial feeds yet

  1. Tankko: it’s full text if you use the right aggregator. It’s full text in NewsGator, for instance. My feed includes both full and partial text.

    Which aggregator are you using?

    Like

  2. Tankko: it’s full text if you use the right aggregator. It’s full text in NewsGator, for instance. My feed includes both full and partial text.

    Which aggregator are you using?

    Like

  3. Tankko: because your aggregator is pulling my partial text feed for some reason. I don’t use Thunderbird, so don’t know what’s up.

    Like

  4. Tankko: because your aggregator is pulling my partial text feed for some reason. I don’t use Thunderbird, so don’t know what’s up.

    Like

  5. As some one before me said, look at the source of the feed…

    The partial content is in the “Description” section. The full content is in the “Content:Encoded” section.

    If you aren’t seeing the full feed, your Reader is only looking at the “Description” Feild and ignoring the other. If this is the case, you are getting a lot of partial feeds when you could be getting full.

    Like

  6. As some one before me said, look at the source of the feed…

    The partial content is in the “Description” section. The full content is in the “Content:Encoded” section.

    If you aren’t seeing the full feed, your Reader is only looking at the “Description” Feild and ignoring the other. If this is the case, you are getting a lot of partial feeds when you could be getting full.

    Like

  7. Robert, your example is flawed, because you don’t get to the point in the first section.

    If you’ll use the inverted-pyramid style of journalism, with the summary in the first sentence and expansion in the first paragraph, then people will *want* to know if they want to read more.

    I’m coming more to the feeling that short feeds are better for the reader, ’cause the force the writer to get to the point — to write for the reader’s sake, not just the writer’s sake.

    Like

  8. Robert, your example is flawed, because you don’t get to the point in the first section.

    If you’ll use the inverted-pyramid style of journalism, with the summary in the first sentence and expansion in the first paragraph, then people will *want* to know if they want to read more.

    I’m coming more to the feeling that short feeds are better for the reader, ’cause the force the writer to get to the point — to write for the reader’s sake, not just the writer’s sake.

    Like

  9. For a Marketing guy, you sure divide people into opposite camps, if you feel strongly enough about said issue, work in some sort of win-win; not playing ‘us vs. them’ polarizing games.

    I know half of Microsoft hates me, but they sure could use me. Tap me when they pull in a that marketing overhaul and get new blood.

    Like

  10. For a Marketing guy, you sure divide people into opposite camps, if you feel strongly enough about said issue, work in some sort of win-win; not playing ‘us vs. them’ polarizing games.

    I know half of Microsoft hates me, but they sure could use me. Tap me when they pull in a that marketing overhaul and get new blood.

    Like

  11. pull in a 180, that….

    What be with disappearing words and sentences on comments? I get that ever so often, drives me nuts. Well, not as much here as TypePad. Egads. Cached comments sent up, outtages, glitches, postings hours after submit, comments randomly ate up. Ben and Mena sure hatched a monster in TypePad.

    Like

  12. pull in a 180, that….

    What be with disappearing words and sentences on comments? I get that ever so often, drives me nuts. Well, not as much here as TypePad. Egads. Cached comments sent up, outtages, glitches, postings hours after submit, comments randomly ate up. Ben and Mena sure hatched a monster in TypePad.

    Like

  13. Robert, what is “”, and why does the full text of your post appear in that element and not in “”? There is no mention of “content:encoded” in the RSS 2.0 spec at http://blogs.law.harvard.edu/tech/rss

    Obviously some aggregators (such as Bloglines) know what it is, but some don’t. The thing is, I don’t think you can blame the aggregator if the feed is not RSS 2.0 compliant (even though it says rss version=”2.0″ at the top).

    I want to read your full feed – but the mobile aggregator I’m using right now sticks rigidly to the RSS 2.0 spec – and I can’t really blame them for that.

    Like

  14. Robert, what is “”, and why does the full text of your post appear in that element and not in “”? There is no mention of “content:encoded” in the RSS 2.0 spec at http://blogs.law.harvard.edu/tech/rss

    Obviously some aggregators (such as Bloglines) know what it is, but some don’t. The thing is, I don’t think you can blame the aggregator if the feed is not RSS 2.0 compliant (even though it says rss version=”2.0″ at the top).

    I want to read your full feed – but the mobile aggregator I’m using right now sticks rigidly to the RSS 2.0 spec – and I can’t really blame them for that.

    Like

  15. [Sorry – I used angle brackets in the comment above and they got parsed out of it. Corrected version below:]

    Robert, what is “content:encoded”, and why does the full text of your post appear in that element and not in “description”? There is no mention of “content:encoded” in the RSS 2.0 spec at http://blogs.law.harvard.edu/tech/rss

    Obviously some aggregators (such as Bloglines) know what it is, but some don’t. The thing is, I don’t think you can blame the aggregator if the feed is not RSS 2.0 compliant (even though it says rss version=”2.0″ at the top).

    I want to read your full feed – but the mobile aggregator I’m using right now sticks rigidly to the RSS 2.0 spec – and I can’t really blame them for that.

    Like

  16. [Sorry – I used angle brackets in the comment above and they got parsed out of it. Corrected version below:]

    Robert, what is “content:encoded”, and why does the full text of your post appear in that element and not in “description”? There is no mention of “content:encoded” in the RSS 2.0 spec at http://blogs.law.harvard.edu/tech/rss

    Obviously some aggregators (such as Bloglines) know what it is, but some don’t. The thing is, I don’t think you can blame the aggregator if the feed is not RSS 2.0 compliant (even though it says rss version=”2.0″ at the top).

    I want to read your full feed – but the mobile aggregator I’m using right now sticks rigidly to the RSS 2.0 spec – and I can’t really blame them for that.

    Like

Comments are closed.