You talking about having a RFC: Subscription to nodes? tye's reply to theorbtwo's reponse to me is englihtening.
Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.
| [reply] |
You are correct, both interesting and enlightening! This looks to be a kind of solution that I could live with and given the problems of modifying the PM codebase quite reasonable. It also points to some ideas about external tracking that I hadn't given any thought too---possibly gold in them thar hills!
--hsm
"Never try to teach a pig to sing...it wastes your time and it annoys the pig."
| [reply] |
There is not an automated way. The person changing the node can /msg people, of course. And Janitors usually /msg authors when they touch one of the author's nodes. But there isn't any mechanism in place that /msg's participants in a thread if one of the nodes in the thread is modified.
| [reply] |
Do you suppose it would be worth an [update] tag which would generate a Update: and the necessary msg's?
--hsm
"Never try to teach a pig to sing...it wastes your time and it annoys the pig."
| [reply] |
A tag which does what, automagically /msgs everyone who has contributed to the node, read it? No thanks.. But there have been several discussions about a way to put nodes/threads on a 'watch list' where one would be notified if any of these changes.. Go search in past discussions maybe.
For this, I'd probably prefer another node list which sorts the entries according to the last change, which would mean we would have to save this information, we don't currently, that I know of.. But I hear tyes current new toy may incorporate this info.
C.
| [reply] |