Linden Lab has announced changes to the standalone Gaeta 1 continent, and the Zindra adult continent. Via the SL Wiki
On Wednesday April 15th, 2026, Linden Lab announced some significant Mainland changes involving the Gaeta 1 continent and the Adult continent of Zindra.
The Changes
Gaeta 1
A transitioning of all current residents from Gaeta 1 to other Mainland continents. This is to start in April 2026, with an aim to complete by the end of 2026.
This transitioning will be handled carefully, with personalised outreach to residents on Gaeta 1 by members of the Lab’s staff.
Land holders on Gaeta 1 will be offered size-for-size parcel replacements, and LL will work with them to find a comparable parcel that suits their needs and preferences.
No region on Gaeta will be retired without due consultation with the land holders currently based on it. Time will be given for all land holders to plan, examine options and discuss matters with the Lab as the process commences and progresses over time.
The transition is expected to unfold “over many months”.
Once complete, Gaeta 1 will go offline as a continent.
Zindra
Zindra will see an expansion of approximately 90 regions.
This expansion will be rolled-out alongside the transitioning of Gaeta 1 – but does not mean Gaeta 1 land holders “must” accept parcels within Zindra.
However, if moving to Zindra is seen as preferable by any Gaeta 1 land holder, they will be given priority access to the new Zindra regions.
These new Zindra regions will include scenic waterfront, extended road networks, coastal water passages, and additional development that helps complete and enhance the Zindra continent.
Why is this being done?
To quote from the official blog post:
Adult mainland continues to operate at very high occupancy and shows consistent demand. At the same time, some General and Moderate mainland areas, including Gaeta 1, have seen lower overall use over time. Instead of expanding the total size of mainland, we are adjusting existing capacity to better reflect where Residents are most active today.
This change applies only to the unconnected continent named Gaeta 1. IT IS NOT PART OF A BROADER MAINLAND CLOSURE, and there are no changes to content policy connected to this announcement.
– From the Lab’s official blog post on the Gaeta 1 and Zindra changes
Town Hall Meeting
As a part of the consultation process and to answer initial questions / hear feedback on these changes, Linden Lab will be holding an in-World Town Hall meeting on Monday, April 20th, 2026, commencing at 11:00 SLT. The Town Hall meeting area can be accessed using the following SLurls:
Pususaari – Where spring feels gentle, February 2026 – blog post
The following notes were taken from the Tuesday, April 14th, 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
No SLS Main channel deployments for the week, but the channel was restarted.
The WebRTC deployment will be expanded to Magnum, finally completing its deployment across all RC channels.
The next simulator update – Loganberry – will include (among other thinks) the performance improvement work Leviathan has been working on and the fix for avatars remaining a cloud Leviathan has also developed (which addresses causes of clouding on the simulator – viewer-side clouding is not touched).
In Brief
Leviathan Linden:
Has been ” removing use of Tilia (payments system) from our code.” Exactly what this means is unclear, given the use of the Tilia wallet and close ties between LL and Thunes, Tilla’s owners.
He has also spent a little bit of time trying to incorporate some suggested code changes for the game_controller code, as suggested by a user, but upon testing he found something isn’t working right, so some investigation is required.
Monty Linden has been working with the Firestorm team on some of the TeleportFinish failure modes. One set of fixes, involving viewers simply walking away from the HTTP connection, is getting improvements so one subset of viewer-side TP/RC issues will be improved.
Kyle Linden noted that the SL 26.2 Flat UI Beta (releasing soon) also has a viewer-side TP disconnect fix.
Harold Linden (SLua):
There are a number of crash fixes and minor correctness fixes out on the Aditi (the beta grid), which should be coming to the Lua region on the main grid “soonish”.
As Rider mentioned, the scripting language definitions are going to be accessible to the viewer now, so you can always pull down the correct type definitions for whatever region you’re currently on.
Harold is additionally generalising his work for making llSetPrimitiveParams less annoying to use. Essentially it’ll be a fluent API where you can batch up prim params commands as you would do currently, but you do it through function calls rather than manually adding a bunch of stuff to a list.
Kyle Linden indicated there will be a “big push” on Lua documentation in the upcoming week(s).
General Discussion
Please refer to the video below as well.
It has been again reported that large linksets of prims or meshes that have alpha scripting (LSL and / or Lua) against Blinn Phong materials (apparently PBR is reported as working as expected) for certain parts of that linkset are failing to change alpha state or are slow to change. Copies of suitable linksets / a formal bug report on this were requested.
This sparked something of a discussion on probable causes, length of time the bug has been around, means to repo, etc., running through the mid-point of the meeting through to pretty much the end.
A WebRTC question was asked: the current settings seem to be 60m range, no distance attenuation. Is that the only option available?
Response: there should be distance attenuation. The curve is different than Vivox, though. If you’re not experiencing any distance attenuation, bug fixes are required with more details so LL can try to replicate what you’re doing.
Date of Next Meetings
Leviathan Linden: Tuesday, April 21st 2026.
Formal SUG meeting: Tuesday, April 28th, 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 will mark the 23rd anniversary of Second Life opening to public access – and as we’ve all come to expect, the month will mark the start of several weeks of events and celebrations running into July under the umbrella of the Second Life Birthday (SLB) otherwise know for this year as SL23B.
Dates and Theme
This year the SLB festivities will open on Friday, June 18th, 2026 and will run through until Sunday, July 19th, 2026. The theme for 2026 is The Golden Age of Hollywood, which the Lab describes thus:
Think classic cinema, red carpets, vintage glamour, and the magic of the silver screen. While the theme may inspire many builds and performances, exhibits are not required to follow the theme. We encourage you to share what makes your Second Life experience meaningful. Your interests. Your communities. Your creativity.
However, as has been the case over the last several birthday events, exhibitions are not confined to the theme itself, with the Lab additionally noting:
Every year, we celebrate because of the incredible Residents who bring this world to life. The birthday celebrations are an opportunity to showcase what inspires you and what keeps you coming back.
Volunteer Applications
On Tuesday, April 14th, 2026, Linden Lab announced that Volunteer applications have opened and remain so through until Monday, May 18th, 2026. As noted, exhibitor applications are now open. Key requirements for volunteers are noted below – however, for the full list of requirements, please refer the the exhibitor application form, via the link following these notes:
Volunteers are asked to commit to at least two hour shifts at a time, and to note that as SL23B spans 11 days, LL prioritise applicants who can participate across multiple days. Stage Crew are expected to contribute a minimum total of 8 hours.
Training sessions will be provided across multiple times. All volunteers are expected to complete a training session, regardless of whether they have been volunteers at previous Birthday events. Those failing to complete the required training will be removed from the Volunteer group.
These are volunteer positions, and as such, volunteers will not be paid. Additionally, volunteers cannot rez/wear tip jars or solicit for tips.
Stage Crew:
May not act as personal hosts for performers. You may only host if specifically scheduled as a Stage Host under the official guidelines.
Members should report any issues to their Stage Manager first. Stage Managers are responsible for assigning roles, tasks, and timing.
Greeters should report any issues in the Greeter group and a Mole or Coordinator will assist.
Please note: All enquiries about hosting exhibitions, staging performances or volunteering at the event should be directed to Linden Lab, not this blog.
Logos representative only and should not be seen as an endorsement / preference / recommendation
Updates from the week through to Sunday, April 5th, 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.
We see you: Christina Koch looks out of one of the Orion capsule’s windows towards a GoPro camera mounted on one of the four forward-swept solar array wings of the vehicle’s European Service Module (ESM). To her right, she is holding aloft the mission’s zero-gee indicator / mascot, “Rise”. Created by a 3rd grader, “Rise” has a smiley-faced Moon and is wearing a blue-and-green cap representing Earth, all in a homage to the famous Apollo 8 “Earthrise” photo. Credit: NASA
On Wednesday April 1st, 2026, NASA’s Artemis 2 mission launched on a 10-day cruise to the Moon and back (with time initially spent in Earth orbit), carrying a crew of four to test the capabilities and facilities of the Orion Multi-Purpose Crew Vehicle (MPCV). The mission was a key preparatory step to send crews to the surface of the Moon, starting with the flight of Artemis 4, currently targeting a 2028 launch.
In the first part of this 2-part series I covered Artemis 2 from launch to TLI. Here I complete the voyage in summary form.
Whilst marked by a number of on-going space health experiments, video calls to Earth and performing sundry tasks and s few minor fixes, the outward trip from Earth to the Moon was pretty much a claim affair. A 17.5 second mid-course correction manoeuvre was performed automatically by Integrity, the Orion spacecraft, on mission day 5 – which was actually the first to be performed, the initial correction burn having been cancelled due to Integrity being so precisely on course whilst under its own flight control software.
Taken in high Earth orbit, this image shows the European Service Module and its main engine, with the Earth as a backdrop as the motor is test gimballed ahead of the TLI burn to send Integrity to the Moon. Captured by a solar-panel mounted GoPro camera. Credit: NASA
Day five also saw the crew test their dual-purpose Orion Crew Survival System (OCSS) suits – the orange-coloured space suits the crew wore during the Artemis 2. Designed for quick donning, the suits function as a contingency safety system during the crew’s time aboard and Orion spacecraft, providing up to 144 hours of life support in the event of a cabin depressurisation.
Artemis 2 astronaut Christina Koch poses in her custom-made OCSS suit ahead of the Artemis 2 mission. Credit: NASA.
In their second role, the suits are intended to act as water survival suits in the event of an emergency evacuation of an Orion vehicle post-splashdown. In this role, the suits are intentionally coloured “international orange” so as to be more clearly visible in the water – just like survival suits used on ocean-going cargo vessels, oil rigs, deep sea fishing vessels, etc They additionally have inbuilt flotation devices. Each OCSS is custom made to fit an individual astronaut.
Day five also saw a series of discussions with Mission Control on the upcoming loop around the Moon to review lunar surface targets for observation and photography during the flyby and finalise observation techniques.
On flight day 6, Integrity officially entered the influence of the Moon, with lunar gravity now the dominant force in shaping the vehicle’s trajectory. Until now, Integrity had effectively (if slowly) been decelerating, due to the “pull” of Earth’s gravity behind it, effectively cruising at a few thousand kilometres an hour at it approached the Moon. Now, under the Moon’s influence the craft would start to very slowly accelerate, allowing the Moon’s gravity to swing it around the Moon and lob it back towards Earth without any significant engine burns.
In 1968, the crew of Apollo 8, the first humans to fly around the Moon, captured an iconic image of Earth “rising” over the Moon as the Apollo CSM re-emerged from being on the Moon’s far side. On April 6th, 2026, and 57 years later, the crew of Artemis 2 captured this image of a crescent Earth “setting” over the Moon as their Orion spacecraft started its journey around the Moon’s far side. Credit: NASA
Around the Moon
At 23:00 UCT on April 6th, Artemis 2 made its closest approach to the Moon, passing some 6,545 kilometres above the Moon’s far side. Shortly thereafter Integrity reached a distance of 406,771 kilometres from Earth, breaking the record for the furthest any humans had been from Earth and set by the crew of Apollo 13 in 1970. At this point, Integrity officially started its flight back towards Earth.
During the loop around the Moon, Artemis 2 was in communications black-out with Earth due to the bulk of the Moon being between the spacecraft and Earth, effectively blocking all signals. This blackout lasted 40 minutes, and ended with a successful recovery of comms and telemetry at the expected time.
A gif showing the solar eclipse as seen from deep space by Artemis 2. Credit: NASA
Following the comms blackout, the crew of Artemis 2 witnessed a solar eclipse from deep space as the bulk of the Moon came between them and the Sun. This allowed the crew to observe both the eclipse from a unique perspective, and witness a number of “impact flashes” of meteoroids striking the semi-dark lunar surface facing them. The Moon was not fully dark as the Earth was off to one side relative to Integrity, and so was reflecting sunlight back onto one hemisphere of the Moon, bathing it in “Earthlight”.
Also during the flight around the Moon, the crew christened two previously unnamed craters on the Moon. They named one for their spacecraft, Integrity, whilst the second was – in a poignant moment – named Carroll, in honour of Reid Wiseman’s late wife, who passed away from cancer in 2020.
Artemis 2 crew Commander, Reid Wiseman with his late wife, Carroll, after whom the crew named a crater on the Moon.
Between flight day 7 and flight day 9, Orion departed the Moon’s sphere of influence on its free return trajectory towards Earth, once again slowly accelerating. For most of Day 7 the crew were engaged in debriefing calls with Earth, recording their observations, feelings and emotions during their trip around the Moon whilst memories and reactions were still fresh. They also put in a call to astronauts aboard the International Space Station (ISS).
A further planned use of manual control by Wiseman and Pilot Victor Glover on Day 8 was cancelled in order to allow mission managers conduct a data-gathering exercise related to a non-critical helium leak within the Orion’s European Service Module (ESM), so that they might better analyse the issue post-mission. Two final trajectory adjustment burns were carried out on Days 9 and 10, lasting 8 and 9 seconds respectively. Most of Day 9 saw the crew packing and stowing experiments and equipment in readiness for re-entry and splashdown.
Following the course correction burn on Day 10, the ESM was jettisoned, its work done. The reaction control thrusters system (RCS) on Integrity then operated in sequence over 19-seond period, both manoeuvring the capsule away from the ESM and orienting it in readiness foe atmospheric re-entry.
A gif showing solar panel GoPro camera views of Integrity’s crew capsule sparating from the European Service Module in readiness for re-entry. Credit: NASA
EDS: Entry, Descent and Splashdown
Day 10 saw the most critical elements of the mission unfold: atmospheric entry, descent and splashdown. During Artemis 1, and as I’ve covered in numerous Space Sunday pieces, post-recovery, the heat shield showed some disturbing issues. As well as the expected ablation damage to the heat shield, it also showed signed of deep scoring and charring, with relatively large holes apparently seared through the heat shield material.
After extensive analysis, it was determined that an error in the fabrication process for the initial heat shields for Artemis 1 through 3 had resulted in pockets of gas being trapped in the layers of ablative material. Due to the original re-entry profile for Orion, as used on Artemis 1, which saw the vehicle “skip” in and out of the upper atmosphere to reduce its velocity prior to actual re-entry, these gases ended up being super-heated several times, weakening the heat shield’s structure and eventually blowing holes up and out of it as they outgassed.
While the fabrication process for the heat shields was revised to mitigate any issues of gases becoming trapped – Artemis 2, due to time constraints, would have to fly with its original heat shield. To compensate for this, NASA altered the mission’s re-entry profile to be more Apollo-like: a single direct re-entry. Whilst this might increase stresses on the vehicle and crew, it would reduce the time over which any trapped gases in the heat shield might have expand and contract and weaken its overall integrity, thus increasing the risk of failure.
As it turned out, the heat shield (subject to post-flight inspection) did its job in this new re-entry profile and protected Integrity and its crew, all of which descended by parachute post re-entry to splashdown off the coast of California, where a recovery operation overseen by the USS John P. Murtha out of San Diego saw the recovery of both crew and the space vehicle. Following initial medical checks on the Murtha, the four crew were then flown to the mainland for further check-ups, prior to proceeding on to the Johnson Space Centre in Texas to be reunited with families and loved ones.
The Artemis 2 crew at Johnson Space Centre, April 11th, 2026. (l to r): Jeremy Hansen (CSA); Christina Koch (NASA); Victor Glover (NASA) and a triumphant-looking Reid Wiseman (NASA), holding “Rise” the mission’s zero-gravity indicator and mascot. Credit: NASA
Research related to Artemis 2 will continue post flight, and some of it will continue to focus directly on the four crew, comprising functional check-out tests, simulated space walks, exercises, etc., to further gain insight into the human body’s ability to adapt to low gravity operations and work, and its ability to recover from them. As well as this, all four will be a part of a media circus for some time to come. To them, and all those involved in Artemis and Artemis 2 – congratulations.
What Comes Next?
Originally, Artemis 2 was to be followed by the first attempt at landing an Artemis crew on the Moon. However, this idea both spoke to an unwarranted gung-ho attitude on the part of Artemis management at NASA (no crewed pre-testing of the lunar landing system (called the Human Landing System, or HLS) in Earth orbit), and assumed the mission would actually have a lunar landing vehicle (from SpaceX) available to meet its 2027 launch date.
Blue Origin’s Blue Moon Mark 2 HLS (l) and SpaceX Starship HLS – NOT to scale. The Blue Origin vehicle is 16 metres high as benefits a low centre of mass – crew compartment, engines electronics, etc, all at the base of the vehicle, which includes broad-set landing legs for stability. The SpaceX design – 52 metres tall – suffers from a high centre of mass: crew compartment, electronics, batteries, engines all in the upper third of the vehicle, requiring an elevator (single point of failure) to get crews to / from the surface on the Moon, and a comparatively narrow-set landing legs, further increasing vehicle instability when landing on an unprepared surface like the Moon.
In taking over at NASA, Jared Issacman saw the gung-ho approach of Artemis 3 as a step too far, and so – with Congressional and White House approval – determined Artemis 3 should be an Earth-orbiting testy of the HLS vehicle by a crew. Also, in keeping with his predecessor, Sean Duffy, he indicated that SpaceX was no longer the sole provider of the Artemis 3 HLS; but would directly face off against Blue Origin, who had been awarded a HLS contract by order of Congress after NASA changed the scope and rules of the original HLS contract to favour SpaceX.
Given that the SpaceX HLS continues to exist as little more than a few disparate elements (such as the crew elevator – largely developed by NASA) and pretty computer renderings, this move to include Blue Origin – who are actively testing elements of their HLS, Called Blue Moon Mark 2 with NASA astronauts – is a wise one, given the SpaceX CEO appears to believe time frames and delivery dates are purely functions of his ego.
A full scale mock-up of the Blue Origin Blue Moon Mark 2 crew section with airlock undergoing testing for astronaut egress / ingress and the recovery of an incapacitated crew member, using the neutral buoyancy facility at NASA’s Johnson Space Centre. Credit: Blue Origin / NASA
As it is, this year should see Blue Origin fly a Blue Moon “pathfinder” mission to the Moon. This will see a scaled-down version of the Blue Moon cargo lander fly a payload from NASA to the Moon, allowing it to test the flight control, navigation, and data communications systems and avionics which will all be part of both the Blue Moon Mark 1 cargo vehicle and Blue Moon Mark 2 HLS. If successful, the mission could put Blue Origin in a strong position to provide the HLS vehicle for both Artemis 4 and Artemis 5.
However, even if one (or both) HLS vehicles get successfully tested in Earth orbit in 2027, it does not mean NASA will be ready to send astronauts to the lunar surface – there is another hurdle to overcome, one entirely of NASA’s own making: cryogenic orbital refuelling.
To explain: while techniques for transferring hypergolic propellants between space craft has long been available (the ISS, for example, routinely takes on propellants for its manoeuvring thrusters), cryogenic propellant transfer in space is entirely new. It’s not been used before simply because cryogenic propellants are not exactly stable. For one thing, they don’t like heat (and in space, in direct sunlight it s very hot). Heat makes them revert to a gaseous state, expanding their volume. This puts greater and greater pressure on the tanks holding them, such that if the gas isn’t vented to some degree, everything is going to quickly vanish in a brilliant (if silent – in space, no-one can here you go pop!) explosion.
Renderings like this showing one vehicle (in this case a SpaceX Starship (uppermost) transferring propellants to another may look good, but the fact is, such transfers have never been tried in space and are far more complex than hypergolic propellant transfer and storage. Credit: SpaceX
Cryogenic propellants are also heavy in their liquid state, making them somethings of a deadweight if you’re attempting to lift them to orbit rather than burning them as a means to get to orbit. This latter point means that in order just to get to Earth orbit or to the Moon, the SpaceX HLS and Blue Moon Mark 2 (respectively) must launch without the fuel needed to get to the Moon, land a crew and get them back to lunar orbit. Thus, the fuel must be ferried to them post launch.
For Blue Origin, this means launching a Blue Moon HLS to lunar orbit, but without the propellants it needs to operate between lunar orbit and the Moon’s surface. Instead, these must be delivered by a “tanker” craft called the Cislunar Transporter, being developed by Lockheed Martin. But here’s the catch: the Cislunar Transporter has to be launched without the propellants it needs to get to the Moon or those it must transfer to the waiting HLS. So, once in orbit it also has to be “refuelled” by at least two Blue Origin New Glenn rockets.
And if that sounds complicated – SpaceX much do much the same with their HLS, which will launch with only sufficient propellants needed to get to Earth orbit. After this it must either make up to sixteen individual dockings with Starship “tankers” to take on the propellants it needs to reach the Moon and perform its duties there, or it must rendezvous with a (also yet to be built) “orbital fuel depot” previously filled with the propellants it needs by multiple Starship “tanker” flights.
And this is where boil-off comes into play: all of these approaches will result in large volumes of cryogenic propellants spending a lot of time in direct sunlight, turning back to a gaseous state, expanding and requiring venting to prevent their storage tanks rupturing. So techniques and entirely new technologies need to be developed and tested in order to reduce the overall boil-off issues lest more time is spent on “tank top-up” missions than in actually sending humans to the Moon. Further, no-one knows if large volumes of cryogenic propellants can easily be pumped from one vehicle to another in microgravity.
Thus, even though Artemis 2 has been a huge success and NASA is turning its attention to Artemis 3, the programme as a whole still has some hefty hurdles to clear before it is close to being ready to send humans back to the surface of the Moon, and at the current rate of progress, I cannot see all those hurdles being cleared by “early 2028 – less than 2 years from now – when Artemis4 is supposed to launch on its crewed mission to the lunar surface.
Logos representative only and should not be seen as an endorsement / preference / recommendation
Updates from the week through to Sunday, April 5th, 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 – Legacy search; WebRTC improvements; QoL improvements – 26.1.0.22641522367 – March 12 – no change.