On Fri, Oct 9, 2009 at 11:19, Evan Prodromou <e...@status.net> wrote:
> So, I've been working on adding user bans and blocks to 0.9.x, and I'm
> realizing that I don't like the current model. Currently, a banned user
> cannot post notices. A publicly blocked user's notices don't show up on the
> public page.
>
> I'd like to give site moderators the following ways to manage users:
>
> Sandbox. This is the logical extension of public blocks. The goal is to
> isolate a problem user and keep them from bothering others, but still let
> them use the platform. Sandboxed users...
>
> ...Don't show up in public timeline, tag lists, or search results.
> ...Don't generate outgoing emails when they subscribe to other users, send
> an @-message, etc.
> ...Can't send DMs or nudges.
> ...Have links they generate (homepage link, links in outgoing notices) add a
> nofollow to reduce search-engine juice.
> ...Can't post to a group.
>
> Silence. This is to completely prevent a user from participating without
> actually deleting their account. Along with silenced users...
>
> ...cannot post any notices.
> ...cannot subscribe to others.
> ...cannot join a group.
>
> Delete. Deletes the user's account; all notices, subscriptions, etc. are
> completely erased.
>
> Does that make sense? Another possibility is just to have two remedies:
> Sandbox and Delete.
>
> -Evan

I'd like a way for users to be able to post notices, and see their
notices in the public timeline when logged in, but have their notices
not show up in the public timeline for anyone else.  This would make
it more difficult for malicious users or spammers to get attention and
more difficult for them to realise they need to go register another
account.

Additionally, each of these consequences should be independently
addable and removable by the admin to an ACL that each user would
have.  There can be 'policy groups' for combinations (eg combinations
called Silence and Sandbox) to be quick and easy to apply.
_______________________________________________
StatusNet-dev mailing list
StatusNet-dev@lists.status.net
http://lists.status.net/mailman/listinfo/statusnet-dev

Reply via email to