Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

Re: The ability to delete

by ysth (Canon)
on Oct 23, 2005 at 09:10 UTC ( #502303=note: print w/ replies, xml ) Need Help??


in reply to The ability to delete

One situation where a delete feature could be helpful is when you inadventently make a duplicate post. This can happen when you click on Submit but nothing seems to happen for a long time and then you click on it again, or do a refresh or some such. Something like that happened to me yesterday and I wasn't able to delete the duplicate post.
This seems like a non-problem. In the case of your node, it was reaped 31 minutes after it was created. Perhaps if you had yourself considered it for deletion it would have been even faster. Yes, the current process involves several people and a short time delay; IMO those are good things.


Comment on Re: The ability to delete
Re^2: The ability to delete
by phydeauxarff (Priest) on Oct 25, 2005 at 23:28 UTC
    In the case of your node, it was reaped 31 minutes after it was created.

    I wonder if there is a compromise that can be developed.

    I agree that deleting nodes = bad thing...but

    How about the ability to do something similar to Reaping or in this case, Self Reaping?

    Perhaps a user, within certain guidelines, could "reap" their own node and the result would display something like "phydeauxarff has reconsidered this node for presentation - for more info click here" and provide a link to the original node should anyone care to dig in and see what it was

    this would offer folks a chance to recant something they decided they didn't want to say after all and would still keep the continuity of the site intact

      That'd be less ugly than an empty node or even one full of long stretches of striked text...

      It wouldn't make the node owned by the NodeReaper, which leads to questions like unreaping and exclusion from searches, etc.

      On the other hand, it is uglier than a node with a mature update that is more informative and customized to the specific circumstances.

      On the gripping hand, I don't foresee such getting implemented anyway. So I'm not going try to hash out more details of the design. (I prefer the previously identified route of getting preview for updates and then edit histories).

      - tye        

        (I prefer the previously identified route of getting preview for updates and then edit histories).

        I'm curious about this....
        I certainly appreciate having the preview button available when creating a node, and I miss it when when updating.

        I tried a Super Search on "previewing updates" which turned up nothing. Is there a separate discussion on this elsewhere, or plans to implement it?

      I sometimes simply abandon a reply in mid-edit - pretty much a self reap before posting. Using the preview button and actually reading what you have written often aids in such a decision.

      The most common source of duplicate posts I've noticed is when a node is posted by Anonymous Monk, then is duplicated by a registered monk. Perhaps a solution to that is to provide a way of changing ownership of the original node so it doesn't need to be duplicated? I guess this could lead to problems with people trying to claim nodes they didn't author so it's not clear that this solution would be better than the (relatively minor) current problem.


      Perl is Huffman encoded by design.
        it is trivial to change the owner of a node from anonymonk to a registered user - provided you have appropriate permissions to edit the node.

        I suspect the most elegant implementation of what you suggest would be to empower the janitors to do this and anyone could request that a node owner be changed from anonymonk by /msg'ing them

        I am not sure how to overcome the obvious issues of verifying the authenticity of the claim of ownership of a node and/or the issue of someone eventually trying to abuse this process for such things as reputation gain.

        Absent a solution for those probs - I doubt anything like this would ever see the light of day.

Log In?
Username:
Password:

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

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (7)
As of 2014-12-27 02:20 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

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





    Results (176 votes), past polls