Erik Moeller wrote:
> 1) You'll need some capability for banning
signed in users.
What's the point? They'd just log out.
For one thing, we ban offensive usernames. For another, we don't give
sysops the ability to view IP addresses of signed in users, so they can't
ban their IP because they don't know it.
The idea here is that in each row, either userid or
iprange is NULL (but
not both). Banning a single IP is possible because anonymous edits
generate pseudo-accounts and thus a userid.
Works for me.
> 4) While you're at it, you may want to think
about a better access rights
> system than simple sysop/non-sysop. ACLs would probably work best.
Hm. I'm not very familiar with the concept of ACLs
Lists, I assume). What in particular can they do that userprops cannot?
Well, the idea is that you can set permissions on a per page basis, and do
* cannot edit
Hans can edit
Heinz can edit
* can edit
Hans cannot edit
Heinz cannot edit
* can edit
anon cannot edit
This might be useful for, e.g., allowing certain users to edit the Main
Page without giving them sysop privileges. It would also allow use of your
engine in other CMS contexts. Might be doable via the articleprops.