July 2026 SL Web User Group

The Web User Group meeting venue, Denby

The following notes cover the key points from the Web User Group (WUG) meeting, held on Wednesday July 1st, 2026. These notes form a summary of the items discussed and is not intended to be a full transcript. Pantera’s video is embedded at the end of this article, my thanks to her for providing it.

Meeting Overview

  • The Web User Group exists to provide an opportunity for discussion on Second Life web properties and their related functionalities / features. This includes, but is not limited to: the Marketplace, pages surfaced through the secondlife.com dashboard; the available portals (land, support, etc), and the forums.
  • As a rule, these meetings are conducted:
    • On the first Wednesday of the month at 14:00 SLT.
    • In both Voice and text.
    • At this location.
  • Meetings are open to anyone with a concern / interest in the above topics, and form one of a series of regular / semi-regular User Group meetings conducted by Linden Lab.
  • Dates and times of all current meetings can be found on the Second Life Public Calendar, and descriptions of meetings are defined on the SL wiki.

Web Services Updates

  • Under-the-hood Authentication/email service upgrades are complete, with some internal clean-up going on. However, now that all services are migrated/updated, LL can look towards adding more authentication options in the future.
  • Web search is slowly getting UI tweaks as LL hammers out how to present information in mobile and improve query responses. The latter – providing better tuned search results, should become more consistent over the next couple of months – is also on-going work.
  • Internal marketplace improvements around bulk redeliveries, which have sometimes been getting stuck + clean-up of search results/listings. If anyone is still experiencing issues, please file a report.

General Discussion – Marketplace

  • A question was asked if reviews on Marketplace listings are indexed by the search system. At one time they were, but as LL didn’t do anything with the data that aspect of indexing was removed to improve search performance.
  • Variants (having things like multiple colours for an item in a single listing:
    • Creators at the meeting were asked how many different variants of the same items did they tend to offer. Responses varied from 6 to 24 or 8 to 18.
    • Shoppers were asked how often in viewing items on the Marketplace (e.g. via search results or when browsing a store) did they see multiple variants of the same item. The responses were generally “too often”.
    • One suggestion to deal with the above – at least until the Variants capability surfaces – would be to add a filter to search allowing colours to be specified.
    • Creators were asked how they indicate to shoppers they have other versions / colours of a products available: this appeared to be through the Related Products option.
  • Store clean-up: creators were asked how frequently they clean their Marketplace stores of products (e.g. those that no longer sell, those they’ve deprecated, etc.). Answers varied from “never” to “every month”, with it also being pointed out that some creators will actually move older products from their in-world store to the MP to make room for vendors selling newer products in-world.
    • The above led to a suggestion of having a “Archive” where people could either see something like a list of older items / items that don’t sell so well from the creator and / or has the ability to offer redeliveries of such items, but  without the ability to purchase them.
  • A question was asked about the Last Updated field within listing and its accuracy.
    • Juniper Linden noted that it has a long-standing bug which actually looks at the wrong data, thus leading to incorrect dates being displayed. It is something on the “fix” list, but it has risen to the top of the list.
    • The suggestion was made that if it is giving false information, it should be disabled until fixed.
  • Marketplace content flagging (including flagging reviews):
    • The point was made this this needs a degree of overhaul (e.g. more Reasons for Flagging, etc.).
    • Juniper Linden indicated the flagging process is under review. Suggestions on categories for flagging via Canny were requested.

Marketplace Search Discussions

  • The inclusion of 3 Featured Items in search returns was highlighted as potentially confusing for a couple of reasons:
    • The items are not clearly labelled / differentiated from the result of the search returns on a page to be easily identified as Featured Items (that is, pad for).
    • Sometimes the three Featured Items do not appear to be related to the search term and could thus cause confusion / annoyance. For example: a search for (say) “Living room suites” returns a page of items in which the first three are two houses and an living room lighting set.
    • Juniper linden noted that the entire Featured Items element within the Marketplace will be receiving changes that should hopefully make it clearer as to which items displayed on a page are Featured Items.
  • Use of keywords:
    • A discussion on the use of “keywords” within listings titles, descriptions and keywords appears to result ins a bias towards such items in search results. The example cited was home décor items with something of an equestrian theme (e.g. including reference to horse tack or featuring a horse) utilise the term “equestrian” in the item title, within the keywords and within the item description (so effectively repeating it), all being listed first in the results of a search for “equestrian”.
    • This is somewhat hard to guard against, as it is not strictly keyword mis-use (much as using keywords such as “bed”, “four poster bed”, “canopied bed”, “canopy bed” isn’t exactly keyword stuffing a listing for a 4-poster bed).
    • However, the fact it does appear to push items to the top of search results regardless of relevance and / or sales volumes is something it was felt by LL should be investigated further, a a report on the issue was requested.
  • Marketplace search “relevance” being the default option when displaying results:
    • By default, search results are listed in terms of “relevance” – which is itself an esoteric terms, being based on various criteria LL cannot specify (as it potentially opens the door for gaming search).
    • This is a problem, as “relevance” can result in a lot of “old” and potentially outdated items being prioritised in search results. This can results in a) someone making a ill-informed purchase; and / or b) gives the impression much of the content in SL looks basic or “old”.
    • It was therefore suggested that perhaps Age: Newest First or Best Selling might be better defaults, or “relevance” is revisited and improved, and / or that the Last Updated field issue noted above is fixed, so users can see the actual age of an item.

TJay’s Marketplace Extension for Browsers

  • Related to the above, TJay’s Marketplace Extension for browsers was mentioned.
  • This adds a number of capabilities to Marketplace listings, including: an option to hide the Featured Items section (again, mentioned above) on the front page, category and search pages; a display of product keywords for a better understanding of each item’s attributes and keywords; the date an item was “first posted” (listed) on the Marketplace.
    • HOWEVER, as noted both on the extension’s download page notes, and possibly as a result of the Last Updated issue noted above, it is possible that the “first posted” date added by the extension might be inaccurate in some cases (I’ve used the Chrome extension for the last few years, and so far as I can tell, “first posted” seems to be generally accurate, outside of the warning given in the extension download pages).
  • Those wishing to try the extension can obtain it via the following links:
    • Chrome (work for the majority of variants – Epic, Brave, Gener8, etc)
    • Firefox.
    • Edge.

What Constitutes “Valid” Content?

  • The last part of the meeting was a fairly “spirited” (in chat) discussion on “valid” Marketplace content.
    • A viewpoint was raised that whilst not wishing to deprive a person of MP income, the Marketplace is ever-increasing in size, leading to a feeling among some “newer” creators producing “the latest” in goods, that they are being “squeezed” in the Marketplace, and that perhaps some action needs to be taken to remove “older” content on the basis of when the creator last logged in.
    • The counterpoint to this is that whether or not a creator has logged-in “recently” or not is irrelevant: if their goods (no matter how old) are selling, then there is a not unreasonable expectation that this should be allowed to continue.
    • The issue of support was also raised: is it fair for the MP to be selling goods which may generate support requests to the creator which simply go unanswered as they no longer log in? (The counterpoint here being just because a creator doesn’t respond doesn’t mean they are no longer active – they just might not care about the item in question.)
    • LL do attempt periodic clean-ups of the Marketplace which sees items that have not sold in X amount of time belonging to creators who have no logged-in to SL for Y amount of time (and also presumably have not cash-out out for a time?) being delisted (not deleted) from the MP.
    • A suggestion was made that creators who have not updated / sold content for a period of time should be e-mailed and informed that the item will receive a lower “relevance” rating in search results, decreasing its visibility. A feature request was also raised the idea of “de-ranking” items.
  • Please refer to the video below.

Next Meeting

  • Wednesday, August 5th, 2026.

2026 SL viewer release summaries week #26

Logos representative only and should not be seen as an endorsement / preference / recommendation

Updates from the week through to Sunday, June 28th, 2026

This summary is generally published every Monday, and is a list of SL viewer / client releases (official and TPV) made during the previous week. When reading it, please note:

  • It is based on my Current Viewer Releases Page, a list of all Second Life viewers and clients that are in popular use (and of which I am aware), and which are recognised as adhering to the TPV Policy.
  • This page includes comprehensive links to download pages, blog notes, release notes, etc., as well as links to any / all reviews of specific viewers / clients made within this blog.
  • By its nature, this summary presented here will always be in arrears, please refer to the Current Viewer Release Page for more up-to-date information.
  • Outside of the Official viewer, and as a rule, alpha / beta / nightly or release candidate viewer builds are not included; although on occasions, exceptions might be made.

Official LL Viewers

  • Default viewer  – 26.2.0.25386466510, May 19 -“flat” UI and font update – No change.
  • Second Life Lua Editor Alpha viewer 6.1.0.23768336784, April 29 – No change.

LL Viewer Resources

Third-party Viewers

V7-style

V1-style

  • Cool VL viewer Stable: 1.32.4.34; Experimental 1.32.5.4:  June 27 – release notes.

Mobile / Other Clients

  • No updates.

Additional TPV Resources

Related Links

2026 week #26: SL Open Source meeting

Hippotropolis Theatre: home of the OSD/TPVD meeting
The following notes were taken from:

  • My chat log of the Open-Source Developer (OSD) meeting held on Friday, June 26th, 2026, together with my chat log of that meeting.
  • Pantera’s video of the meeting (embedded at the end of this article) – my thanks to her for providing it.
Table of Contents

Meeting Purpose

  • The OSD meeting is a combining of the former Third Party Viewer Developer meeting and the Open Source Development meeting. It is open discussion of Second Life development, including but not limited to open source contributions, third-party viewer development and policy, and current open source programs.
    • This meeting is generally held twice a month on a Friday, at 13:00 SLT at the Hippotropolis Theatre and is generally text chat only.
  • Dates and times of meetings are recorded in the SL Public Calendar.

Official Viewer Status

  • Default viewer: Flat UI – 26.2.0.25386466510,  -“flat” UI and font update, dated May.
  • Second Life Project Viewers – Lua Editor Alpha viewer 6.1.0.23768336784, April 29.

Viewer Notes

  • 26.3 is still slated to be the next viewer to be issues, but when is currently TBD.
  • Lua (with Linux support) will be the next viewer after 26.3.
  • The next major update after Lua is likely to be vcpkg (under-the-hood viewer packaging), but this is probably going to be late summer before this surfaces.
  • Some upcoming viewer-side WebRTC updates:
    • libwebrtc is to be updated to m144
    • The issue with p2p/adhoc/conference calls dropping when opening Voice Preferences is getting a fix.
    • (Also, on the back-end, the WebRTC Voice-to-text experimentation is continuing.).
  • Geenz Linden is working on a pipeline split in the background that should make getting off of OpenGL generally easier. This won’t move the needle over night, and thus far is mostly code clean-up.

OpenGL, Vulkan

  • The majority of the meeting was a discussion on succeeding OpenGL, with a focus on Vulkan.
  • Geenz noted:
    • There are “a few plans brewing for Vulkan/Metal/D3D12 support”. For MacOS a rendering hardware interface (RHI) to target Metal.
    • Broadly speaking, there does not appear to be anything “super high risk under Vulkan”, but the Lab still needs to approach things with care.
    • Based on available stats, the number of people using “pre-Vulkan” hardware is no longer extensive & the viewer also logs the number of people using systems capable of Vulkan support.
    • However, the problem is not so much who can / is using Vulkan, but rather how up-to-date are people’s drivers and, “are there any landmines lurking in that specific driver/hardware combo” because SL still has to support hardware that doesn’t get driver updates, etc.
    • The work he did for masked water in things like boat hulls should be relatively easy to port.
  • One of the major questions with Vulkan support will be can users’ hardware support modern Vulkan extension (such as bindless, which is liable to be a major optimisation for SL if it goes the Vulkan route).
  • In terms of the general plan for switching APIs away from OpenGL, Geenz noted:
Right now the plan is vaguely shaped as: split out LLPipeline and related components (including the draw pools), setup a general interface for the viewer “core” to talk to “a renderer”, amber the OpenGL renderer beyond minor development as our “classic” renderer, and have a separate renderer that at first will be off by default until we’re confident we’ve taken care of everyone’s bugs sufficiently. The devil is in the details of course, but generally we want to avoid another PBR-shaped release where we’re having to speed towards shoving everyone onto something that needed more feedback before it released. So, people get a choice for a while with the target for the new stuff being “similar+”
  • So short term at least people with be able to switch between renderers, where “short term” is likely measured in years.
  • The chances are as LL gain confidence in different set-ups they will start enabling it by default for certain detected hardware.
  • Concern was raised that a switch-over could result in a “ALM moment” (ALM=Advanced Lighting Model) where peopl didn’t use the renderer because of the way it changed the appearance of scenes. However, the changing of APIs / providing different rendering APIs shouldn’t be such as issue, as scenes should look pretty much the same either way.

Other Items

  • The question of gathering region data for the purposes of producing things like 3D terrain maps was again raised. This has been passed around the majority of User Group meetings in a attempt to understand any limitations on the use of bots for this purpose. Ideally, the data would come directly from LL; however Geenz noted that LL cannot provide the data in its raw form, but it might be possible to get height / elevation data into the Map service.

Next Meeting

2026 week #26: SUG meeting summary

Missing Melody, May 2026 – blog post

The following notes were taken from the Tuesday, June 23, 2026 Simulator User Group (SUG) meeting. These notes form a summary of the items discussed, and are not intended to be a full transcript. They were taken from the video recording by Pantera, embedded at the end of this summary – my thanks to Pantera for providing it.

Meeting Overview

  • The Simulator User Group (also referred to by its older name of Server User Group) exists to provide an opportunity for discussion about simulator technology, bugs, and feature ideas is held every other Tuesday at 12:00 noon, SLT (holidays, etc., allowing), per the Second Life Public Calendar.
  • The “SUG Leviathan Hour” meetings are held on the Tuesdays which do not have a formal SUG meeting, and are chaired by Leviathan Linden. They are more brainstorming / general discussion sessions.
  • Meetings are held in text in-world, at this location.

Simulator Deployments

  • The Loganberry RC is now grid-wide.
  • The next simulator update will be called Mango.

In Brief

  • Rider Linden:
    • Has some fluent interfaces for the Lua project, with what he believes is a final version, with a PR in lsl_definitions.
    • Is now going to his object publishing work (a websocket API, to edit objects and their inventory, to allow things like vscode to see inworld objects and their contents etc., see here).
    • Note that this API will not recognise remote connections, but should be between the viewer and an external editor running on the same machine.
    • He also noted that LSL function interfaces and Lua function interfaces are both built from the same source file. So anything in one, should be available in the other.
  • Leviathan Linden:
    • Has added added OBJECT_LOCKED to llGetObjectDetails() via the Lua project. The new enum is available to LSL and will work in the mono runtime… but it won’t be delivered until the Lua project ships.
    • Has also been working to port Wolfgang’s game-control work from Alchemy to the official viewer game-control project. This is a work in progress, and some changes will be required.
    • Still needs to do some follow up work on Navmesh crash fix he was working on in week #23.
  • Roxie Linden noted that:
    • The WebRTC team is still working on some evaluation of options for voice-to-text transcription.
    • This work is still very much at the experimentation stage, so people should not expect to see it suddenly appearing.
    • There will need to be some tuning of sound filtering and voice activity detection for any transcription service to work, but this should not affect Voice quality.
  • Harold Linden (LUA):
    • Has mostly been on housekeeping work.
    • Is going to merge the work from the Lua branch back into the main server branch (with Lua still flagged off) so they get out of sync less.
    • He also plans to pull the new Luau changes from upstream since LL is a little behind with this.
    • Noted that as well, classes and Lua integers will be flagged off until they firm up, but the code will be part of the repo.
    • Noted in the general discussion that the Lua scheduler only gets one time slice per frame (its the same scheduler as used for Mono).
    • Overall, believes the project is now approaching “release quality”.
  • Monty Linden noted that lsl-definitions have been updated recently but not baked into a release and cycled around yet – this will happen “soonish”.

General Discussion

Please refer to the video below for  more on the following.

  • The issue of teleport disconnect viewer crashes was raised again.
    • As has been previously noted within SUG meetings, there is no singular cause of TP disconnects  / crashes. LL have been looking into causes and have been working to fix some of the causes.
    • Anecdotal evidence indicates that recent fixes have (in the current release viewer – “Flat UI”) have helped improve some issues.
  • There have been reported of IM chat failures occurring with the notification: Chat Session Aborted.
    • Two causes for these issues have been identified, and a fix for one was released as part of the Loganberry simulator update.
    • LL is actively working on the second, which appears to be one of the IM chat server misbehaving. The hope is that a fix will be deployed soon.
  • There was a discussion around the Lua scheduler (some of which is noted above) between 34 and 42 minutes of the meeting.
  • A general discussion on animations, including the potential for Lua to simplify things by using fewer scripts and for WIBNIs such as an IK system that simply directs where body parts should be (e.g. “bum on this cushion; elbow on this armrest”).
    • This included a discussion on llGetVisualParams, revocation of scripted animation permissions, etc. Please refer to the video.

Date of Next Meetings

  • Leviathan Linden: Tuesday, June 30, 2026.
  • Formal SUG meeting: Tuesday, July 7, 2026.

† The header images included in these summaries are not intended to represent anything discussed at the meetings; they are simply here to avoid a repeated image of a rooftop of people every week. They are taken from my list of region visits, with a link to the post for those interested.

June 2026 SL Trust and Safety User Group meeting

Linden Estate Services: Trust and Safety User Group meeting place
The following notes were taken from:

  • My chat log of the Trust and Safety meeting held on Tuesday, June 16th, 2026, together with my chat log of that meeting.
  • Pantera’s video of the meeting (embedded at the end of this article) – my thanks to her for providing it.
Table of Contents

Meeting Purpose

  • The Trust and Safety User Group is to provide a forum to discuss topics relating to safety and security in Second Life. However, please note that for matters of privacy and personal safety, the following will not be openly discussed by members of the team:
    • Reports of abuse, together with the outcome of investigations or actions taken in response; specific account information (including terminations, suspensions, warnings, etc.); DCMA or copyright issues; internal processes; ToS interpretations.
  • The meetings:
    • Are held on the 3rd  Tuesday of the month, at 11:00 SLT.
    • Take place at the Linden Estate Services meeting place.
    • Are a mix of Voice and text chat.
  • Dates and times of meetings are recorded in the SL Public Calendar.
  • For descriptions on all SL user groups and their purpose please refer to SL Official User Groups.

Phishing Links

  • Second Life dialogue boxes have sometimes been used to trick users into entering their passwords – if you see something like this – always click Ignore, never enter information personal information.

    Phishing issues have become an increasing problem over the last several years, with people placing URL links into group and IM messages which are inherently untrustworthy (e.g. fake SL Marketplace URLs leading to sites designed trick users into users into revealing personal information, such as passwords, etc.).

  • These links have been made harder to identify as they can be easily disguised as innocuous text links which can be easily clicked (tip: hover the mouse over the text link to show the actual URL in tooltip format before clicking).
    • A good point of reference for avoiding phishing attempts and what to do if caught by one has been written by Pantera Pólnocy on the Firestorm wiki.
  • Steps have been taken at various times to try to reduce the risk of such exposure via routine warnings issued by LL, through the implementation of the SL eye-in-hand logo appearing next to official URL links (those to https://xxxx.secondlife.com, where xxxx might be something like marketplace), which has also bee adopted by Firestorm, although this particular approach is not foolproof.
    • Firestorm 7.2.4 has also introduced  a “URL unmasking” option for added safety.
  • LL are aware of the concerns and are looking to implement further protections of their own against such attacks.
  • However, there is a duty of care among users to exercise common sense as well. For example, where the URL is fully exposed, checks that it is valid. for example:
  • Capabilities such as providing Group owners / moderators to whitelist “allowed” links, etc., have been requested and are being considered.

Multi-Factor Authentication

  • Multi-Factor Authentication (MFA) remains the preferred way to protect a Second Life account.
  • There have been multiple requests for LL to improve MFA, including a means to use it via er-mail, plus ability to recover without requiring a support ticket to be filed.
  • Additional options for MFA are being discussed by Trust and Safety (including automated recovery), but no specific updates or new capabilities had reached a point where they are ready for discussion with users.
Under Construction – the Trust and Safety in-world offices, which will be home to information on matters of trust and safety and governance in Second Life

General Discussion

  • General harassment / abuse using alt accounts:
    • Questions were asked in both general terms and with specifics on the use of multiple accounts to harass / abuse others.
    • As per the guidelines for the meeting, specific cases were not open to discussion.
    • However, Alabaster Linden (Trust and Safety team supervisor) did confirm there are specific bad actors who routinely appear within Abuse Reports, and there are discussions going on internally within the team as to how:
      • A more proactive approach can be taken with regards to instances of harassment at places like welcome hubs to prevent general harassment.
      • A more rapid response can be given to cases of repeat harassment.
    • With regards to the latter, Alabaster Linden also indicated that there is work going on in the background that will hopefully make it easier to manage / reduce the impact of repeat harassment via identified individuals.
    • It was also reiterated that all issues of harassment  / abuse should be filed with LL as Abuse Reports (see my Abuse Reports tutorial, if required).
  • Abuse Reports:
    • Trust and Safety receive around 350-400 abuse reports a day.
    • All reports:
      • Do get reviewed, but obviously, and wherever possible, high-priority items (e.g. immediate cases of harassment or griefing) tend to get the most immediate treatment.
      • Are investigated and are not handed off for automated processing via AI tools or similar.
    • Unfortunately, sometimes it can take time for some issues to be addressed (e.g. land encroachment on Mainland).
    • Abuse Reports can be submitted from any viewer, use of the official viewer is not required.
    • Abuse reports do not have to be filled out in full, but should contain as much pertinent information as possible.
    • Again, please refer to my Abuse Reports tutorial (written in consultation with the Governance Team – as it used to be called).
  • Data gathering:
    • There have been recent concerns about the use of bots for data-gathering in Second Life, particularly since the BonnieBots were completely banned.
    • These concerns related to legitimate use of such bots for gathering non-intrusive information (e.g. such as with Grid Survey, or gathering region data which can be used in the production of heightmap / 3D renderings of regions, etc), and have been passed from user group to user group.
    • As such, guidelines are being sought as to what is / is not regarded as a legitimate use of bots for data gathering and (on a more technical level) whether some data on regions can be made available less intrusively than via the use of bots.
    • The second part of this question is something that requires more internal discussion at LL.
    • The first part of the question is difficult to answer, as some are more tolerant of bot use than others.
    • It was suggested that the issue is more comprehensively written-up in a support ticket (or similar), outlining things like data usage, concerns, what is being sought, etc., so there can be a more direct conversation on the matter, rather than it being passed from user group to user group.
    • Alabaster Linden also offered to go through the various policies provided by the Lab on the use of bots, etc., and see if there is something specific that can be published by way of a blog post as a part of the promised outreach by the Trust and Safety team to help clarify matters.
  • A question was asked on what is allowed within region maturity ratings – the clearest answer is via the Maturity Ratings guide. There is also the Adult Content FAQ.
  • The last 15-20 minutes of the meeting are general conversation.

Next Meeting

2026 SL viewer release summaries week #24

Logos representative only and should not be seen as an endorsement / preference / recommendation

Updates from the week through to Sunday, June 7th, 2026

This summary is generally published every Monday, and is a list of SL viewer / client releases (official and TPV) made during the previous week. When reading it, please note:

  • It is based on my Current Viewer Releases Page, a list of all Second Life viewers and clients that are in popular use (and of which I am aware), and which are recognised as adhering to the TPV Policy.
  • This page includes comprehensive links to download pages, blog notes, release notes, etc., as well as links to any / all reviews of specific viewers / clients made within this blog.
  • By its nature, this summary presented here will always be in arrears, please refer to the Current Viewer Release Page for more up-to-date information.
  • Outside of the Official viewer, and as a rule, alpha / beta / nightly or release candidate viewer builds are not included; although on occasions, exceptions might be made.

Official LL Viewers

  • Default viewer  – 26.2.0.25386466510, May 19 -“flat” UI and font update – No change.
  • Second Life Lua Editor Alpha viewer 6.1.0.23768336784, April 29 – No change.

LL Viewer Resources

Third-party Viewers

V7-style

  • Kirstens Viewer S24(7) Build 3470 (RC-2) – June 14- release notes.

V1-style

  • Cool VL viewer Stable: 1.32.4.33; Experimental 1.32.5.3:  June 13 – release notes.

Mobile / Other Clients

  • No updates.

Additional TPV Resources

Related Links