Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I'm too lazy to learn SOAP, so I wrote a simple screen scraper that gets "http://use.perl.org/journal.pl?op=top" and looks at the by-date stuff, and notices whether there's anything new since the last time it ran.

    I should probably do it up in SOAP tho, since then it won't be fragile HTML-scraping.

    Aren't there already CPAN modules for talking to use.perl.org?

    • That gets the journal entries, but it doesn't find the replies. Especially on Monday, you can get replies to an entry that was made a few days ago, long after you read the original entry itself.
      • It'd be cool to have a way to "tag" an interesting journal entry (or articles in general) and receive messages whenever a comment is posted. Already, journal writers get a message for any comment posted, even replies to comments from other people. I think.

        So, the question is, does "tagging" scale? Obviously, on slashdot, it could shut the whole world down if you allowed it on any article in general; hmmm... given that most articles would be tagged toward the end of the initial furor, that might not be too bad. Very few comments are posted 24-48 hours after the article runs -- but if they are, some people would like to be notified.

        But for journals this seems like a neat idea. For here, at least.

        I'm sorry, pudge, I'll quit having ideas! :)

        --
        J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers