Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid

ALive Nodes

by artist (Parson)
on Mar 20, 2003 at 21:53 UTC ( #244735=monkdiscuss: print w/replies, xml ) Need Help??

Dear Monks,

Do you want to make your comments to an old node more visible? Here is an idea.
Concept: Live Nodes:
Use: Visibility to Still Interesting Discussions and Contributions
Description: It would be helpful to see what's added in the monastery. If a monk decides to add a comment to a node which is somewhat old, current visibility is:

  • Author of the parent node is notified
  • Shows up as a 'Note' in the newest node
  • Search for something and happen to visit that node
  • Had Bookmarked the parent node and happen to visit it.

    Idea is to provide the visibility for such items even after you clear your newest nodes. Also if you are adding something, you can get feedback on that too as you node now will be more visible.

    • A. Any Node has timestamp
    • B. A Node may have reply
    • C. Every reply Node has a parent node
    • D. Node could be parent node or reply node.

    Parent Node(N) and Replys(R)
    Node Table in the monstery Table A
       N1 => 1	 R11 => 2  R12 => 6  R13 => 14
       N2 => 3       R21 => 10 R22 => 7 
       N3 => 8       R31 => 9  R32 => 15
       N4 => 11      R41 => 12 R42 => 19
       N5 => 16      R51 => 18
       N6 => 20

    Assuming Current Timestamp: 20
    Sorting by Largest Timestamp Differences for all parent nodes
    Table B

       R12 - N1 => 13
       R42 - N4 => 8
       R32 - N3 => 7
       R22 - N2 => 7
       R51 - N5 => 2
       Current-N6 = 0
    Filtering Above within last x= '5' units of time
    Current - x = 20- 5 = 15.
    So Taking only data where timestamp > 15 from 'Table A'

    Table C

      N3 => 8	R32 => 15
      N4 => 11      R42 => 19
      N5 => 16      R51 => 18
      N6 => 20
    Sorting by Largest Timestamp Difference for all parent nodes where timestamp of parent or the reply node is > 15
    Table D
    TS     Reply Parent Difference
    19     R42 - N4 => 8
    15     R32 - N3 => 7
    18     R51 - N5 => 2	     
    20     Current-N6 = 0  
    To be Displayed (Sorted by Timestamp differences)

    Table E
    TS_Difference   Reply  TS
    8		R42    19(11)
    7		R32    15(8)
    2		R51    18(16)
    0		(N6)   (20)
    Sample Observation:R32 which had parent node at timestamp 8 (12 timestamps ago) is still seems live.

    Notes:By sorting in such fashion, we give visibility to the nodes which still seems interesting to the community members. We can employ other sort/search mechanism here if more useful.

    Request:Your input about the idea and implementation.


  • Replies are listed 'Best First'.
    Re: ALive Nodes
    by valdez (Monsignor) on Mar 20, 2003 at 23:00 UTC

      I agree with you, but our pmdevs are busy and probably can't do that here and now; tye and YAS are working to reach an agreement on future development of our beloved site. I think we will have the opportunity to say something on what should be done.

      Be patient and, in the meantime, try to build some Perl wheel to obtain the same results. It can be very challenging: use Cache::Cache to save some load on the Monastery, parse files with XML::Simple or HTML::TokeParser::Simple and you are almost done :)

      I'm writing something using these modules, but you can find many useful tools here: PerlMonks Related Scripts, What XML generators are currently available on PerlMonks?.

      Ciao, Valerio

    Re: ALive Nodes
    by zby (Vicar) on Mar 21, 2003 at 09:24 UTC
    Re: ALive Nodes
    by shotgunefx (Parson) on Mar 21, 2003 at 10:27 UTC
      Perhaps a lightweight compromise would be to list the last N active (top level node) threads under newest nodes. Active being any thread that has had a new node attached to it. The nodes listed would exclude newer nodes (Nodes that still showed up under Newest Nodes).


      "To be civilized is to deny one's nature."
    Re: ALive Nodes
    by ignatz (Vicar) on Mar 21, 2003 at 00:19 UTC
      In terms of increasing the value of The Monastery I can think of no more worthy goal than trying to increase the accesability and continued dialog of old nodes. However, this seems extremely complex. (Maybe my brain is just tired Should I try to re read it after a good nights sleep? Is that even possible these days?)
      ()-()             When you know what you're doing,
       \"/              you don't know what you're doing.
        `               -- Robert Fripp, A Motto for Crimson
    Re: ALive Nodes
    by Anonymous Monk on Mar 21, 2003 at 13:56 UTC

      Excellent idea, I think this is one thing that is missing from many community-based discussion engines. The other being visibility/rep is directly related to how early a node is posted. Us Anonymonks are all for it ;)

    Re: ALive Nodes
    by Courage (Parson) on Mar 22, 2003 at 09:39 UTC
      It's a known problem that has no acceptable solution.

      Even after some answers a node could be still unanswered, and I'm inclined to think that sometimes people that did not answer a question but add some pointless comment to a node do more harm than good, and, regrettably, it is not very rare case, especially for "hard-to-answer" questions.

      Easy questions quickly receive a lot of good answers though.

      Courage, the Cowardly Dog

        Few Ideas:
        • Author can ask editors to set a flag for the node which is not answered properly.
        • Flag is set automatically when the question is asked, and not answred in 24 hours. As soon as the first answer is recieved, the flag is cleared. Author will have right to set the flag again for the first 24 hours. Then request to editors must be made. Flags get automatically cleared after the new answer.
        • Any user can request editors for any node that he/she thinks that is not answred properly.
        • Voting system for higher level monks for determining if the question is answred properly.

        Single or the combination of ideas could be applied to get more satisfaction out of monastery.


          I really, really appreciate your efforts to solve this problem and to improve this site!

          I wish you wholeheartedly really really good luck on this and let your cattle be safe and sound!
          Courage, the Cowardly Dog

    Log In?

    What's my password?
    Create A New User
    Domain Nodelet?
    Node Status?
    node history
    Node Type: monkdiscuss [id://244735]
    Approved by ChemBoy
    Front-paged by mojotoad
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others romping around the Monastery: (3)
    As of 2021-12-01 04:16 GMT
    Find Nodes?
      Voting Booth?

      No recent polls found