I am dealing with some similar issues as I struggle to deliver a multi-blog
environment which is both engaging, as well as somewhat moderated, for a
group of high school kids.
One issue is the seemingly monsterous prospect of administering to a
potentially large group of users. For this, a few of us have been
contemplating the relative usefulness of having a self-registration feature
for Pebble. Something like this is fairly low risk if the blog is posted on
an intranet, but other issues quickly arise if this is a public [internet]
I manage internet blogs, and so far, I have managed to enter all of my users
by hand, which seems daunting, but so far hasn't been too bad considering
that I currently only manage around 50-60 users. Once the amount of user
grows much larger however, I will begin to want more tools, such as a way to
hierarchically manage the user base with folders or something.
In terms of moderation, I would suggest a two-pronged approach of having two
different sets of blogs: one which is a forward facing blog (one I like to
call a "stage"), and another, which is members only for the same group of
writers which is considered a coresponding "back-stage" blog. The "stage"
blog is the one which is ultimately presented to the larger audience
(intranet or internet), so this is the one with the tighter moderation where
there are only contributors with a subset of publishers who control
everything. On the other hand, the "backstage" blog is much less restricted
in terms of moderation, and all or most users have "publisher" privs, but
the blog is also members-only, so only the members are exposed to any
problem posts - where problem posters can be moderated and subsequently be
relegated to "contributor" only, or no access as necessary to deal with
Just some thoughts.
p.s. You might also want to check the PebbleUserGroup.org for more ideas.
On Dec 8, 2007 8:08 PM, man tree <treeman1874@...> wrote:
> Hi all,
> I'm "treeman" who is the social worker in the young centre.
> I would like to set a blog for my member, staffs and guest who can share
> their favours there.
> My IT consultant recommended me to install pebble as it suits our system.
> After I installed the pebble, I try to do testing in it,
> Some questions would like to ask:
> For the security of the pebble,
> I read there are 4 types of the users: admin, owner, publisher,
> But could I re-organize the function of those users?
> As I found the problems:
> Could pebble support the function of multi-author in the blog?
> If I let the member or guest to post the entries in the blog, should be
> chosen the role of "contributor".
> But to be the staff of me, I couldn't want to authorize all the function
> of contributor to our members.
> As most members are the youngsters, couldn't expect their behaviour in the
> We would like to control all the entries and manage the categories for
> them, also the below functions, such as:
> a) Add/remove referer filter
> b) Add/edit/remove/clone blog entry
> c) Add/edit/remove category
> d)Add/edit/remove static page
> e) Approve/Reject/Remove responses
> As I play the role of contributor with difference accounts (like member A
> and B),
> A has the rights to edit and delete the entries of B, and images and
> It's quite strange....is there any setting to control?
> I suppose pebble has the different levels having different (and
> configurable) privileges with regard to publishing, editing, options, and
> other users. If pebble doesnt to do this type of function, Since my boss
> already approved to install the pebble in our web, he believed the blog can
> support the function of multi-users with the best of access level. I feel
> worry now if I open the blog for our members for those unsolved problems.
> Please advise.
> SF.Net email is sponsored by:
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> Pebble-user mailing list