Would'n it be niece if in the personal nodelet you would have a sign idicating if there was a new comment (or a change to an old comment) in the thread of given node? It could be a simple '+' sing or something - nothing very intrusive.

This way we could use the threads in a manner simmilar to mailing lists. People could subscribe to threads and be noticed when there is something new in them. As a side effect there would be more reusal of the information contained in PM, for now there is little sens in posting to an old thread - nobody would notice.

There was something simmilar proposed in 'My Active Nodes' - idea, but mine is a little bit more general. Now the Personal Nodelet is just another bookmark mechanism - actually a bit redundant since there is already one in the browser, this would change it to something new.

Replies are listed 'Best First'.
Re: A feature for Personal Nodelet
by davis (Vicar) on Mar 14, 2003 at 09:54 UTC

    That would mean storing the "most recently viewed state" (couldn't think of a good name) of all the threads in the personal nodelet, and comparing each of those threads' state to the current state in order to tell if anything had changed. It would also require tracking which users had looked at which nodes (though I suppose this could be similar to the method used to tell who's voted on a particular node).

    In short, it sounds like it would be a nightmare to code

    Is this going out live?
    No, Homer, very few cartoons are broadcast live - it's a terrible strain on the animator's wrist
      Yeah - I know that, I'm a programmer too :-)

        It'd be a minor nightmare to code. It would be a major nightmare either on server load to do all of the checking required each time the nodelet is displayed or a major nightmare in resources to be able to update all of the personal nodelets whenever a new node is posted.

        In other words, it will never happen.

        If one wants to track a list of threads for new replies, then the only scalable solution is for each user to keep their own list of threads-to-be-tracked and record the last time they checked. Then each user can infrequently fetch the list of new replies (since the last time they checked) and compare these replies' root node IDs against their list of threads (and update when they 'last checked').

        If one wants to track other than just by root nodes, then the amount of complexity to do that efficiently goes up a great deal.

        There might eventually be something similar to this done inside of the Monastery using a cron job. But it certainly won't end up in a nodelet (barring tons of work in caching).

        And if one wants such a feature, the fastest way to get it is to implement it outside of the Monastery using existing Monastery features.

                        - tye
Re: A feature for Personal Nodelet
by mojotoad (Monsignor) on Mar 14, 2003 at 18:23 UTC
    Nodes are already aware of which thread they belong to, correct? (something is aware of it, anyway, because each sub-node has "in thread" links when viewed). So maintain a descendant counter in each root node that is incremented each time a new node in the thread is created (or decremented when a descendant node is reaped).

    With such a count, thread activity is a simple comparison of the last-seen count and the current count for that thread.

    Is this really that much more overhead?


Re: A feature for Personal Nodelet
by zby (Vicar) on Mar 14, 2003 at 11:07 UTC
    It could be a partial answer to those new sections requests - everyone could have a kind of his own sections.