Node Watch

Ever have one of those classic nodes that reads like a good book and you keep checking back on it to see if anyone has added some witty remark? Or perhaps something you wrote in CUFP or the Code Catacombs that you want to keep track of?

How about a process that maintains a list of monks interested in particular nodes and sends a message to them when the node changes.

Your thoughts?

Retitled by Steve_p from 'New PM Feature Request'.

Replies are listed 'Best First'.
Re: New PM Feature Request - Node Watch
by Tanktalus (Canon) on Jun 15, 2005 at 22:38 UTC

    Sounds similar to this request - maybe the solution there will help?

    Update: As per tye's comment in the CB - I'm assuming you are meaning that you want to watch threads and not Nodes. Although I suppose people can update their nodes, too, as I'm doing right here...

    Update 2: The problem with the solution there is that you need to monitor what you've linked, it's not automatic. But it's probably as close as you can get without someone actually writing the changes... it's something to tide you over.

      While adding links to interesting nodes im my home node is a good idea, it's not exactly what I had in mind.

      Once you have identified an interesting node (and the thread it anchors) it would be nice to be able to be notified when someone adds to or modifies the thread. Just having a link to it is not enough. I want to know when there has been activity.

      For example several people have responded to this node. Only those whose responses I reply to explicitly will receive a notification in their inbox. I would like all those interested to receive such a notification.
Re: New PM Feature Request - Node Watch
by idsfa (Vicar) on Jun 15, 2005 at 23:23 UTC

    I smell a request that is just crying out for an RSS feed.

    Feed here

    The intelligent reader will judge for himself. Without examining the facts fully and fairly, there is no way of knowing whether vox populi is really vox dei, or merely vox asinorum. -- Cyrus H. Gordon
Re: New PM Feature Request - Node Watch
by davido (Cardinal) on Jun 16, 2005 at 06:08 UTC

    I'm not really familiar with the code behind Recently Active Threads, but it seems that what you're after could be a cross between Personal Nodelet (where you can add nodes to the nodelet) and Recently Active Threads.

    I don't know how hard it would be to implement this. demerphq is the king of Recently Active Threads. But it seems like it ought to be, at least, possible. As they say, "patches welcome."


Re: New PM Feature Request - Node Watch
by demerphq (Chancellor) on Jun 18, 2005 at 16:10 UTC

    Ok. For the record I would love to do this. The trouble is that I have yet to come up with or hear a plausable design. Scale is a real issue with something like this. We have several thousand active participants here and we have about a half million posts. That combines to make for potentially serious work supporting this feature.

    I can think of half-assed implementations that wouldnt be too much trouble, and probably would scratch most of the itch. It wouldnt be too difficult to allow users to store root nodes of threads and then use the RAT to display them on user request, but the minutae of handling things more specifically than that escapes me.

    If someone can offer a reasonably sane design that seems like it would work id give it a go, but currently I dont think there is much that I can do. BTW, before anybody replies with a design please familiarize yourself with the design of the everything engine.


      demerphq thanks for looking at this for me. I think the RAT would be very useful.

      I'm fairly new to PM but I have a background in databases so naturally a db solution springs to mind (my mind at least). Do you have any links to documentation on the "everything engine" I'm not familiar with it.

        Regarding links to everything engine, take a look at the bottom of any page on the site. Regarding a DB solution, yes sure it would have to be in DB. But the question is how. More explicitly but briefly the problem is how do you efficiently handle thread watching when you are using a parent pointer representation for the reply tree.


Re: New PM Feature Request - Node Watch
by blue_cowdawg (Monsignor) on Jun 18, 2005 at 02:42 UTC

    Hmmm... or maybe an RSS "ticker tape" for nodes...

      blue_cowdawg said:
      Hmmm... or maybe an RSS "ticker tape" for nodes...

      That would be cool, but I was thinking more of a notification service that would ping you when a thread you were interested in changed. Not like a ticker tape that you would have to be paying attention too.