|Pathologically Eclectic Rubbish Lister|
When I saw the Slashdot node, I thought.... hey, another use of Perl to teach cryptography. Nice. I jumped over to the monestary to post it. Found out that it was posted by another monk, who's intent was "Hey, this is a cool thing" rather than "Lets be political here and node everything to be like (obscure encription method to be named)". That was my intent too. Besides, we have rsa-in-3-lines-perl already.
And then I read merlyn's warning... which I belived was valid, but misplaced in it's context. Probably the only time I downvoted him.
I'm all for a scientific study of the code. I posted up a question regarding "read+" et al, which tye asked.
But Corion's censoring now makes me fear that all my nodes, nay, everyone's nodes, can be edited by an unauthorized third party. I only expect two partys to edit nodes I submit: vroom and the site owners, and myself.
One last point: I belive there may be a few sites which actually deconstruct the code, either C or Perl, to show how it would work. In this case, pointing monks to those sites would help (even if it duplicated efforts of those who posted on Slashdot. But then, we can say "these were found on Slashdot in that article....")
Update: Corion sent me a message making it clearer on what editors should or should not do. I must agree with tye that editors should only move a node, but not mess with it's contents. I would reserve the "last resort/extreeme case" for the editors, once throughly discussed between the editors and vroom (a la MAPS RBL); but I feel that this wasn't the case -- it was a first-strike censoring. I didn't see this node's contents. I wish I could, it would allow for a better call.