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.
  • An article on openP2P.com [openp2p.com] (O'Reilly) discusses the Lazyweb concept as applied to feature requests for a software project.

    By converting the Lazyweb home page to an RSS feed, Lazyweb creates a poor man's Bloglines... people who are interested in the topic covered by a particular Lazyweb can subscribe to the feed and monitor questions (or feature requests or whatever) posted there. So I guess one would ask blog authors to cooperate in providing content to the aggregate feed by linking to the Lazyweb in any bl

    • Thank you for the link. As explained in the reply to your other post, I'm far from being an expert myself. (About anything, BTW!) So I'm reading it. I think that the keyphrases are:

      More people can describe features than write software, just as more people can characterize bugs than fix them. Unlike debugging, however, a LazyWeb description does not necessarily have a target application or a target group of developers.

      But when we read the following...

      Will it work? Who knows. Like any experiment, it could

      --
      -- # This prints: Just another Perl hacker, seek DATA,15,0 and print q... ; __END__
      • Heck, maybe it's basically a precursor to Technorati ... where, I think, it's possible to see all recent entries for blogs that use a particular tag and that use software that has pinged Technorati.

        The way the Lazyweb author describes it, a blog author manually includes a simple hypertext link to the Lazyweb site in order for the new item to be aggregated to the Lazyweb. I wonder if it would be possible to rewrite the Lazyweb software to generate "new Lazywebs" automatically for each incoming link that includes a "?tag=" parameter in the URL. Then a person writing an item in his blog about mod_perl could specify mod_perl as the item's tag; the word "mod_perl" would appear in the list of tags for that item on the resulting HTML page for the item and would automatically be a link: "Tags for this item: <a href="http://perllazyweb.com?tag=mod_perl">mod_perl</a>"

        If the Lazyweb spawned a new page/RSS feed for links to it about "mod_perl," it would be possible for people to subscribe to the "mod_perl" RSS feed.

        (Perhaps I've just reinvented Technorati; maybe that's exactly how Technorati is pinged.)

        In effect, each such tag would result in a different, community-written "Planet Perl" (http://planet.perl.org/) for each of the topics (tags) entered by people on their blog entries.

        I'm not sure how this Changes the World as compared to message boards and Usenet, but the ability to have blog entries automatically appear on a single web page and RSS feed is cool, and if Lazyweb could be turbocharged as described above perhaps it would enable, in effect, the creation of new message boards and Usenet newsgroups on the fly, complete with an RSS feed for interested persons.

        I wonder if software is available that enables the creation of a mini-Technorati.

        use.perl journal entries don't include tags or automatic pings, but I guess they could...