[sldev] Suggestion to improve moderation capabilities: auto-mute banned avatars

[Kamilion]

Personally, I wouldn't mind it it popped up the little blue box on the
bottom normally reserved for "Some Person has come online" that said
"Some Person has been auto-muted". As long as the user has a fair
chance of being informed of an action, it's perfectly fine for the
server to automatically perform actions that benefit the user.
However, the mute should also be automatically removed either after X
hours or when leaving the parcel or simulator. Any automated action
should be undone after it's no longer needed.

Just my two cents. ;)

On 9/12/07, Andre Roche <roamingryozu at gmail.com> wrote:
> Another feature to throw into that would be to, effective immediately upon
> banning from the land, return all objects owned by that person.  As far as
> the muting thing goes.  I don't think the server should ever tell my
> personal client's mute list to add someone to it without me knowing.  On the
> other hand, I think you're right in the idea that a person who is banned
> from a parcel should have no effect on or visibility by persons within that
> area.
>
> Nice set up you got there with the particle tracker Dale.  Only thing I can
> think to suggest is that the particle system itself isn't so blatantly
> displayed...  Might upset some scripters/particle makers with that.
>
>
> On 9/12/07, Dale Glass <dale at daleglass.net> wrote:
> >
> > I've been working on various improvements to make moderation as fast and
> > convenient and possible.
> >
> > Now I've added:
> >
> > An avatar list, which allows finding people quickly, as well as performing
> > actions like ejecting from land on multiple people at once.
> >
> > An option to log the owner and location of speaking objects, for tracking
> > down spam and objects trying to impersonate an avatar.
> >
> > An "event log", currently tracking particle emission, and soon sounds as
> > well. This allows to figure out who is the one flooding the area in
> > particles near instantly. Here's a picture of this in action (not released
> > yet):
> http://daleglass.net/images/screenshots/particles3.png
> >
> >
> > So I got to test all this in practice yesterday during an attack on
> > Luskwood. Result was: As intended, this makes it very quick and easy to
> > find the attacker and ban them. But that's not much good.
> >
> > I teleported to Lusk, saw the particles, and issued the command to ban the
> > owner of particle spamming self-replicating objectsr maybe 5 seconds after
> > I saw the particles. But the practical result was about zilch because the
> > attacker wasn't on Luskwood land (probably nowhere near as well) in the
> > first place. So somebody who possibly never intended to enter Luskwood
> > land got banned from there and was still causing problems just fine. This
> > is not good.
> >
> >
> > My suggestion to fix this: Automatically temporarily add to everybody's
> > mute list the avatars banned from the parcel, while the avatar remains on
> > the parcel. This will mean that while you're on the parcel where somebody
> > is banned, they or their particles won't be seen if they're hovering right
> > outside the banline.
> >
> > This should be an option, so that the area's moderators can see what is
> > really going on if needed. This needs to be on by default, because
> > otherwise it's ineffective.
> >
> >
> > In principle, part of this can be implemented quite easily by requesting
> > the parcel's banlist each time a parcel border is crossed (could have a
> > delay to save some performance impact and avoid unnecessary banlist
> > fetches while flying around).
> >
> > LL's help would be needed so that when somebody updates the banlist all
> the
> > viewers in the parcel automatically get their list updated.
> >
> >
> > How does this sound?
> >
> > _______________________________________________
> > Click here to unsubscribe or manage your list subscription:
> >
> /index.html
> >
> >
> >
>
>
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>
>