I am quite interested in people's update to their posts, but is there a way that I can know which nodes have been updated?

I checked in my user setting, and seems to me there is no setting for the order of nodes on newest node page.

Maybe sort by last modified time? so that those updated nodes would come to people's attention?

Any other suggestions? or maybe nobody cares this any way. I realize that if we sort by last modified time, a slight editing would bring a node to the front. Maybe have a checkbox, and allow the author to determine whether it is a significant update that should bring the node to the front?

Replies are listed 'Best First'.
Re: Newest node page - order of nodes
by theorbtwo (Prior) on Feb 10, 2003 at 02:46 UTC

    I think, in general, the correct answer is "If you want your updates to be noticed, don't update, reply". IMnsHO, updates should be used to fix typos and note major errors... nothing inbetween.

    Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).

[reply]
Re: Newest node page - order of nodes
by diotalevi (Canon) on Feb 09, 2003 at 23:59 UTC

    A modification - have updated nodes appear in the 'Newest Nodes' page. How else would most people know of modifications to a long-gone node?

    Seeking Green geeks in Minnesota

[reply]
      I recently discussed this with Chmrr. My idea was to have an update system for root nodes. It would require two new fields for root nodes (Last Modified, Note ID) and an additional table. One would be presented with a textarea to make an ammendment to the node, this entry would be timestamped and stored in the Note ID table. Last Modified and Note ID in the root node table would be updated. Subquent updates would be prepended to the existing note. When the root node is displayed the note would be prepended to the node body when displayed. Finally, Newest Nodes could pick up on touched Last Modified fields.

      --
      I'm not belgian but I play one on TV.

[reply]
        Why?

        A node already has a "createtime" and "lastupdate" and even a "lastedit" field. I cannot see what adding yet another field and creating an additional table would do.

        You know how we have messageonreply, what no a messageonupdate? Everytime a node is updated, it would send a message to a special group, something like SystemNodeUpdated and then people could go to the messageinbox, with 'recipient' being that of SystemNodeUpdated, and view the messages, which would look something like:
        <SystemNodeUpdated> says "PodMaster updated Re: Re**2: Newest node page - order of nodes on Mon Feb 10 02:22:22 2003 GMT"

        update: I guess adding a table to keep track of this could potentially lead to some kind of database indexing optimization ... i'm not convinced we need it.

        MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
        ** The Third rule of perl club is a statement of fact: pod is sexy.

[reply]

Back to Perl Monks Discussion