✨ Feature Requests

I’ve had this feature idea for a long time, and I think it would be a small but very useful improvement to the Edit Object window. When working in the Content tab, it would be extremely helpful if the name of the currently selected object/prim were also displayed somewhere within the Content tab itself.

Simple request - people ejected or banned from groups, shouldn't be notified that they have been. Sometimes a user is being removed through no major fault, or for fault that isn't immediately occurring within the group itself. Being able to remove or ban silently is less likely to cause immediate or more volatile response. Sure, sometimes it'll still happen - but there's also good chance it'll go by unnoticed, or unnoticed enough for tension to die down. You aren't notified when someone removes you from their friends list, or bans you from a region or parcel - so why are people still notified when they're removed from groups? If the admins wish to inform a user a reason for the eject / ban, I don't see why they can't just send an IM of their own accord. I don't currently see good reason to keep these notifications.

We need more pinning abilities like Pin Group... Pin Conversations In the Conversation Log window it would be helpful to be able to pin conversations to the top. This would benefit residents who need to continue a conversation with a non-contact ie: creators, CSRs, etc. This way you can pin conversations that need to be handled to the top then unpin once resolved. Pin Contact In the contact list add the ability to pin your favorite contacts to the top. Please and thank you!

As a creator sometimes I have ongoing communications with customers. Sometimes I remember that somebody messaged me with a query and I need to send them an update, but I can't remember who it was. The 'Recent' Tab seems to always be empty during those times (is it tied to login session?). What I really need is some kind of UI that shows me who I have conversed with in IM over a given period of time. Let me see who I was talking to a day ago, a week ago etc. This will help me avoid missing important connections or leaving customers hanging because I've lost their username.

I would like to contribute Korean (ko) UI localization to the official Second Life Viewer. Korean UI support would help Korean-speaking residents navigate preferences, understand notifications, and use viewer features more comfortably. Before undertaking a full translation, I would like to confirm whether Linden Lab would consider accepting a new Korean localization. My proposed approach is to: Work in a separate branch using the existing English XUI files as the source. Begin with language selection, the login screen, and key preferences. Preserve XML identifiers, substitution placeholders, and strings marked as non-translatable. Test Korean font rendering, text clipping, layout, and language switching, and provide screenshots with the initial PR. Expand coverage through manageable PRs based on maintainer feedback. Could you please clarify: Is a new Korean UI localization currently welcome? Would an initial partial translation with English fallback be acceptable, or is a minimum level of coverage required? Which branch should the initial PR target, and who should coordinate the translation review? Are there additional translation guidelines or ongoing maintenance expectations? I would appreciate guidance on the scope and submission process before proceeding with the full translation.

I have a number of groups, as well as clubs I belong to where I am not interested in notices while off-line as they are notices of events about to happen. But I still need to receive these notices while i'm on-line. As a DJ, I get lots of off-line notices from other DJ's of their sets even while I'm asleep and off-line. I would like an extra check box so I can still get notices of events while I'm on-line but not collect past notices I am no longer interested in.

Long lamented on the SL forums, and anyplace SL users congregate, "the death of collaborative inworld building' is seen as a major social issue for many creatives and collaborative efforts. Reducing the inherent 'land impact' of the 'basic-building-blocks-of-sl' would make prim-building more of a viable activity, both as a social/collaborative outlet in sandboxes and limited impact private builds, but also as a path toward helping new users function in the user-generated-content economy. A reasonably modeled and textured prim-built end-table will often have many fewer vertices than an imported mesh counterpart, yet through trickery of LOD generation and physics models, the uploaded mesh can achieve land impacts that make the prim-built version completely non-viable in most cases. Reducing the land impact of primitives also has the upshot of encouraging simple lighting, the placing of more reflection probes, and so on.. which our shared world desperately needs to encourage in a 2026 version of SL, with more and more PBR avatars' butts reflecting the blue sky outside.

A Group owner or admin can post a notice in the group. They then can tag a box so that this group notice will not expire/disappear in 2 weeks. This will be helpful when you want an object or notecard or certain instructional messages to be available for a longer period. It would prevent me (and other group owners/officers) from having to repost certain things (and forgetting that i have to) I also see it in other groups where admins point to a notice with instructions or an object and then realize it is gone and they have to hurry to repost. It could be limited to a certain number to not strain servers but i think it would bring server load down. I am not that tech savvy so i hope i explained it well.

Calculating how many prims you get on what size parcel has always been a chore. It would so much easier, if the allotment were 1 prim per square meter or 1/2 prim per square meter. Please consider this.

Is there a way you can create folders within the group notices, so you can keep those you will to attend... or maybe a calendar? If you go through and keep the notices you want they get buried ... under all the new notices. A way to seperate and attach to a calendar would increase community interaction.