Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

If the three conditions you outlined were met, I would recommend:

  • posting a link within the thread to the original source
  • dropping the node rep to 0 if it were positive (or leaving it as-is if it were negative)
  • assessing a 10 XP penalty to the OP
  • appending "(plagiarised)" to the title of the node (not the whole thread) (yes, I know it is currently possible for the OP to edit it)

I think it is important to target only those nodes that were plagiarised - not every post ever written by the OP. This would specifically discourage the negative behavior and make the Monastery's response feel less like an unrestrained personal attack. It may also make it less likely that the OP simply create a new account and continue the behavior under a new nick. If a significant pattern of plagiarism was found (as in this case), then a graded progression of consequences (including locking out/deactivating the OP's account) could be considered.

Finally, I agree with what Joost said: reposting interesting questions or answers from other sources is (in general) fine "as long as the content is interesting (and prefererably attributed)" (emphasis mine).

Just my $0.02

In reply to Re^2: How should Perlmonks deal with Plagiarism? by bobf
in thread How should Perlmonks deal with Plagiarism? by liverpole

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

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others scrutinizing the Monastery: (6)
As of 2022-08-18 16:23 GMT
Find Nodes?
    Voting Booth?

    No recent polls found