There are thousands and thousands of active regions and thousands of users (https://opensimworld.com/). It's not millions, but it s the best self-hosted virtual world ecosystem.
Is a "viewer" a Second Life term for "game client"? And is Firestorm a particular FOSS client for the game?
If so, that's really interesting... like you can access the same shared Second Life world but through a custom client? Does it reuse existing game assets or you free to reinterpret character models, textures, effects, etc.?
Quick overview:
Second Life / Open Simulator worlds are divided into "regions". Each region is 256m on a side on Second Life, and can be other sizes in Open Simulator. The world is about the size of Los Angeles. The viewer starts out by talking to a login server for a grid, which authorizes it to connect to a region. The viewer then talks to the region. There are short messages over UDP, and some bigger stuff over HTTPS.
Once a viewer is talking to a region, it asks the region server about adjacent regions. The viewer can then talk to a few adjacent regions, too, showing the user a big, seamless world. As the user moves around the world, connections are made to new regions, and connections to regions out of range are dropped. This is how the world scales. There are about 27,500 live regions today, each with its own simulator program, always on even if nobody is using it. Each simulator program takes about one CPU and under 4GB on a server. Second Life is currently hosted on AWS, with dedicated servers. This scales well; the world could be scaled up substantially if there was demand.
The always on feature runs up costs, but the business model is that users rent land. So costs and revenue stay in balance. Regions really are always on - trains run through regions where no one is around, for example. This architecture made more sense when Second Life had their own servers in a co-location facility.
The region servers talk to their direct neighbors. This allows movement across region boundaries. If a region goes down or is restarted, the viewer will show a water-filled hole with steep sides where the region is supposed to be. So the overall system is fault-tolerant.
Content is stored on asset servers, separate from the region servers. These are ordinary AWS web servers, front-ended by Akamai caches. Content includes textures (images in JPEG 2000 format, which is a pain to decompress fast), meshes (a documented but nonstandard format), sounds, etc. There's petabytes of content. The region servers tell the viewers what hashes (UUIDs) to ask for, the viewers get the content from the servers with ordinary HTTPS requests, and all this is assembled in the viewer into 3D images for the user.
Any user can upload new content. Uploading an image costs about US$0.05. Uploading a 3D model might cost $0.50. This is a one-time charge. As long as someone, somewhere, is using that content, it's kept on the servers. There's a garbage collection run every month or so.
Voice is outsourced to Vivox. (Vivox has problems. Not recommended for new designs.)
Coming soon is "puppetry". Second Life is now testing full body and face tracking, for those who want their avatars to run more than canned animations. This involves an entirely new data path by which viewers talk to other nearby viewers via a server that just forwards data. Second Life is getting VRchat features.
So that's what a viewer is. And that's what the architecture of a big metaverse looks like.
If they support VR now I might give it another look.
The idea behind "puppetry" is that not everyone will use it, but performers and people who want to be looked at will. The audience doesn't have to wear trackers. I'm looking forward to live theater in Second Life.
I've been to puppetry virtual meetings in Second Life. Someone rigged for full body tracking and with a good microphone dominates the meeting without effort.
Assets are downloaded from the servers. Users can upload and optionally gift / sell their own.
Assets are downloaded by the viewer from the SL servers.
Viewers are "game clients" yes. The viewer is intended to mostly be a dumb receiver. The server does most lifting.
Firestorm is a fork of the official viewer. It forked about the time I played SL but seems to have grown into it's own these days.
I had no idea this existed, and have been looking for it [conceptually] for years. Thanks!
At the time most people thought the open ecosystem of interconnected endpoints was destined to dominate the global information storage, because smtp had outcompeted proprietary messaging systems, and the url was looking to displace localized hypertext systems and the open web looked unstoppable.
That was before the reactionary trend where gmail overtook the smtp momentum and actors such as Facebook expanded their walled gardens by absorbing or straight up acquiring forums and smaller players. Facebook wasn't unique in their business model of locking up as much of the world's information as possible into their platform, but they were certainly the most successful.
That made it the more telling when Facebook made their pivot into assisted reality public, starting with naming their walled garden the metaverse, a term taken right out of the most visionary futurists of yesteryear! Let's see if the time has come for the pendulum to swing back. It'd certainly be most fitting if the term itself gave new life to the open interconnected ecosystems to show us again what's possible with permissionless innovation.
You might want to take a look at the Matrix.org approach to this: https://thirdroom.io/
Fun fact: Apparently Matrix (the protocol itself) was made after a brainstorm session on how to create an improved and decentralized / federated Second Life game :)
The Firestorm viewer sources are at "https://vcs.firestormviewer.org/". It's a major fork.
Technical documentation of the client-server protocol is at "https://wiki.secondlife.com/" It's out of date, but it helps.
The real progress is that the build procedure has been cleaned up. It used to require ancient versions of Visual Studio on Windows. Firestorm can be built on Linux. I've built it and submitted patches that went in.
This is just the client side. The server is proprietary. But there's a compatible server, Open Simulator. It's not a clone; it's in C#, while the original is in C++.
There are meetings for third party viewer developers. Both inside Second Life, and on OSGrid, which is a third party grid of simulators. That really is the metaverse - a federated system of 3D worlds. It's sluggish, because most of the people running regions don't have enough server power. Think Mastodon for 3D.
I'm been writing a new client in safe Rust for the last two years. I'm trying to see how much can be done in parallel. The viewer isn't ready for public use yet. I've posted videos made with it.