Re: Re: Taking away edit-own-nodes privledges.

I hadn't intended this as a punishment... possibly, I did a bad job explaining my point... possibly it's simply a bad idea.

Keeping an edit history would be a very good idea... unfornatly, it's also fairly difficult. Both, it would be difficult to add to the existing archetecure in a clean matter, and it would take a lot of db space and energy, unless implemented very carefuly.

Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).

Comment on Re: Re: Taking away edit-own-nodes privledges.

Replies are listed 'Best First'.
Re: Re: Re: Taking away edit-own-nodes privledges. by tilly (Archbishop) on Dec 20, 2003 at 06:47 UTC
I have no idea how hard it would be to add to the existing architecture. But the db space isn't that bad. Or at least no worse than letting a few more people post. (My guess is that when people see that a history of changes are left, they won't be as inclined to make cosmetic corrections.) And whether or not your idea is meant as a punishment, the people who wind up restricted will feel punished.	[reply]