HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
matrix-org
thirdroom
C2022–2023
matrix-org / thirdroom

thirdroom

Open, decentralised, immersive worlds built on Matrix

4Distinct people
6Mentions
0Explicit recommenders
658GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Open, decentralised, immersive worlds built on Matrix

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month6 dated mentions

Observed mentions: 2022-02-08 22:17:28 UTC to 2023-12-26 09:21:50 UTC.

012022-02-01 00:00:00 UTC to 2022-03-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsFeb 20222022-03-01 00:00:00 UTC to 2022-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-04-01 00:00:00 UTC to 2022-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-01 00:00:00 UTC to 2022-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-06-01 00:00:00 UTC to 2022-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-07-01 00:00:00 UTC to 2022-08-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-08-01 00:00:00 UTC to 2022-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-09-01 00:00:00 UTC to 2022-10-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2022-10-01 00:00:00 UTC to 2022-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-11-01 00:00:00 UTC to 2022-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-12-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2023-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 20232023-02-01 00:00:00 UTC to 2023-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-03-01 00:00:00 UTC to 2023-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-04-01 00:00:00 UTC to 2023-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-05-01 00:00:00 UTC to 2023-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-06-01 00:00:00 UTC to 2023-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-07-01 00:00:00 UTC to 2023-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-08-01 00:00:00 UTC to 2023-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-01 00:00:00 UTC to 2023-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-01 00:00:00 UTC to 2023-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-01 00:00:00 UTC to 2023-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-12-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Feb 20222022-02-01 00:00:00 UTC2022-03-01 00:00:00 UTC110
Mar 20222022-03-01 00:00:00 UTC2022-04-01 00:00:00 UTC000
Apr 20222022-04-01 00:00:00 UTC2022-05-01 00:00:00 UTC000
May 20222022-05-01 00:00:00 UTC2022-06-01 00:00:00 UTC000
Jun 20222022-06-01 00:00:00 UTC2022-07-01 00:00:00 UTC000
Jul 20222022-07-01 00:00:00 UTC2022-08-01 00:00:00 UTC101
Aug 20222022-08-01 00:00:00 UTC2022-09-01 00:00:00 UTC000
Sep 20222022-09-01 00:00:00 UTC2022-10-01 00:00:00 UTC110
Oct 20222022-10-01 00:00:00 UTC2022-11-01 00:00:00 UTC000
Nov 20222022-11-01 00:00:00 UTC2022-12-01 00:00:00 UTC000
Dec 20222022-12-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
Jan 20232023-01-01 00:00:00 UTC2023-02-01 00:00:00 UTC000
Feb 20232023-02-01 00:00:00 UTC2023-03-01 00:00:00 UTC101
Mar 20232023-03-01 00:00:00 UTC2023-04-01 00:00:00 UTC000
Apr 20232023-04-01 00:00:00 UTC2023-05-01 00:00:00 UTC000
May 20232023-05-01 00:00:00 UTC2023-06-01 00:00:00 UTC000
Jun 20232023-06-01 00:00:00 UTC2023-07-01 00:00:00 UTC101
Jul 20232023-07-01 00:00:00 UTC2023-08-01 00:00:00 UTC000
Aug 20232023-08-01 00:00:00 UTC2023-09-01 00:00:00 UTC000
Sep 20232023-09-01 00:00:00 UTC2023-10-01 00:00:00 UTC000
Oct 20232023-10-01 00:00:00 UTC2023-11-01 00:00:00 UTC000
Nov 20232023-11-01 00:00:00 UTC2023-12-01 00:00:00 UTC000
Dec 20232023-12-01 00:00:00 UTC2024-01-01 00:00:00 UTC101

What Hacker News says

6 sources
> having entire foundation-authored blog posts dedicated to updates to Third Room (which I did not think was a project owned and maintained by the foundation?) TR is a Foundation project - its repo is github.com/matrix-org/thirdroom (not github.com/vector-im); its copyright is by the Foundation, etc. And the point is to provide spatial collaboration building blocks for Matrix (just like Olm provides e2ee building blocks; matrix-js-sdk provides IM & VoIP building blocks) etc. > where other projects (e.g. Synapse, bridges, etc) don't get as much as a tweet nowadays (apart from the spec, i.e. Matrix itself) That’s my bad; the projects seem to have fallen into the habit of publishing and tweeting/tooting/skeeting their updates in TWIM (eg friday’s 1.0.0 release of the IRC bridge) rather than via individual tweets and blog posts like we used
Read the rest
to. The reason is that the various projects prefer to write software than blog posts/tweets, and I’ve lapsed in writing the posts/tweets myself (given I spend my life trying to fix funding and get Element X shipped) and haven’t successfully handed over to someone else to do it. It doesn’t mean the work isn’t happening though; we’re just failing to show off about it. > Which imo sounds like Third Room being prioritised over moderation/t&s. The rationale is that if TR generates money, that money can be put to more T&S and the rest of Matrix. It’s a way of trying to fix the funding nightmare. If it doesn’t generate money (by attracting innovation funding from people who actually like the idea of open spatial collaboration), then obviously folks won’t be able to work on it as their dayjob as there won’t be $ to do so. I guess one way of thinking about is that we model TR’s funding as separate from the rest of the Foundation - it has to be able to fund itself, and it is not stealing resources from elsewhere. (You could argue it steals focus, but in turn it exercises large chunks of Matrix - VoIP, Hydrogen SDK, SFUs etc, which I believe compensates for that, in combination with the marketing value). TL;DR: if TR doesn’t pay for itself via its own funding or by generating cash, then we won’t have $ to pay for it.
In Third Room and Web Scene Graph: A New Web API for Spatial Collaboration
Arathorn·Sep 27, 2022Submission

Show HN: Third Room Tech Preview: open decentralised worlds built on Matrix

Hi all, We just launched the first public tech preview of Third Room: an open source, standards-based, decentralised vision of interoperable virtual worlds for the open Web, built entirely on Matrix - without cryptocurrencies, NFTs or walled gardens. It's built on an new opensource game engine for the web called Manifold, which provides a solid 60fps of fullscreen 3D thanks to multithreading across webworkers using SharedArrayBuffers and Atomics, using Three.js for rendering, bitECS as an entity component system, Rapier for physics and Hydrogen for Matrix chat+networking. It requires no servers other than your normal Matrix homeserver. You can play with it at https://thirdroom.io or hop straight into a world like https://thirdroom.io/world/#terra-1:thirdroom.io. The code is all Apache Licensed up at https://github.com/matrix-org/thirdroo
Read the rest
m. We're hoping this provides a much-needed counterbalance to the Big Tech visions of the metaverse, or ones which are entangled with decentralised financial incentives, and might be a genuinely open platform for building spatial web/metaverse apps in future. Feedback welcome!
10 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.