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

use Perl Log In

Log In

[ Create a new account ]

blazar (7356)

blazar
  (email not shown publicly)
http://blazar.perlmonk.org/
Yahoo! ID: bik.mido (Add User, Send Message)
Jabber: blazar@jabber.org

Journal of blazar (7356)

Tuesday April 10, 2007
10:39 AM

Dear Lazyweb

[ #32956 ]

No, that's not a mischosen Subject, and this is not an actual "lazyweb" request. Just reporting a lazyweb-friendly project I just discovered, that was IMHO a nifty idea. Unfortunately, it "was", because as detailed in http://www.lazyweb.org/archives/010257.html, "The LazyWeb is closed." Anyway, the code is out there, ready to be used. But what is IMO interesting, again, is not the actual implementation as much as the idea.

Why do I think that the idea is so cool? Well, because every now and again I do have questions and ideas of my own, for something too many orders of magnitude above the level of my current technical skills for me to even think about developing them to put the thing to work. But if by any chance I feel inspired and write about it in an OT entry in a community that is at least vaguely related, it either gets unanswered at all, leaving me with Warnock or gets an explicit reply along the lines of: go get the skills and do it. Also, there may well be a community where discussing the issue may be appropriate, but one may simply not know about it. Thus a service like that offered by that site, would be useful in these circumstances.

So, why did the project fail? Well, I don't have the slightest idea. But judging from the last entries, perhaps it was too broad in scope. Moreover, I suppose that it would have greatly benefited from not being a new thing altogether, but a side project of some major information site.

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.
  • Hello! Thanks for the very interesting post. Thanks for sharing!

    My take on this is Lazyweb becomes a message board to which messages are posted automatically whenever a modern blog links to it (via the ping magic). That seems like a great idea... a lazy way for blogs to post messages on a particular topic to a central message board on that topic.

    Then, would the blog author need to check the Lazyweb comments from time to time?

    I guess the ideal way for a person to post an answer would be for the person t

    • Please note that I have virtually no experience with blogs and the like, so I'm not terribly familiar with their specific jargon, let alone the technology. Said this...

      Then, would the blog author need to check the Lazyweb comments from time to time?

      I'm not really sure. Since the Lazyweb provides feeds anyway, I suppose he would use them to keep track of possible comments. But the Lazyweb also provides a quick means, in the form of a single link for anyone who reads a particular entry, to the original p

      --
      -- # This prints: Just another Perl hacker, seek DATA,15,0 and print q... ; __END__
  • 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 in