I swear I thought I posted about this a long time ago, but couldn't find it. Anyway, I've been maintaining a simple RSS feed to show the recent posts on PM. Apparently, according to bloglines at least, some people have been using it.

Anyway, I just adjusted the feed so that it shows the full text of questions posted, and not just the subject.

Hope others might find this useful!

-- zigdon

Replies are listed 'Best First'.
Re: Perlmonks RSS feed
by McDarren (Abbot) on Jul 14, 2006 at 05:14 UTC
    Apart from showing the node contents, this seems to be pretty much identical to the newest nodes feed that jcwren provides from tinymicros?
      Ah, yes - I knew I wasn't being that smart! To be fair, I've had it up at least since 2004, the only thing I changed now was adding the node content. The whole point is that I find that I read posts much more consistantly if they come to me without me asking.

      -- zigdon

Re: Perlmonks RSS feed
by jdporter (Chancellor) on Jul 14, 2006 at 14:48 UTC
Re: Perlmonks RSS feed
by demerphq (Chancellor) on Jul 14, 2006 at 12:57 UTC

    Newest nodes has a built in RSS feed. I dont know how good it is, but it is there.


      If you mean the 'xml' link, it just shows the titles - it's actually what I was using to generate the RSS feed originally. Now I still use it, but get each node's xml separately.

      If there's a different link, I guess I don't see it?

      -- zigdon

Re: Perlmonks RSS feed
by Aristotle (Chancellor) on Jul 15, 2006 at 14:25 UTC

    What Iíd like to do at some point is to build a fulltext Atom feed that uses Feed Thread and Feed History extension elements. You could then read Perlmonks from right inside your aggregator just like on the site, threading and all. (Using Feed History would offset the cost of a fulltext feed by ensuring that aggregators donít need to poll aggressively to avoid missing feed entries.)

    (Since theyíre not even completely finished and blessed, there isnít much support yet for these extensions Ė but that would be helped if there were incentives for it in the form of existing consumable data. Which would in turn be a happy side-effect of having a clean static archive of Perlmonks, which IMO is worthwhile all by itself. I always worry a bit about the fact that the years of community knowledge and history that have accumulated at Perlmonks are stored in whatís effectively a closed silo. Be nice to have a copy of it outside the database in a future-proof standard format.)

    Makeshifts last the longest.