Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

Re: RFC: Subscription to nodes

by DrHyde (Prior)
on Sep 22, 2003 at 19:31 UTC ( #293242=note: print w/replies, xml ) Need Help??

in reply to RFC: Subscription to nodes

I haven't looked at the code, but this would probably be quite complex.

Simpler, I'm sure, would be to send me email when someone replies to one of my nodes. It would, I expect, scratch most of the itch here.

Replies are listed 'Best First'.
Re: Re: RFC: Subscription to nodes
by Louis_Wu (Chaplain) on Sep 22, 2003 at 19:50 UTC
    There is an option in User Settings, in the Miscellaneous section, to /msg me when there's a reply to one of my posts, which works well in notifying me of direct responses, but it doesn't tell me if someone responded to my responder with a correction.

    Knowing whether the whole thread has any updates is different from knowing if you've been responded to personally. We have an existing option for the later, but the former sounds quite handy. I can spend even more time at the Monastery. :)

    "No, no, you're not thinking, you're just being logical." - Niels Bohr
      Furthermore, I want to be notified if a given thread has updates. There are several wonderful topics that I may or may not have posted in, but I would love to follow. PM should make the hard things easy. :-)

      We are the carpenters and bricklayers of the Information Age.

      The idea is a little like C++ templates, except not quite so brain-meltingly complicated. -- TheDamian, Exegesis 6

      Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

Re: Re: RFC: Subscription to nodes
by Anonymous Monk on Sep 22, 2003 at 20:33 UTC
    I haven't looked at the code, but this would probably be quite complex.

    How do you figure that? Just add in an extra function call whenever a node is posted that checks who's monitoring the node's parents and send a message to those users. Seems straightforward to me :)

      Oh yes, look at the parent, get a list of interested people, then look at *its* parent, get a list of interested people, then *its* parent, and so on. Then de-dupe the list, then mail it out efficiently. That alone could get quite expensive.

      You also need a database schema change to somehow record a list of people who want to be mailed about posts. Plus the interface for users to add and remove themselves from those lists.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://293242]
[marto]: very nice
[choroba]: Especially the "Real Time" link
[choroba]: I can confirm it shows a lightning at the moment it strikes

How do I use this? | Other CB clients
Other Users?
Others having an uproarious good time at the Monastery: (9)
As of 2018-05-23 21:43 GMT
Find Nodes?
    Voting Booth?