However, the point that wrapping the entire bit of text in CODE instead of just the necessary parts is important, as the former case will make downloading the code that much harder. If the person feels that their post 'looks better' in fixed-width fonts, then they should be using PRE and TT tags for non-code parts, and CODE for code. They'll get just the same effect as if they used code, and and code they do have will be downloadable without extra luggage.

In the case for the editors, I think it's important that the introductary documentation that everyone is supposed to have read before posting (ha ha!) include the fact that posts might be edited, not for content (except in extreme cases), but for readibility if the CODE tag is misused.

My opinion is that PerlMonks provides the CODE tags feature for a specific purpose, namely to protect code blocks from HTML rendering and to provide a convenient way to download them. Using a CODE block around one's entire node goes against this purpose, without providing any benefit to the community.

Additionally, I feel that "censorship" is a serious word that is frequently used too lightly. I fail to see how a trivial change made to the formatting of a node to improve readibility could possibly be construed as censorship.

The first couple of times, I'd edit them and notify the author. If the problem persisted, I'd consider the author anti social and downvote (some) new nodes and request reaping of any that overly disrupted otherwise useful threads. If the author managed to make enough of a nuisance of him/herself, then the author would probably eventually find that s/he had "fogotten" his/her password.

I would not continue to edit (at least the majority of) them!

Are all-code posts that big of a problem? I think it ranks more closely to that of individual monks who persistantly post incorrect answers, use poor grammar, don't break their text into paragraphs, use <a href="http://www.perlmonks.nog/..."> instead of [...], etc. Sure these are all annoying, but I don't think any of them fall into the category of "let the editors fix them forever". (Yes, I know and accept that I will be fixing these types of problems "forever", but I refuse to keep fixing them for the same person over and over again and, if the person refuses to modify their behavior, then I think other editors should likewise not use their special powers futher.)

        - tye (but my friends call me "Tye")