2026 week #21: SL CCUG meeting summary

Hippotropolis Campsite: venue for CCUG meetings
The following notes were taken from:

  • My chat log and audio recording  of the Content Creation User Group (CCUG) meeting of Thursday, May 21st, 2026.
  • Please note that this is not a full transcript of either meeting but a summary of key topics.
Table of Contents

Meeting Purpose

  • The CCUG meeting is for discussion of work related to content creation in Second Life, including current and upcoming LL projects, and encompasses requests or comments from the community, together with related viewer development work.
    • This meeting is generally held on alternate Thursdays at Hippotropolis and is held in a mix of Voice and text chat.
  • Dates and times of meetings are recorded in the SL Public Calendar.

Official Viewer Status

Viewer Notes

  • 26.2.0 is now release, per the above. The code has also been merged into all viewers currently in development (such as the Lua Editor) with the exception of the Graphics Care Package (GCP) viewer.
  • Viewer 26.3.0 is the performance improvements viewer, intended to be the next release viewer and which is currently awaiting being issued as an alpha or RC viewer. This viewer:
    • Includes async inventory loading, which should further help with loading very large inventories; together with new texture streaming updates which should help those on SL minimum specification computers with constrained VRAM.
    • Is viewer is reported as providing good performance across a range of systems and scenarios.
  • As a part of the texture streaming updates mentioned above:
    • The viewer will not have: “a proper” texture quality setting (Low to Ultra) or the current LOD resolution drop-down.
    • The viewer will have a new texture resolution drop-down, which is more aggressive on its Low setting to optimise the use of VRAM on low-specification client systems; a Medium setting also doing more lower-resolution loading for textures at a distance from the camera (but high resolutions for those close-up); a High setting with resolutions slightly below their current levels; and an “Ultra” option that pretty much matches the current setting.
    • The viewer will also have a new (around 5 metre) “camera bubble” that follows the camera round and tries to load high resolution textures as best the client computer can manage
  • Lua Editor viewer:
    • There are “a lot of asterisks around” this viewer, both in terms of client-side work and server-side work.
    • This viewer may end up with numerous flags within it which can be toggled on / off depending on the status of server-side Lua support.
    • The availability of an official Linux remains tied to this viewer.
  • The Graphics Care Package Viewer (GCP) is effectively “on hold” as work continues on other viewers. However, when it does surface, it will likely include (but not necessarily be limited to) the following:
    • EEP post-processing settings, easing the work of setting-up EEP environments.
    • PBR specular support.
    • Updated and more performant Screen Space Reflections (SSR), including the ability to adjust SSR rendering to better suit the capabilities of the client computer (e.g. cranked right up on a very capable modern computer & GPU, or dialled down so it doesn’t choke older hardware).

General Discussions

  • It was asked if PBR (glTF) lighting is coming soon. Geenz noted that this requires server-side work, notably around the messaging service between the simulator and the viewer. Such work would need to be implemented before LL can fully commit to having largely glTF-compliant lighting. So, not in the immediate future.
  • A question was asked about artefacts occurring in varying levels when a gradient (slope) is applied in the construction of metallic materials, and whether anything was being done to correct this.
    • The question was related to gradients in normal maps, but was not total clear (i.e. was the gradient part of the normal map, or something added latter?). As such a canny report was requested on it.
    • There is a known issue with gradients on the diffuse map, and this is being addressed with the GCP viewer.
  • A request was made for PBR emissive map textures to load as the colour #000000 (up the receipt of the first discard level), as the current value – colour #808080 -, which  causes objects that use emissive to glow while they load – see this issue / Github).
    • Geenz Linden noted this could be so modified, but it would then cut across some of the texture loading work that has been going into the upcoming performance improvements viewer (26.3)
    • As such any change is unlikely to be implemented as a part of that viewer.
  • With the BonnieBots data collection system now banned from SL, a request was made for clarity on what is / is not permissible in gathering data from the grid, as there are a number of valid projects that require the use of specific data gathered from the grid via bots (e.g. in obtaining terrain heightmap data for use in producing 3D terrain maps). Geenz indicated:
    • He would try to get some clarity on this from senior management.
    • That including things like heightmap data into the map system is something the Lab is looking at, so as to make requesting this kind of data easier for those using it.
    • That additionally, LL is considering the use of things like object imposters and mesh proxies where applicable – but there is nothing solid to report on any of this at the moment.
  • It was asked if there are any further updates being planned for the avatar skeleton / avatar bones / blend shapes. Short answer: no; any work on the avatar / avatar skeleton would need to be relatively in-depth due to the risks of content breakage, etc., and so is something LL do not want to take on at present.
  • A question was asked about LL’s strategy for on-boarding and retaining new users. As previously noted in these summaries (and others), LL is not pursuing any single goal for this; there are several inter-related strategies (such as the one-click install on the viewer – making it easier to obtain; & the upcoming graphics improvements – which should make running SL a smoother, more predictable experience).
  • The subject of VR support was raised. The feedback from Geenz was that VR poses significant issues for SL, particularly in the area of being compelling enough to people already using VR headsets. For example:
    • Implementing a means by which people can simply put on a VR headset and look around SL or even move around with their avatar is not technically that complex. However, neither of these approaches would necessarily be compelling to people coming into SL who are familiar with using VR on other platforms.
    • By contrast, making SL interactive in a manner that is compelling to existing users of VR – e.g. being able to engage with, move, etc., in-world objects through hand  arm / body movements and to have things like full facial tracking and representation and having all of that packaged and streamed to everyone else in a region – is a considerably more complex task, potentially touching on multiple areas of the platform. As such it is not actually something LL is directly focused on.
  • The above led to a broader discussion at the end of the meeting on the Lab’s discontinued Puppetry project, its application in a possible VR project, together with alternate approaches, matters of IK, etc., all of which came down (again) to the view that providing a “good” and scalable VR solution in SL requires working on multiple moving parts / would have lengthy lead-times, and so is not something LL  wishes to commit to in the near-term  .

Next Meeting

2026 week #20: SL Open Source (TPVD) meeting summary

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, May 15th, 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  – One-Click Installer – 26.1.1.23806384790 – April 10 – No change.
  • Second Life Release Candidate (RC) viewer: Flat UI – 26.2.0.25386466510, May 15 -“flat” UI and font update – NEW.
  • Second Life Project Viewers – Lua Editor Alpha viewer 6.1.0.23768336784, April 29..

26.2.0 – “Flat UI”

  • A new beta RC was issued on May 14th – see the list above for details.
  • Unless a significant blocker arises, this viewer is likely to be promoted in week #21 (commencing Monday, May 18th, 2026).

26.3.0 – Performance Improvements +

  • 26.3 is still in progress. The new texture streaming updates should be merged already.
  • Work is continuing on getting the async inventory updates included.
  • Geenz Linden is working to get the new material and texture batching work in a good state for it as well.
  • A beta /RC viewer should be appearing on the Alternate Viewers page “soon”.

26.3.1 Maintenance Update

  • The second of the maintenance viewer updates – bug fixes, etc., – is now in preparation.
  • Expect to see this appearing on the Alternate Viewers page “soon” as well.

Graphics Care Package Viewer

  • This is somewhat “on hold” at present, but work will hopefully resume in the near future, as there are a number of bug reports stacking up.
  • There is a reported mirror breakage within the GCP viewer.

Linux Support

  • Linux support in the official viewer is to return with the Lua viewer.
  • LL is targeting the more common Linux systems for support.
  • There is a noted issue with Linux systems without PulseAudio crashing WebRTC versions of the viewer. It has been requested that the WebRTC SDK is fixed to correct this issue, or to provide fallback code PulseAudio to ALSA.
  • It was noted that is a patch or PR was supplied to address this issue, LL would consider it, but LL currently doesn’t have the internal resources to implement a fix themselves.

WebRTC Update

  • As noted in recent user group meeting summaries, WebRTC is now grid-wide and Vivox is effectively retired for Voice. So those using voice on a Vivox-only viewer will now need to update to a WebRTC-capable viewer.
  • WebRTC updates will continue as required, and deployments are carried out separa6tely to the week grind simulator deployment / restarts.
    • Viewers running the latest client-end of WebRTC should not be affected by this, as they they will disconnect from one voice server in the cluster ahead of it going down for update, and automatically reconnect to an operating server in the cluster.
  • In terms of updates, currently the WebRTC team is updating the 3p-webrtc-build branch, and is hoping to look at a code contribution that will enable them to support more recent versions of WebRTC.
  • A patch has also been forwarded to the team to deal with a Linux viewer freeze at shutdown in WebRTC. This also has yet to be looked at.
  • No decision has been taken as to any new capabilities will be added to WebRTC going forward, although voce-to-text transcription (with the potential for multi-language support) remains on the list.
    • There is a lot to be decided on the transcription front: addressing privacy-related concerns, how it is enabled/disabled for people, UX elements, etc.

General Discussion

  • LL is retiring the use of the Opire bounty platform for viewer development code bounties.
    • The major reason for this is that it has led to a spate of bot-generated submissions, many of which are not related to any of bounties, causing headaches in trying to identify valid bounty code submissions.
    • The bounty programme is being re-thought rather than discontinued, and further updates on changes to the bounty programme will be made public once they have been agreed and are available.
  • A discussion on an approach to mirrors for Linden Water, including:
    • A suggestion that 512×512 mirrors could be used to achieve the required results with less VRAM usage.
    • Geenz Linden’s view that mirror probes are currently exposed as a texture array, which needs to be of uniform size, unless bindless, which doesn’t work for Mac OS (until LL moves to a more modern API such as Metal Vulkan). However, he is considering making an exception to the need for the uniform size requirement for a special Water probe type, with its own sampler – although a problem here is the viewer is close to the limit of samplers for Mac OS.
  • Requests have been made to update the official support for CEF to a more recent version. There is an internal project to update CEF / Dullahan within the official viewer.

Next Meeting

2026 week #19: SL CCUG meeting summary

Hippotropolis Campsite: venue for CCUG meetings
The following notes were taken from:

  • My chat log and audio recording  of the Content Creation User Group (CCUG) meeting of Thursday, May 7th, 2026.
  • Please note that this is not a full transcript of either meeting but a summary of key topics.
Table of Contents

 

Meeting Purpose

  • The CCUG meeting is for discussion of work related to content creation in Second Life, including current and upcoming LL projects, and encompasses requests or comments from the community, together with related viewer development work.
    • This meeting is generally held on alternate Thursdays at Hippotropolis and is held in a mix of Voice and text chat.
  • Dates and times of meetings are recorded in the SL Public Calendar.

Official Viewer Status

  • Default viewer  – One-Click Installer = 26.1.1.23806384790 – April 10 – No change.
  • Second Life Release Candidate (RC) viewer: Flat UI – 26.2.0.25021396775, April 29 -“flat” UI and font update.
  • Second Life Lua Editor Alpha viewer 6.1.0.23768336784, April 29.

Viewer Notes

Viewer 2026.02

  • 26.02 is enjoying low crash rates, confirming its status as the next viewer in line for promotion to release status.
  • There will likely be another RC update to this viewer prior to its promotion, which will include some “small, small” changes and fixes (e.g. making bold text easier to see, correcting some text overruns in some floaters, and correcting an extended CEF load time on the viewer splash screen).

Viewer 2026.03

  • This viewer is now described as “following hot on the heels of 26.02”, although it has yet to appear as either an alpha/project viewer or a beta/RC viewer.

Graphics Care Package vs. Lua Support Viewer

  • No firm decision as to which of these viewers is liable to progress to release status first.
    • The Lua viewer would appear to have the advantage given it is currently going through alpha/project viewer evolutions to move towards a beta/RC version, whereas the GCP viewer has yet for officially see the light of day.
    • However, the Lua viewer is dependent on the development of Lua back-end support and simulator updates, plus it is also the viewer being used to re-introduce Linux into the mix of official viewers (with limited support), and both of these might slow the viewer’s promotion to RC and then release status.

WebRTC Update

  • The May 5th grid-wide deployment of WebRTC went ahead as planned, so Vivox is no longer the Voice service across SL. WebRTC is.
  • The deployment apparently went well and there have been few reports of issues.
  • Moving forward, the focus will now be on fixes and updates (e.g. open chat voice attenuation) and general clean-up and the removal of unwanted code.
  • Once this work has been completed, attention will be turned more towards adding new features the WebRTC.
    • Voice-to-text transcription has been requested as one of these new features (and has been experimented with inside the La, including with multiple languages), however, no decision has yet been made as to WebRTC new features or their scheduling.
    • It was also requested to have the moderation tools for Voice made accessible to scripts per this feature request.

General Discussions

  • There are reports of what might be a bug which is causing some avatars to appear to have a 1,000,000 complexity number, when they are far below this. At the time of writing these nots it is unclear if a Canny bug report has been filed on this or not, or how widespread the issue might be.
  • A request was made for expanding SL material assets so they can be used to *completely* set an object’s material? So a BP tab in the material as well (e.g. the ability to drag and drop Blinn-Phong materials into a PBR asset alongside of the PBR materials, so have a complete package with the BP materials available for fallback purposes).
    • There are no specific plans for this. However, as Geenz linden has previously mentioned in recent meetings, there are plans in hand to add specular materials to PBR.
  • Will the terrain painting project be revived? Unlikely at this point is time; performance issues are the current priority and after that, there is more general PBR work to be completed. As such, the terrain painting work remains frozen.

Next Meeting

2026 week #17: SL CCUG meeting summary

Hippotropolis Campsite: venue for CCUG meetings
The following notes were taken from:

  • My chat log and audio recording  of the Content Creation User Group (CCUG) meeting of Thursday, April 23rd, 2026.
  • Please note that this is not a full transcript of either meeting but a summary of key topics.
Table of Contents

 

Meeting Purpose

  • The CCUG meeting is for discussion of work related to content creation in Second Life, including current and upcoming LL projects, and encompasses requests or comments from the community, together with related viewer development work.
    • This meeting is generally held on alternate Thursdays at Hippotropolis and is held in a mix of Voice and text chat.
  • Dates and times of meetings are recorded in the SL Public Calendar.

Official Viewer Status

  • Default viewer  – One-Click Installer = 26.1.1.23806384790 – April 10 – No change.
  • Second Life Release Candidate (RC) viewer: Flat UI – 26.2.0.24254827122, April 15 -“flat” UI and font update.
  • Second Life Lua Editor Alpha viewer 26.1.0.21525310258, February 12.

Viewer Notes

Viewer 2026.02

  • 2026.02 remains the current Release Candidate viewer (next in line for promotion to release status).
  • This viewer will likely have a further RC update prior to any promotion. This update should result in much sharper text rendering within the UI.

Viewer 2026.03

  • LL are working on implementing “whatever performance wins that we can”.
  • This includes “batching” changes – that is, taking multiple objects within a scene and rendering them in a single pass, rather than multiple passes.
    • This work was initially undertaken for what is called the “simple draw pool”, which had batching logic added some time ago, but the work was never extended to the Blinn-Phong or PBR draw pools, and this is now being done.
    • The hope is that this change should help lower specification computers render scenes more comfortably. 

General Viewer Notes

  • Work is currently stalled on the Graphics Care Package (GCP) viewer given the focus on performance improvements for 2026.03. However, work should resume on the graphic improvements and updates for this viewer soon.
  • Given the above, it is still anticipated that the Lua Editor viewer (which is currently available as a project viewer) will go to RC status and then release ahead of the GCP viewer.

WebRTC Deployment

  • The current deployment of WebRTC has hit a few bumps, but the Lab is hopefully the deployment will be completed in “the next two weeks”, and certainly before SL23B.
  • The lack of voice attenuation over distances less than 60 metres (allowing personal conversations to be heard over a large distance) will likely not be addressed prior to WebRTC deployment is complete, and will be looked at afterwards – although it was also noted that attenuation under WebRTC will be different to Vivox.

General Discussions

  • Question: will there will be further updates to Animesh, particularly with regards to having to click on them without having to put a transparent prim around them for interactions?
    • Short answer: the need to click is intentional, and currently, there is no work on Animesh any time soon.
  • Question: will the one-click installer process also be applied to alpha and beta/release candidate viewers, or will these have their own install options?
    • LL is looking at “future options to make opting-in to alphas and betas have a lot less friction”, but discussions a re ongoing and not ready to be announced.
    • Alpha and beta/release candidate viewers will retain their own cohorts within github, allowing people who opt to use them from the Alternate Viewers page to continue to be opted-in to updates to those viewers as they are made available.
    • The ability to select and download a viewer from the Alternate Viewers page will continue.
  • Aside from general text chat on matters such as Animesh (between users) and on Fantasy Faire, this was a quiet meeting, and as such was brought to a close after some 30 minutes.

Next Meeting

2026 week #16: SL Open Source (TPVD) meeting summary

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, April 17th, 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  – One-Click Installer = 26.1.1.23806384790 – April 10 – NEW.
  • Second Life Release Candidate (RC) viewer: Flat UI – 26.2.0.24254827122, April 15 -“flat” UI and font update – NEW.
  • Second Life Project Viewers:

26.2.0 – “Flat UI”

  • Now at RC status, per the Above list.
  • More updates to be made to this prior to promotion.
    • LL is working through some font kerning problems that were seemingly made much more obvious with the new font choice.
    • It was also noticed that the official viewer has been rendering fonts ever so slightly different from FS – which kicked off the above investigation.

26.3.0 – Graphics Care Package

  • The is the viewer previously known as the SL Visual Polish (SLVP) viewer.
  • The performance tweak has been ported over, and the team is now looking at additional performance work.
    • Async inventory is being parted out into easier to review chunks.
    • LL is also looking at some CPU and GPU wins overall – Geenz Linden is working on getting texture batching working for the PBR and Blinn-Phong paths. There is potentially more work on these lines, and these will likely be incorporated prior to passing the viewer to QA.

Lua Viewer

  • The Lua Alpha update that it had been hoped would surface around the start of April is now being aimed for some time in week #17.
  • The current lean at the Lab is to move this viewer through to RC status and then release before the 26.3.0 GCP viewer, but no firm decision has been made.
  • Again, this viewer will also be the first new Linux release from LL.
  • As a reminder: LL have officially dropped “SLua” (“SL Lua”) and just going with “Lua”.

WebRTC Deployment

  • The WebRTC deployment is still underway. No firm end-date as yet, although it should now be across all simulator RC channels.
  • Anyone experiencing Voice issues with WebRTC is asked to file a bug report.

General Discussion

  • The vcpkg updates for the viewer build process will not be surfacing until “after Lua at the very least”.
    • Geenz estimates it will likely not emerge until late summer, due to dependencies on work being completed vis. KDU and the removal of the Havok sub-libraries from the viewer.
    • In terms of the latter: VHACD will replace the convex decomposition for mesh upload, and server-generated path-finding mesh will replace the Havok path-finding mesh loaded by the viewer for visualisation.
    • A major reason for removing the Havok sub-licences is the impact they have on TPVs, who have to go through the process of obtaining and signing sub-licence agreements via LL, which complicates the open-source environment.
    • In this respect, if LL had a truly open-source replacement for KDU on the graphics side, they would look to make similar moves there as well.
  • Physics shapes and why and what the viewer can do with them became a topic for conversation at around the half-way point in the meeting, and this continued for around 10 minutes.
  • During the above there was a general discussion on the mesh uploader and clarifying LOD numbers for those coming into mesh creation.
  • A question was asked on interpreting section 8 part of the Unauthorized Uses of Linden Lab’s Trademarks policy – a question perhaps best dealt with via a support Support Ticket.
  • A request was made for TPVs to receive stats reports once more (use, crash rates, etc). Geenz noted in reply:
Some of that is a bit of a black box to us as far as your specific crash rates, as for viewer usage we’re bottlenecked by a single person is responsible for that so it doesn’t always get done. I’ve been hoping to get a more automatic solution for this for a while, but our metrics folks have been booked up with other things for a good bit now.
  • The question was asked about the possibility of viewer-side Lua for building custom UIs to replace some of the HUD systems people use, and whether work on this is still moving forward. Geenz repliedwith:
That’s been on the shelf for a while. Dunno if or when we’re gonna bring that one back – I think what we’d need to really look at bringing that back with a significant amount of interest is gonna be how people would want to use [it]. There’s a lot of criteria that goes into making product level decisions like that, and with the viewer side Lua stuff it was increasingly being looked at something for internal use than something like a content feature.
  • The question was asked if the puppetry project was once and for all “dead”, to which Genenz again replied:
Lots of things were learned from that project, but I wouldn’t say it’s dead necessarily. Just not a priority. There’s a lot of things that would need to happen for puppetry, and I think it’s really increasingly more of a “when we need <x> we’ll work on that part of it” sort of thing. Because like joint streaming is just generally kind of useful, but we don’t have an immediate need for it. But who knows – maybe some day. Hell, if there’s any interest in having a proper poser viewer-side that ticks all of the privacy and consent boxes that might be a potential path. But we’re nowhere near there yet.

Next Meeting

2026 week #14: SL Open Source (TPVD) meeting summary

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, April 3rd, 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  – Legacy search; WebRTC improvements; QoL improvements – 26.1.0.22641522367 – March 12.
  • Release Candidate viewer – one-click installer = 26.1.1.23806384790 – March 31 – NEW.
  • Second Life Project Viewers:

Viewer 2026.01.01 – One-Click Installer / Velopack

  • Now available as a RC viewer – see above.
  • This could be promoted as early as week #15, depending on how it performs (crash rates, etc.), over the next few days..

Other Viewers

  • 2026.02 – “Flat” UI and Splash Screen Refresh – this is due to have an Alpha update issued on April 3rd.
  • The Lua Alpha viewer is also due to have an update issued on April 3rd.
    • Note, LL are now officially dropping “SLua” (“SL Lua”) and just going with “Lua”.
Example of the upcoming flat UI. Via: Geenz Linden / Github #4681/2
  • The viewer formerly known as the Second Life Visual Polish viewer (SLVP) is now known as the Second Life  Second Life Graphics Care Package.
    • The hope is to get that into alpha soon – but only after we get the necessary server work done and get some regions up on ADITI.

WebRTC Deployment

  • The WebRTC deployment has hit a “hiccup”.
  • As a result the deployment has slowed, with WebRTC liable to remain only on the RC server channels (Le Tigre, BlueSteel, Magnum, etc.) and covering about14% of the Main grid until the problem is resolved.
  • Anyone experiencing Voice issues with WebRTC is asked to file a bug report.

General Discussion

  • There is an increasing issue of AI driven pull requests.
    • This appears to be a case of people trying to make claims via the bounty programme for code submissions without actually putting any effort into the work.
    • Commenting on the matter, Geenz Linden noted:
If you’re using LLMs to submit pull requests, that’s not an automatic no. However, blatantly vibe coded submissions, submissions that are effectively taking stuff from other viewers without any kind of attribution or permission and so on, and anything that just generally reads as super low effort just to claim a bounty is likely to be closed without comment in a worst case, or otherwise scrutinized in order to ascertain the individual’s understanding of what that code actually does vs. how much is just prompting to see if they can land something. We don’t want to shut down utilizing AI in people’s processes, but certain things are gonna get PRs shut down or scrutinized more heavily. So please keep this in mind.
    • This called into question the value of the bounty programme, with the fair point being made that TPV developers have spent years developing code for their viewers and submitting much of it to LL without any thought of reward other than improving people’s SL experience.
    • Geenz further noted the the bounty programme is due to get reviewed “sooner [rather]than later”, although it is likely “some form” of it will be kept, as it has also led to useful code contributions – such as those for getting the Linux viewer back into the frame (due to surface with the Lua viewer) and the viewer vcpkg work.
    • The suggestion was made that a contract programme – whereby an external coder is contracted to produce work – might be more beneficial than the current bounty programme. Again, this was pretty much the case for Linux and vcpkg.
    • A further suggestion was made to offer general bug / feature request bounties in L$ only – potentially making them less attractive to those trying to bend the system and earn US $ using AI LLMs.
  • The question was asked if Leviathan Linden’s work on server-viewer messaging would be surfacing in one (or an) Alpha viewer soon – the reply was that discussions on where and when to place this work are still ongoing, in order to ensure the viewer work and server work appear pretty much together.
  • Suzanna’s excellent write-up on the latest Lua release gained a further shout-out. On this (again):
    • This release will be deployed to Aditi (the Beta grid) first for testing.
    • It requires all Lua scripts to be recompiled in order to keep working.
  • Tis last 10 minutes of the meeting was spent discussion whether “SLua” should be retained as the name for the Lua project, or if “Lua” was better (certainly more widely recognised) given it is an implementation of Luau.

Next Meeting