Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic
 
PerlMonks  

Optional notification of significant edits

by Wassercrats
on Aug 24, 2004 at 17:13 UTC ( #385459=monkdiscuss: print w/ replies, xml ) Need Help??

If people get downvoted for posting a new reply to make sure the questioner gets alerted, then there should be an option to alert someone of a significant node update so he won't miss it.

Currently, the best way to handle a small but significant update is to both append the original post and create a new one, which is what I did. Appending the original will help people who've bookmarked it, and the new post will alert people who are just reading new replies.

Comment on Optional notification of significant edits
Re: Optional notification of significant edits
by ambrus (Abbot) on Aug 24, 2004 at 17:31 UTC

    I sometimes use /msgs to notify someone of an update.

Re: Optional notification of significant edits
by talexb (Canon) on Aug 24, 2004 at 18:31 UTC

    Please make a habit of using the [id://385430|your node] format rather than an HTML tag -- I log on to perlmonks.org, and your tag references perlmonks.net, which causes me to get logged out.

    It's probably more efficient to /msg someone with the news of the update .. if you really want to. Otherwise, either they read it, or they don't read it.

    If I think one of my replies was particularly useful I might go back (Hubris) and see what new replies or updates there are. I don't think I've ever bookmarked a node (Laziness) so I can go back and have another look at it. I'll get notified if someone replies to one of my nodes. That's enough -- I have enough other things to do (Impatience).

    Alex / talexb / Toronto

    "Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

Re: Optional notification of significant edits
by bronto (Priest) on Aug 25, 2004 at 11:16 UTC

    I think that having a node back in the Newest Nodes each time an update takes place, or at least with a mechanism like the one used for the home node, could be useful, so that significant updates won't be missed

    Just my two cents...

    Ciao!
    --bronto


    The very nature of Perl to be like natural language--inconsistant and full of dwim and special cases--makes it impossible to know it all without simply memorizing the documentation (which is not complete or totally correct anyway).
    --John M. Dlugosz
Re: Optional notification of significant edits
by Wassercrats on Aug 25, 2004 at 13:31 UTC
    I don't really like the idea of applying weird, additional features to compensate for misuse, but another idea is to let the poster choose to disable upvotes for certain nodes to make it clear that he's not going for votes. Maybe the upvote option could change into an abstain option in that case, so people who vote as often as they can (which gains them XP, and is another thing that should be eliminated) wouldn't be forced to downvote a post when there's nothing wrong with it.

    That would eliminate the need for people to say "please don't upvote this node," which I've seen several times.

Re: Optional notification of significant edits
by Anonymous Monk on Aug 25, 2004 at 16:39 UTC
    If people get downvoted for posting a new reply to make sure the questioner gets alerted

    Once again, you miss the point. You didn't get downvoted just because you posted a new reply, you got downvoted because your reply didn't add anything to the discussion. Simply posting a link to another site, without even a description of why, is both asinine and pointless.

    then there should be an option to alert someone of a significant node update so he won't miss it

    A "significant update" should almost always result in a new post. Adding a single off-site link is not significant.

    Currently, the best way to handle a small but significant update is to both append the original post and create a new one, which is what I did. Appending the original will help people who've bookmarked it, and the new post will alert people who are just reading new replies.

    I agree 100%, but again I reiterate that your example update was not significant. New posts containing actual significant information don't get downvoted, so your concerns are baseless.

      you got downvoted because your reply didn't add anything to the discussion. Simply posting a link to another site, without even a description of why, is both asinine and pointless.

      My link was to a thread in which the top post had me asking what the person I was responding to (peppiv) wanted to know. Slightly below was the answer--a link to various versions of the actual script. It needed no explanation, so I just said "See this."

      If people actually have the nerve to downvote a helpful post like that, they should reply and say something like "I downvoted your reply because you didn't explain the link" or "I downvoted your reply because the useful information wasn't directly within the post." I suspect people would then downvote their post.

      I don't like the sub-thread structure of Perlmonks, but one benefit to it is that you know what's being responded to, and quotes and explanations aren't needed as often, and I take advantage of that sometimes.

        I don't like the sub-thread structure of Perlmonks

        What do you like about Perl Monks, other than annoying everybody?

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: monkdiscuss [id://385459]
Approved by MidLifeXis
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (8)
As of 2014-12-22 18:10 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (126 votes), past polls