✨ Feature Requests

I created a group several years ago for my store, and I wish I had the ability to change the group name (to remove brackets, change a word, etc.). I'd even be willing to pay a small fee for this (similar to changing my avatar name, but maybe payable in Lindens...like paying to partner/unpartner).

Second Life presents itself as a creative platform, but the 'Destination Guide' currently surfaces mostly lifestyle‑oriented categories (beaches, clubs, homes, shopping, photogenic regions, etc.). This unintentionally frames SL as a lifestyle simulator for new residents, even though the platform supports far more imaginative and non‑realistic content. There is no clear place in the 'Guide' for: surreal or dreamlike environments, experimental or conceptual builds, impossible architecture, non-realistic worlds, creative experiences that don't fit in existing categories. These spaces do exist in SL, but they're basically invisible to newcomers because the 'Guide' doesn't signal that they're part of the platform's identity. This isn't a criticism of existing categories, just an observation that a major creative segment of SL isn't represented. A few new categories would make the 'Destination Guide' more accurate and more welcoming to the imaginative side of the platform. Thanks!

Hi! I run a medium sized Community in Second Life. Over the years, my community, like many others moved from using the Group Chat features in Second Life to discord due to the need for the ability to have persistent discussions that happen over the long term. However, I feel that this has had the side effect of giving my community less of a reason to log into Second Life. After all, all of the community discussions happen outside of Second Life now in discord instead. I believe that if we had a persistent group chat, many users will log into Second Life, simply to see what messages they missed in the group chats whilst they were away, which will ultimately lead to more activity. Communities like mine would be able to transition back to using Second Life as our primary communication venue, which will be good for Second Life's long-term health as more people will be engaging with the platform and helping it to grow, and in turn help financially justify other much-needed improvements to the group chat system.

Like the notes tab available for user profiles, a notes tab for group profiles. For say, tracking group join fee prices, for example. Or making note of why we joined that group in the first place. Or club schedules.

I think that the group owner the one that started the group should be able to remove and and all avitar the assign to the role of "OWNER" when people leave the group . It would be very much handy then having to wait on a trouble ticket.

Currently, Abuse Reports for harassment in Second Life can only be submitted inworld, where the interface allows little more than a short paragraph and offers no practical way to attach supporting evidence. Reports can also be initiated through the Boxy chatbot, but that method is similarly limited and does not allow residents to fully document coordinated harassment. This makes it difficult to report situations that might also originate off-platform but result in a great degree of inworld disruption. Additionally, Linden Lab’s Support Ticket system only allows Abuse Appeal submissions, which occur after enforcement actions may already have been taken, leaving residents with no prior way to submit detailed context or evidence explaining the initial abuse. Allowing harassment reports to be submitted via Support Tickets with adequate space and evidence attachments would benefit residents by enabling clearer, better-documented reports, while also supporting Linden Lab’s ability to review reports submitted by residents concerning harassment directed at Linden Lab staff. This would help Governance more efficiently investigate coordinated or bad-faith harassment campaigns affecting residents, staff, and the broader Second Life community, improving accuracy, fairness, and community safety. If there are other methods to submit a detailed harassment report to Linden Lab with supporting evidence that will be investigated, then please include those methods in a reply or comments. Thank you for considering an improved reporting process that enables more thorough review of harassment.

I would like to suggest that Second Life PLUS or higher memberships should have an alternative to static housing locations. I would like to see Linden Labs establish RV Parks and make it possible for PLUS or higher memberships to have a temporary spot in an RV Park and drive the Linden Road System and see many places. Obviously, this means mobile home RVs, like the large ones you see on the road. maybe something like the Benz ones with the box on the back. Being able to reserve a spot would be nice. Having a max duration would prevent people from squatting at the best locations, but this could be a way for Linden Labs to reduce the constant turnover of Linden Homes. And create some fun activities like collecting Park "stamps" or travel "badges".

As has been noted over and over again, the increase in phishing spam links is or has gotten out of control. In the following, I propose a practical way in which to address this issue which would seriously curb the issue if not altogether get rid of such an activity. Create new role abilities. New abilities would have defined rules for group owner, group moderator(s) or other trusted individuals to be the only allowed individuals to post links in a group. Sub-classification for members who don't fit the aforementioned roles to be allowed only to post image links from known/well established image sharing sites. (This too should have a on/off toggle to prevent any type of abuse as needed) Group owners/moderators can have/create an allowed list of URL's that are permitted in their group. Example: Marketplace.secondlife.com Defining permitted URLs allows only those that are an exact match and prevents misspelled and misleading links. In the event a user attempts to post outside of their role abilities, the post is blocked from being sent and user notified as to why. In the above proposed solution, spammers would not by default be allowed to post spam links in any group as the default persons of the established "everyone" role would not allow it nor any other default role as defined by the group administration. In consideration of what to do with groups whose administration has been absent for a period of 6 months or more, by default all link postings should be disabled until such a time (if ever) a group owner logs in and establishes who may post links. While some may see this as an unpopular option, it prevents those groups that some still use from being exploited. I propose this solution as if there is no ability to post phishing links, then there is less likelihood that users are entering in their credentials and their accounts being compromised as well as serving the great community good of people who just don't want to see this mess as there are other means of advertising for those who are interested. Regards, DJ Vicious

It would be very useful if the Notecard links were clickable. For example, in this image, I have two marketplace links, and if someone wants to access them, they need to copy the entire link and paste it into their browser. It would be much simpler if they could just click and be redirected to the mentioned page in the Notecard.

basically a webhook for script errors -- Nexii Malthus, summarizing what we need You develop scripts for Secondlife. You start hearing people reporting that your scripts are crashing. Now what? Unless it's a very reliable crash, you're kind of in unexplored territory. SL is vast, many unique and hard-to-reproduce situations could be happening. The crash log is seen by your end user, not by you. The developer cannot know how widespread the problem is, whether it's a bug in a SL Server update, whether it's an edge case in their own programming... Possibly avenue to a solution: An unmodified, compiled script has consistent bytecode, and if I understand it right, an internal asset id corresponding. The simulator knows when this item has crashed (and currently only generates a message to the owner on a message channel). Perhaps a developer could "flag" scripts for logging "that script", or the set of scripts for a project that is in the wild and reporting problems. The developer could view (on the web? in the viewer?) a simple log, aggregating the crash reports from the currently-logged scripts, grid-wide for each flagged script. Perhaps some bit of information like the simulator version/memory use/event queue at time of crash. The simulator knows all sorts of things about what happened; Any log improves the current total black-box situation. Eg, "hearing that scripts are crashing on region restart? start logging now and see what comes in". This would be a limited utility. The number of scripts we can flag and limit how many log entries each script holds would be small. This would not be a performance monitoring tool; it would be turned on when a problem is suspected, to capture what's happening "out there." Acknowledged implications: Plenty of privacy concerns abound. To avoid adding new means of tracking users, gaining access to personalized data etc: The developer should not be able to find out what specific region the script was in when it crashed The developer should not be able to view the script's memory The developer should not be able to view who was running the script Might be useful: What type of crash list of events queued simulator version number region status Anything else that could be useful without opening bad implications? Any other implications that need calling out?