[sldev] Re: More client forwarded chat channels.

[Able Whitman]

This would definitely be a good, flexible way to share mute lists between
users, something that I would really like to see. Unfortunately I'm
restricted to only modifying the client (until the server code is released,
hint, hint), so mute list sharing is out of the scope of my patch for now :)

On 6/22/07, Argent Stonecutter <secret.argent at gmail.com> wrote:
>
> On 21-Jun-2007, at 20:01, Able Whitman wrote:
> > I meant that I wasn't keen on reserving a channel just for the
> > purposes of allowing scriptable muting of objects. General-purpose
> > client channels are a good idea, though.
>
> Allowing multiple channels mostly lets you "subscribe" to different
> sets of muting advertisements. There's no security or privacy or
> interference reasons for doing so. Having a single channel would
> avoid the problem of having to find out what channel the parcel
> you're on is using.
>
> Mute advisories from objects you don't own should only be honored
> while you're on the parcel that they're broadcasting from. When you
> live the parcel the advisories should come back.
>
> A user interface to allow you to see what individual advisers or
> channels have muted, and track how often they're coming in, and to
> ignore them... that's something that absolutely needs to be in the
> final version. To experiment with the model you'd only need something
> like this:
>
> Dialog: "The parcel you're in has a "mute list", would you like to
> use it? (yes) (no)"
>
> For objects you own, this dialog wouldn't come up.
>
> Griefers wouldn't be a problem, since you would only accept mute
> advisements from objects you don't own if they have the same owner as
> the parcel you're on. If they come in too fast... you could simply
> mute them. :)
>
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20070622/4a2eca54/attachment.htm