Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much
 
PerlMonks  

Re^3: How should Perlmonks deal with Plagiarism?

by planetscape (Chancellor)
on Oct 07, 2006 at 04:38 UTC ( #576795=note: print w/replies, xml ) Need Help??


in reply to Re^2: How should Perlmonks deal with Plagiarism?
in thread How should Perlmonks deal with Plagiarism?

Technically, one cannot approve or front-page one's own nodes. However, if one is working in concert with another, it's obviously possible to see how one account can approve, front-page, upvote another, etc. Approval can be withdrawn by janitors, though, and anyone who suspects behaviour as outlined above is advised to give the gods and/or janitors a heads-up. (janitors as a user-group can be messaged the same way you'd message another Monk.)

planetscape
  • Comment on Re^3: How should Perlmonks deal with Plagiarism?

Replies are listed 'Best First'.
Re^4: How should Perlmonks deal with Plagiarism?
by grep (Monsignor) on Oct 07, 2006 at 06:03 UTC
    Well here's at least one example of one approving the other's plagiarism.


    grep
    One dead unjugged rabbit fish later

      There are many actually. Also interesting is the preponderance of root nodes madtoperl posted. Most monks who have been around for a while have contributed many more replies than they have root nodes.


      DWIM is Perl's answer to Gödel

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://576795]
help
Chatterbox?
[Corion]: ambrus: Yes but I also need to implement the file / IO watcher, because Prima has that (in Prima::File), and I need to supply the appropriate thing to make push_write etc. work with Prima
[ambrus]: Corion: yes, you need to implement the io watcher, which should be simple because Prima::File is basically that, and the timer watcher form Prima::Timer
[Corion]: ... or so I think. As I said, I'm somewhat vague on how to make AnyEvent cooperate with a callback-driven IO event loop that gives me callbacks when data is available or can be written
[ambrus]: what push_write thing? I don't think you need that. that's implemented generically by AnyEvent::Handle
[Corion]: ambrus: Yeah, that's what I think as well. But you give me an idea, maybe I should start with implementing the timer, as that should be far simpler and with fewer edge-cases/nasty interaction than the file watcher
[ambrus]: You only provide the watcher part that tells when the handle is readable or writable, not the actual writing and reading.
[Corion]: ambrus: Hmmm. It makes sense that AnyEvent would implement the push_write itself, but I think I don't have a good idea of where the boundary between AnyEvent and the underlying event system lies... Implementing the timer should give me a better idea
[ambrus]: Corion: push_write is in the higher level abstraction of AnyEvent::Handle, not in the watcher
[Corion]: ambrus: Hmm - rereading Prima::File, that merrily coincides with what Prima does - it tells you "you can read", and you're supposed to read from the fh yourself. I thought it called you with the data already read, which would've been harder to integrate
[ambrus]: you just need an io watcher, created by &AnyEvent::Impl:: Whatever::io(...)

How do I use this? | Other CB clients
Other Users?
Others avoiding work at the Monastery: (8)
As of 2016-12-08 12:18 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    On a regular basis, I'm most likely to spy upon:













    Results (141 votes). Check out past polls.