-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Fred Bauder wrote:
Plautus satire is probably an older man. What you
suggest is
appropriate for younger users who get carried away. We should give 10
year olds plenty of chances to get it right.
Proposal for a new policy:
1. User does something stupid -> User is warned.
2. User does something stupid -> User is warned, pointed to relevant
policy pages.
3. User does something stupid -> User is blocked for 12 hours (which
will most likely be overnight), pointed to relevant policy pages.
At stage 3 (that is, third act of stupidity) some software changes are
required. Namely:
* Editing restriction to user's talk page (and *possibly* subpages of
their user_talk page)
* Edit link is automagically changed into View Source, but visiting an
&action=edit page will still reset the block
Possibly (or otherwise), I think something more drastic (but potentially
more beneficial) might be required if this doesn't/won't work:
Per-user, per-namespace, per-category blocking. Which means:
* User can be prevented from editing any pages in a particular namespace
(eg. articles);
* User can be prevented from editing any articles in a particular category
Now, tell me where and how to do these things in PHP (I'm fairly certain
I could do them in pseudocode), and they'll be implemented by Mediawiki
1.8 :)
- --
Alphax | /"\
Encrypted Email Preferred | \ / ASCII Ribbon Campaign
OpenPGP key ID: 0xF874C613 | X Against HTML email & vCards
http://tinyurl.com/cc9up | / \
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird -
http://enigmail.mozdev.org
iD8DBQFC6OcE/RxM5Ph0xhMRA0QpAJ9QRZMOSwYXQlNzV6mTYwrOlCVR6wCeLQGv
TVOyTFpI38+/HgVK2NUla30=
=9CJs
-----END PGP SIGNATURE-----