Second Life group list changes explained

A note of explanation. I first published on this update on Thursday, June 4th, PDT. However, that post was withdrawn out of respect of a request from Linden Lab that I not blog on the change at that time. Subsequent discussions with the Lab led to an agreement that I could blog in full on the matter once the change had been deployed across the grid. Hence this post.

Until now, it has been possible to open the details for any Second Life group you have joined and display all the information relating to that group, including the list of members.

However, with the new update, groups with 5,000 or more members will no longer display the list of members unless:

  • You are assigned the Owner or Officer role within the group
  • You are assigned an ability within the group which requires the members list to be displayed (e.g. you are able to assign members to assigners roles, or are able to eject / ban people from the group, etc.).

Instead, and until corresponding changes are made to the viewer, all you will see on opening the members list as a message stating “Retrieving member list (0 / XXXXX)” – where XXXXX is the total number of members in a the group, as shown in the images below.

The back-end cange currently on the server RC channels means that group member lists will not load (or may be truncated until the change is fully deployed) for those groups wil more than 5,000 members
The change to the logic on accessing group member lists for large (5,000+ members) groups means that the members list will no longer display for members of the group, unless they are assigned either the owner or officer role, or an ability that requires they can view the list.  Instead, and for the time being, the above message (illustrated using both the LL and Firestorm viewers) is displayed – click for full size

This update has been made for a number of reasons, including:

  • Where very large groups are concerned, the full list of members has rarely completely loaded into the viewer – it has only seemed that the list has loaded
  • Tests have shown that in order for very large groups (e.g. tens of thousands of members) to load can take on the order of 10 or more minutes, during which time no other activities within the viewer can be carried out
  • Opening the members group list for large groups can result in performance impacts elsewhere (notably in group chat, as we’ve seen with changes made to that service recently).

In particular, the update is related to additional changes the Lab intends to make to the viewer-side code for group management, as Oz Linden, the Lab’s Technical Director for Second Life, explains:

It turns out – and this was one of the reasons we made the change on the RC channel – because we weren’t really sure what it would affect. But it turns out there are a bunch of places in the viewer, where the viewer triggers these requests for all the members of a group where it’s not even going to use the data … So some of those requests are kind-of bogus and not helpful, and we’re going to be making a set of changes to take those out, and replace them with something more focused.

Do note, however, that this change is not in any way connected to the recent increase in the number of groups Premium members can join, and it is believe that around 600-700 groups are affected by the change.

The initial deployment of the update on the server RC channels on Wednesday, June 3rd gave rise to some concern, notably:

  • The message currently displayed by the viewer suggests that rather than the member’s list being prevented from loading, it has simply stalled or perhaps timed-out, which could result in elevated support calls
  • The change breaks a lot of ways in which a group’s members list is used – see BUG-9393
  • In particular, the change means that people unable to see the members list can no longer ascertain which owners / officers are on-line and in a position to assist with any group-related issues which might occur.

Acknowledging some of these points during the Server Beta User Group meeting on Thursday, June 4th, Oz said:

 There are some things we need to do in the viewer to make some of these changes clearer… those changes will be made as soon as we can … In the mean time, if large groups want their officers to be reachable, they may want to put something in the description to help with that.

Further to this, and in relation to making information on group owners / officer visible to all members of an affected group, and on improving the currently-displayed message in the viewer, Oz further stated during the TPV Developer meeting on Friday, June 5th:

We will find a way to make that information available in the fullness of time [owners / officers], but it probably won’t be real quick … We’re going to fix the problems, but it’s going to require building some new interfaces for things like, “show me who the officers are”.

There are certainly going to be some bug fixes for the viewer coming quite quickly, quite probably in the next maintenance viewer, not the one that will get released next week [week #24]  but the next one, that will clean-up how things look. You’ll actually get a positive indication that you can’t see this list, or whatever. But we’re still fiddling with that.

Thus, while the changes to large groups may initially seem a little confusing, they are part of a larger attempt to improve group management functions within the viewer, and the Lab does recognise that more needs to be done to make key information within groups clearer to members.

In the meantime, please remember this change only affects those groups with 5,000 or more members, and does not prevent those assigned roles / abilities that require them to be able to see the group’s member list. Groups with less than 5,000 members remain unaffected by the change, and all members will continue to be able to see the group members lists for these when viewing a group’s information.


10 thoughts on “Second Life group list changes explained

  1. “You’ll actually get a positive indication that you can’t see this list, or whatever.”

    mmhhmm nice one Oz . And no notice from LL.

    Biggest user groups get no information and improvements coming “in the fullness of time [owners / officers], but it probably won’t be real quick …”

    Customers are impacted by these changes. CUSTOMERS.

    Don’t they have a person at the Lab who is charged with thinking about things from a residents point of view?

    Absolutely , I am glad they are working on chat but it shouldn’t be one step forward and two back.


  2. I like Erik’s suggestion. Why penalize everyone?! As Bet said, one step forward, two steps back. Pathetic decision! Please reconsider!


    1. As noted in the article. It’s not just viewing the list that’s the problem, it’s everything else that’s entailed when the list is loaded. The fact that very large group lists actually don’t load (although they may seem to), that the list can have an impact elsewhere within SL operations, etc. Also, this is only a first (if somewhat drastic, for those genuinely affected) pass at trying to improve group management overall.


  3. This is pure longer can we even SEE who owns and runs the groups, so if someone other then the creator is in charge unless you personally know this you’re a little freakin’ screwed. One step forward and a fall in a ditch backward. For pete’s sake what is wrong with telling the residents about this stuff beforehand? Get some LOGICAL input first!!


    1. It terms of group ownership, that can still be seen via the General tab (owner = creator). The greater problem is, as mentioned, the inability to see any officers within the group should their assistance be needed.

      There were broader reasons for implementing the change sooner rather than later, which appear to have been security related. As noted in the article, the Lab is very aware of the shortfalls in the change, and so will hopefully be addressing things in the medium term.


  4. I was given this link in the Firestorm chat. I am not able to leave larger groups that I belong to, I click ‘leave’ and nothing happens. If I try to leave a small group I get the confirmation box to click, confirming that I want to leave. I was told in the FS chat that the changes that are spoken of in this article are the reason I am not able to leave larger groups. I was offered no help on this issue except to ‘talk to LL’. Anyone know how to fix this?


    1. Are you using Firestorm 4.6.7 or an older version? If so, you are likely encountering BUG-9428. This also occurs in any viewer than does not have the Group Ban capability (e,g. official viewer 3.7.7 or older; Catznip R9, Exodus


Have any thoughts?

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.