One of these days I will have time to expand on my posts. Maybe less storms this week and less guests oh and less other distractions.
« Reply #15, on June 4th, 2013, 06:14 AM »
tl:dr; do we actually *need* or *want* post count permissions? It seems like it has served to confuse people more than it has helped them.
tl:dr; The idea of primary/secondary groups is obsolete, I want to move them to a separate table, and I have funky ideas about changing post count groups including their permissions if we still want them.
Also tl:dr; I would explicitly add *everyone* to 'Regular Members' if they are logged in. This seems more logical to me that the current situation which is a by-product of the primary/secondary group antics.
tl:dr; We could reformulate admin powers to be less overarching and more granular. This has consequences for management too.
As you underlined an important thing would be to have groups able to inherit permissions (or whatever) when post count increases (i.e. 0+, 50+, 100+ as you described).
This is probably the most useful thing about post-based groups.
Not sure how else use them since I always prefer to set my permissions in stone. :P
Move groups to a separate table is something I was considering me too, though I've never been in the mood of actually do it (mainly because I find a pita write the upgrade scripts... :angel: )
That (having "regular member" lost when changing the primary group) is one of the things that confuses people more than anything else I think (at least it is frequently confusing for me :P).
What I had in mind can be sort of summarised in two admin "roles": one that has access to the server (and so it can do *anything*, in fact the current SMF-like admin), and another one that doesn't have access to the server and so he can still do many "admin" things, but not any that requires some server interaction (mods, themes, server settings, etc.).
|The way it's meant to be|