Soapstone and Horizon Worlds: a case study in community continuity

A social venue can remain technically accessible while the activity that gives it meaning becomes harder to sustain. That is the useful question in Boone Ashworth’s March 2026 WIRED report about Soapstone Comedy Club in Horizon Worlds. This historical analysis does not claim to know the venue’s present operating status or offer a verified migration procedure.

What the report establishes

WIRED describes uncertainty after Meta announced a VR shutdown plan and then reversed course. The report distinguishes keeping existing VR experiences available from plans concerning creation features and mobile development. In its March 27 update, Soapstone’s CEO described a separate mobile-only experience that would not let its users interact with those in VR.

Participants quoted in the report differed about the importance of headsets. Some valued immersive performance; another emphasized social access without a headset. These are reported individual perspectives, not a survey of all users or proof of a clinical mental-health benefit.

The article therefore raises several distinct continuity questions: can people enter, can organizers change the venue, and can the same people still participate together? A single statement that the platform is “open” cannot answer all three.

Access, creation and co-presence are different dependencies

Access is the ability to reach an existing place. Creation is the ability to maintain or change it. Shared participation is the ability for the intended audience and performers to meet in the same session. A change can preserve one dependency while disrupting another.

For a recurring show, that distinction matters more than the corporate label attached to a service. A familiar room that cannot be updated may have different limitations from a newly built room that divides the audience across clients. Neither condition should be assumed merely from a headline about closure or survival.

This also makes user disagreement easier to interpret. Someone primarily seeking conversation may evaluate a flat-screen experience differently from a performer whose act depends on spatial props. Those preferences need not be inconsistent. The relevant question is which parts of the activity each person is trying to preserve.

An original continuity worksheet for an event

The following is a proposed planning exercise, not Soapstone’s internal plan or a tested transfer method. Begin with one specific event rather than an entire community. List the essential activities: announcing the session, admitting participants, taking turns, moderating disruptions and telling people where the next session will occur.

For each activity, identify the dependency it currently uses and who can verify it. Keep “works in the present setup,” “confirmed in a proposed setup” and “not checked” as separate states. A creator’s ability to open a destination account does not establish that attendees can join or that the event’s required controls exist there.

Then identify what requires the same shared space. A recording may preserve a performance but not the audience’s interaction. A contact list may preserve a communication route but not the room’s social habits. These are different assets, and a plan should say which one it is protecting.

Design a rehearsal that tests the event’s actual requirements

A rehearsal can be small and explicitly provisional. Choose the activity to test and the participants whose access needs it must cover. State what would count as a successful session before trying it. Do not describe an untested destination as equivalent merely because it also offers avatars or a stage.

Document the outcome in ordinary terms: who could enter, which interaction worked, what failed and what remained unknown. If a moderation action or host handover was not tested, leave that field open. This is a way to gather evidence, not a claim that every social platform supports the same controls.

Consent and communication also belong in the worksheet. Do not assume that an organizer may copy account information or private conversations to another service. Ask what participants actually want preserved and offer a clear explanation of any proposed change. This guide makes no legal determination about particular records or jurisdictions.

Preserve the social activity without inventing its future

A continuity plan should distinguish a dependency from a prediction. “We need a shared session” is a requirement. “Everyone will move to mobile” is a forecast that needs evidence. “A second venue exists” is an observation. “It will reproduce this community” is a much stronger claim.

The March case illustrates why a reversal of a shutdown announcement may not settle every practical concern. The value of the report is the detail of those differing dependencies and perspectives, not a generic verdict that the metaverse is either dead or thriving.

For organizers and readers, the durable takeaway is to name the activity, map its dependencies and test any proposed continuity route. That is more useful than promising effortless portability, assuming that all participants want the same interface or treating an individual’s account of belonging as a measured health outcome.

Source and original reading

Boone Ashworth, WIRED, March 25, 2026, with a March 27 update: https://www.wired.com/story/the-last-comedy-club-at-the-end-of-the-metaverse/