In the CB this (European) morning, we were discussing the possibility of having a flag for root nodes which would cause them to reappear on Newest Nodes, sorted by time of last update, instead of createtime..

The reason this came up was because ysth maintains a node about recent perl annnouncements, instead of creating a new node for every one, its nice to have them all in one place, but updates to the node go largely unnoticed.

Anyfish, I pondered whether making changes to root nodes in Perl News could cause them to automagically reappear in NN, since Perl News is low volume anyway. Then we discussed whether we couldn't add a 'this is a significant update' button to the node edit page for root nodes, and reprogramm NN so that such nodes would reappear. (Doing this generally for every update rather than have a checkbox was considered a bad idea, as some people fiddle a lot, or change spellings, also editors updates should probably not trigger this mechanism)

My feeling is that this may help improve the 'posting update as new node else it wont get seen' problem, and shouldn't get abused too much (well, no more than the allowing of editing of root nodes has been, and we seem to have that more or less under control :)

Below is a recap of the conversation, to save said persons (ie me) repeating their opinons in this node.. (excuse the representation of CB, thats just how it looks via my gateway.. ,) 

[Perlmonks castaway@PerlMonks] Is it a Perl News node? Maybe we could 
+special case those to reappear in NN on update?
[Perlmonks castaway@PerlMonks] .. that sounds like a useful solution t
+o me, anyway
[Perlmonks castaway@PerlMonks] anyone think of a reason why News nodes
+ shouldnt do that?
[Perlmonks bart@PerlMonks] It should also reappear on [perl news], as 
+if it was a new node. That's harder, as node ids would need to be sor
+ted out of order.
[Perlmonks ysth@PerlMonks] [castaway] inefficiency?
[Perlmonks bart@PerlMonks] Though I could think of a section of "updat
+ed nodes" at the bottom of [perl news], once it drops off (they proba
+bly all will), would sound even better.
[Perlmonks ysth@PerlMonks] but news is low-enough volume it probably w
+on't matter
[Perlmonks castaway@PerlMonks] ineffcient how? (cheapest solution, cha
+nge the createtime, or something :)
[Perlmonks castaway@PerlMonks] thats my thought.. News is fairly low v
+ol
[Perlmonks ysth@PerlMonks] the newest nodes ticker shouldn't do it by 
+default but have the option to
[Perlmonks bart@PerlMonks] Perhaps a special property assigned to by e
+ditors, enabling this feature
[Perlmonks ysth@PerlMonks] oh; changing the createtime is clever 
[Perlmonks bart@PerlMonks] It's also cheating.
[Perlmonks castaway@PerlMonks] well, assuming the list goes by createt
+ime (Ive looked recently, but I cant remember)
[Perlmonks castaway@PerlMonks] I dont think special-casing them would 
+be all that terrible
[Perlmonks bart@PerlMonks] It probably does. Either create time, or no
+de id. (those should be in sync by default)
[Perlmonks castaway@PerlMonks] ha, I was right: order by createtime de
+sc :)
[Perlmonks castaway@PerlMonks] Could be changed to 'lastupdatetime' as
+suming we have such.. actually that would probably solve a big reason
+ people post new nodes..
[Perlmonks bart@PerlMonks] But somehow I think that the shown create t
+ime should be the real one. You shouldn't fool the user into thinking
+ this actually is a new node.
[Perlmonks bart@PerlMonks] I think a "this is a significant update" ch
+eckbox would be welcome. People while editing can decide between just
+ fixing a typo, or actually changing the content.
[Perlmonks bart@PerlMonks] If the list of updated nodes becomes as big
+ as the actual new nodes, i think it'd be missing its point...
[Perlmonks castaway@PerlMonks too]
[Perlmonks bart@PerlMonks] I also fear some people could abuse this fe
+ature to try keep a node of theirs in the attention...
[Perlmonks castaway@PerlMonks] people could abuse this site for lots o
+f things, it hasnt happened though (much).. and any such will get som
+e sort of punishment if it did happen
[Perlmonks castaway@PerlMonks] (we need to stay perl like, no shotguns
+ .)
[Perlmonks bart@PerlMonks] Like votes on a node be disabled for adding
+ to their XP while its on that list of recently updated nodes.
[Perlmonks bart@PerlMonks] I mean, no chance of gaining XP.
[Perlmonks Intrepid@PerlMonks] On this point I definitely support [cas
+taway]'s assertion.
[Perlmonks castaway@PerlMonks] Id prefer no premptive strikes there un
+til it because evident we need them
[Perlmonks bart@PerlMonks] What? The "not shotguns" approach? Well, I 
+agree... provided we keep a shotgun handy. Just in case.  :)
[Perlmonks bart@PerlMonks] ... Or at least, we know where to get one.
..

[download]
Opinons? Suggestions?

Update: Quick idea revision, how about there being a time limit for using it in certain sections? ie unlimited in News, Discussions, limited to 1 or 2 days (?) in the other sections.

C.

In reply to "Significant update" flag for root nodes? by castaway

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.