1) spam on groups, given the inadequacy of 'eject' and the restrictiveness of invite-only status
2) greifing on *all* land (both parcel and estate, both mainland and island)
3) privacy invasions by banned users such as scanning through ban lines
4) the inability to ban large numbers of avatars easily (e.g. griefer teams)
5) the difficulties involved in having a ban list managed by many different people
6) the difficulties of having your ban list get full too fast (e.g. for busy, often-griefed locations)
This proposal is finalised - that is, I won't be editing/changing it after today,17/July/06. The reason is simple : I want to make sure people know that the above list is *exactly* what they are voting on.
Here is the list of features this proposal stands for:
---> With regard to all ban/allow lists generally :
1&2) Ban/allow lists should be managable by multiple people, secure against alt-griefing, and easy to maintain.
All ban/allow lists in SL should have the fields :
* avatar or group name effected.
* 'active' checkbox. If checked, is in effect, if unchecked, is not in effect. Useful for giving people an 'official' warning before banning them proper, or for marking someone as a troublemaker without banning them.
* 'set by' field, listing the name of the avatar who set the ban or whitelist entry
* 'reason' field, an optional string set by the avatar who set the ban, read only afterwards
* 'set on' field, listing the time that the ban/allow was added on
* 'last used' field (for land bans only), stating how long ago someone affected by this ban/allow was within normal rezzing range of the parcel or tried to teleport directly onto the parcel. Whenever an av can see a parcel, and they are banned on it, the last used time of their ban on that parcel should be updated. This field should be displayed as a number and then a time interval, such as "52 days", "12 minitues", "15 seconds", "3 hours", or similar. Time intervals less than 30 days would display as white, between 30 and 90 days as yellow, and over 90 days as red.
* 'ban alts' field, on by default. If this box is checked, any alts of any person affected by the entry are also effected in exactly the same way. The should work in a way that means land/group/estate owners can't tell who someone's alt is, but can be sure a ban will work against alts too.
The banlist should be forward/reverse sortable by any of these fields.
These functions would :
* enable us to identify provide us a way to give someone a 'non-active ban', a great way to flag up troublemakers so other admins can be quicker to ban them later.
* make managing a big ban list much easier by helping to identify old, inactive entries on the ban list, so they can be pruned.
* make managing a ban list between a group of people much easier, as we can now see who set what ban and why.
* make it possible for us to combat griefing by alts, by treating bans as per-person, instead of per-account as they currently are.
3) "Ban/allow by group" options
Whereever there is a 'banned avatars' list, there should also be a 'banned groups' list, such that anyone in the banned group would count as banned just as if they were explicitly named. Wherever there is a 'allowed avatars' list, there should also be an 'allowed groups' list. Access would be checked as follows :
* if the person is named explicitly on the allowed avatars list, allow them
* if the person is named explictly on the banned avatars list, deny them
* if the person is a member of a banned group, deny them
* if the person is a member of an allowed group, allow them
This would enable you to, say, ban a list of known troublemakers but make an exception for the few nice people in a group. It would also stop someone joining one of your 'allowed' groups to evade a group ban.
4) Bigger ban lists
Ban list maximum lengths should be increased to 500 for the avatar-based ban list and 50 for the group-based ban list. 50 is simply not enough.
5) Ban lists must be scriptable at all levels
One should be able to read from and modify ban lists, parcel, estate and group, via LSL scripts.
This would let you detect, for example, when banned avatars approached your parcel.
This would let you use an object owned by the sim owner or estate managers to do estate-level bans without needing to give people estate manager permissions. That would result in potentially a HUGE benefit to sim owners because they could have lots of people with 'estate orb' access who can ban/unban but nothing else... and thus, sims get MUCH better security.
It would also allow you to use scripts that enforced a 'delete any ban unused for X days' rule, and other ideas such as potentially *automatic* estate bans for people who do various things. Imagine a Second Life where "no weapons" orbs exist, I think grumble Loudon already made one that detects weapons fire.... and they have the power to estate ban violators of the rules. Automatic security enforcement! I know some people may be squeamish about giving that level of power to bots, but remember, some people may find these scripted tools VERY useful and we are not obliged to visit sims whose scripting we disagree with. Bans/Allows added by the script should display both the owner of the object that added it, and also the name of the object itself in its 'set by' field'. LSL-level access to ban/pass lists would enable things like ban list monitoring scripts and and 'neighbourhood watch' systems where parcels/sims could operate on a 'if someone gets banned here, they were probably *just* causing a problem here, so lets ban them for 1hour from nearby parcels, just to keep them away from the parcel they were banned on long enough to keep them out of scan range of that parcel'.
Basically, scripts would enable 3 great things : logging of ban/unban activity, banlist management via automatic rule-enforcing security devices, and various forms of ban sharing. They are a very good idea, as they give us Residents better abilities to collectively decide who we do and don't want on our land and have those decisions respected.
---> With regards to bans in groups :
6) Ban addition/removal permissions in groups
There should be a role/action based permission for adding/deleting people from the group's banned avatar and banned groups lists.
7) Anyone banned by a group should not be able to join or IM the group.
All avatars in a group's 'banned avatar' list, and all avatars which are members of any groups in its 'banned groups' list, should not be able to join the group. They should NEVER be able to IM the group, and they should be forced to completely leave any group IM session they are in when they are banned, and not allowed to start any more IMs to that group while banned.

If an avatar becomes banned while they have an open IM session to the group that they started, that IM session should be closed for EVERYONE in it (to banish spammy group IMs and avoid flooding people with "X has left this session" messages after the spammer is ejected).
9) Selected group members should be able to see banlist changes
There should be an 'action' in the group roles system : "is notified when ban list changes". Anyone in a role with this action is notified when additions/deletions are made from the ban list, being told who is added/deleted, by whom, and what reason the adder/deleter gave for the addition/deletion. Additionally when someone deletes an entry from a ban list, the reason that was on file for their original ban should be displayed alongside the reason that their ban was cleared.
---> With regards to Estate Tools :
10) If someone is estate banned an option should also be given to return ALL their objects as well
Automatic 'and return all ____'s objects?' popup when someone is estate banned.
If a resident is banned on the estate (by name or by a group they are a member of) they should not see the estate at all, they should not be able to teleport to the estate (even by Landmark!). If they are on the estate when they are banned they should be sent home. Further, there should be an automatic popup question if they own objects in the sim, that asks : "do you wish to return ALL of the now banned person _____'s objects?", defaulting to 'no'. It would work for all objects, scripted or not. It would preferably result in a small notice to the person doing the return stating how many objects were returned. Use of these functions should be logged by LL, so that when someone is ARed and then sim banned, LL's abuse team can verify that they did indeed rez objects/push/etc, and were then banned, and what objects they had returned to them by the estate manager. (e.g. if 100 objects named 'bullet' are returned, it should help LL's abuse team build a case).
11) It should be possible to easily share bans between estates.
There should be two more lists in the 'estate' section of 'estate tools'... : "accept shared bans from" and "offer shared bans to". These lists contain one or more names of other estates. If estate A has estate B in its 'accept shared bans from' list, and estate B has estate A in its 'offer shared bans to' list, then any avatar or group that counts as banned on estate B also counts as banned on Estate A.
In other words : if estate B offers to share its bans and estate A accepts, anyone who counts as banned on estate B also counts as banned on estate A.
Estates should be able to share bans to and recieved shared bans from lots of other estates at once, to faciliate the sharing of bans between estates of similar theme.
Estates should be able to have a two-way ban sharing relationship.
Estate owners and managers should never be able to be banned from their own estate by bans shared from other estates.
In the lists, estates where the relationship is established should display differently from ones where you are waiting for the other side to add you to their list. That way you can see which relationships are active and which are pending.
In the estate ban list, there should be an additional checkbox beside each avatar or group name : "share". If checked, the ban is shared with those estates you whare bans to. If not, it isn't.
Double-clicking the name of an estate you accept shared bans from should show all the bans they have that are marked 'shared'.
12) Deleted bans on an estate should be viewable for a short time after deletion
Estate bans which are removed should not disappear from the ban list at once, rather, they should appear greyed out for, say, 7 days. During this time they would not be active, but would be marked with the name of the person who removed them. This allows other estate managers and the estate owner to see when someone has removed a ban from an estate and reinstate it if needed.
---> With regards to Parcel Bans :
13) People who cannot access a parcel should not be able to see or interact with its contents and vice versa.
Anyone who does not have access to a parcel should not be able to see any objects or avatars on that parcel. They should not be able to see, hear or interact with *anything* in the parcel. People in the parcel should not be able to see them, and none of their scripts should work while they are in the parcel. They should not be able to rez objects in the parcel, or move already rezzed objects into the parcel. They'd be invisible to the parcel and the parcel and its contents invisible to them. They'd be able to move through it but not interact with it in any way. Being banned from parcels would completely remove an avatar's ability to interact with that parcel or people on it - even their scripted attachments using llSensor should not detect avatars in parcels they cannot access, and they should not see minimap blips for people who are in those parcels. No chat text on any channel by them or any of their objects should reach into the parcel. Preferably, 'ban lines' could be removed completely as there would be no reason not to let banned avatars fly around in parcels they are banned in (because they cannot do ANYTHING there)... so it would be needless to force them to leave. Plus, ban lines are ugly, and a solution where content on parcels one cannot access simply does not render at all is neater, cleaner, and hopefully will result in a lot less ugly features (ban lines) on the landscape, and a lot less impediment to peaceful Residents who harmlessly want to fly around.
14) Once the ban limit is reached, new bans should replace the ban which has gone unused the longest.
If the ban list is full and a new ban needs to be added, then the ban that which hasn't been used in the longest time should be dropped and the new ban added. A notice should be sent to the land owner the first time this happens, so that they understand what is going on. The notice should only be sent once, however, to avoid possible spamming of land owners.
----> Getting rid of unwanted objects
15) llReturnObject, GetPrimCountForObject, and family
Ok. There are lots of situations where you want to let people build on your land, but not "too much". For example, you're a mall owner and you want to let people have X amount of prims in your mall but you don't want them to break your prim limits. Unfortunately you can't enforce this, without llReturnObject. With llSensor you can detect objects. With a function like llGetPrimCountForObject you can see how many prims it has, and with llDetectedOwner you can see who owns it. Tallying all this up, you can produce totals for who owns how many prims in the area. Then, with llReturnObject, you can return the excess. Adding these functions would help the people who rent out space a LOT, be they landlords, mall owners, or even just normal landowners who want to let a friend build on their land but not to use up all their prims (they could have a warning orb scripted that IMs the friend when they have over X prims in the parcel).
The llReturnObject function would also be useful for security devices.
Make no mistake, banning someone from a parcel or estate that they have objects in should pop up a "and do you wish to return all their objects too?" box.... but for the moment, similar things can be accomplished with llReturnObject.
llReturnObjectKey(key object_key_to_return); <--- returns a single object identified by key
llReturnObjectName(name name_of_object_to_return); <---- returns a single object identified by name (good for dealing with chat spam objects!)
llReturnObjectAllByOwner(string ownername); <---- returns all objects owned by given owner name - perfect for clearing out griefer objects quickly!
I realise that this is asking a lot. I realise that LL staff have a lot on their plate. I wish I did not have to ask for these things.
However, while I was surfing the SL forums looking at proposals to deal with griefing, my sim was attacked by a group of people who attacked the sim using what appeared to be ICBMs, nukes, push guns and chat spam. This is unacceptable. When you have organised teams of griefers trying to take down sims, the situation has got serious, and it is time for more serious banning tools.
--------------------------
To vote for this, click HERE and vote for proposal 1632. Note that you must be logged in to the main SL website to vote. To add your votes to this proposal, make sure your name shows at the top right of the page, make sure you have votes free (use 'my votes' if you want to see what other proposals you have allocated votes to), and then use the drop-down box to allocate votes to this proposal. Note that you can only allocate 10 votes, total, to all the proposals in the voting system in total. You can allocate your 10 votes to this, or spread it more thinly, but whatever you do, please vote for *something* to make sure your voice is heard on the future direction of SL.
This proposal is *not* intended to replace the system whereby land owners can ban unverifieds from their land. Instead, this proposal is meant to cover a lot of things which that system of banning unverifieds does not provide (like bans for people who spam group chat, bans of griefer teams based on their group, and so on). This proposal is also intended to provide a way of banning based on people/groups that are known troublemakers, and to make these bans really have some weight. It is not intended to replace the verified/unverified banning system, it is intended to provide other options (such as banning by groups), and more power in the banning system overall (e.g. bans from groups and stopping banned people seeing what is on your land).
---------------------------
The above is my official version of this proposal. I realise that it is asking a lot. I realise that some people may worry it will lead to griefing by landowners and abuse by group officers. I firmly believe, however, that the net effect of these proposals will be positive - that the bad will be vastly outweighed by the good it does combatting griefing, spamming, and antisocial behaviour generally in Second Life. Lindens, I know you don't have the ability to meet all resident requests, but I think you should seriously consider each and every idea in this one. Even if you choose not to do some of them, please consider each in turn. I know you're already planning to make use of some ideas like these. So, please consider these ones?
