HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
MozillaReality
FirefoxReality
Java2018–2022
MozillaReality / FirefoxReality · Archived

FirefoxReality

INACTIVE - A fast and secure browser for standalone virtual-reality and augmented-reality headsets.

9Distinct people
12Mentions
0Explicit recommenders
772GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

INACTIVE - A fast and secure browser for standalone virtual-reality and augmented-reality headsets.

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, 3:56:07 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 year12 dated mentions

Observed mentions: 2018-09-19 11:57:20 UTC to 2022-02-03 20:19:57 UTC.

02462018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2022

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
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC707
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC303

What Hacker News says

12 sources
This is really interesting. Last night I was looking at FireFox Reality's repo and was pleasantly surprised to see [some newer commits][1]. Now today I see that Wolvic is [a fork of FireFox Reality][2] and that the commits were contributed from that project. I'm happy to see a private company fund new work on this front. [1]: https://github.com/MozillaReality/FirefoxReality/commits/mai... [2]: https://github.com/Igalia/wolvic
In Wolvic, a new browser project picking up where Firefox Reality leaves off
Unfortunately, we don't currently support phone-based Daydream or Gear VR devices. There's both a bunch of extra work to support all of the phone in/out/notification lifecycle scenarios and we have a pretty small engineering team and the long tail of phone/chipset-specific bugs is pretty substantial. We might evaluate support for it or Cardboard in the future, but for right now we're mainly focused on standalone headsets. That said, we're all in favor of people who want to sideload and play with it! https://github.com/MozillaReality/FirefoxReality/wiki/Sidelo...
In Firefox Reality
Not by default yet, but you can enable it for testing. Requires a recompile with a properties file to make the option appear. >Experimental Servo support >To compile with Servo support, create a file called user.properties in the top-level project directory and add enableServo=1. Then to enable Servo in Firefox Reality, go the Developer Options panel in the Settings, and toggle the Servo option. Then a new button will be added to the navigation bar. Clicking that button will reload the current page with Servo. https://github.com/MozillaReality/FirefoxReality
In Firefox Reality
EDIT: I took a quick look at the codebase for the browser (https://github.com/MozillaReality/FirefoxReality), and it isn't what I was expecting (once you dive to app/src) - definitions for the main three supported systems are each at this root level, and I didn't see any kind of "template" or "empty" definition file or anything to guide someone wanting to make one themselves - but maybe that's not possible. It appears that these files are wrappers around the APIs used for those other products (?). So your only hope would be to base your wrapper on these existing ones, which while feasible (working with the API docs too), isn't what I would call "ideal". Plus, there doesn't seem to be a separation of concerns when it comes to input vs output. I mean, what if I wanted to use my hacked powerglove with my Rift HMD? Or what if I wanted to use
Read the rest
my Vive controllers with my Virtuality Pro? I understand that the supported systems are nominally "all-in-one" solutions, but the parts (HMDs, controllers, tracking) are available separately (at least in some of the cases) - so mixing and matching might be something someone would want to do. It would definitely be that case for those implementing their own "mixed setup", where they might have an old VPL datasuit and glove, plus some other old pro-level HMD that they like to play with. As it is, it seems like each setup would have to be a custom "all-in-one" for that setup, so if you had two different systems that used two different HMDs and tracking, but both used the same Powerglove Minelli interface - the code couldn't be "shared" in a reasonable manner (yes, I know with the right symlinking and other buggery it could be accomplished within the current structure, but it isn't ideal). I was hoping the structure would be more like /plugins, with /input /output, and under those /controller /glove /wand and /hmd /motionplatform /cave, then under each /occulus /vive /google /example Or something like that. Am I wrong here? --- Ok - I know this is likely open source and thus can be changed, but I honestly wish that things like this offered (and marketed) a means - via plugins or something (and maybe this does - hence, marketed) - the ability to expand on what i/o devices are allowed. Sure - should the "main players" be featured? Of course. But what about those of us who might like to - oh, I don't know - throw on an old Forte VFX-1 and a Powerglove and go at it? Maybe we want to recreate the experience of using REND386? Or what if you have access to a Polhemus or Ascension magnetic tracking system (or any number of other "pro-level" tracking)? Or HMDs? Or other input devices? Or motion platforms? Maybe you're a developer of something completely new, and want to play in this same environment and make it compatible... Again - I haven't dug into the code, and maybe it's designed to accommodate these kinds of use cases. I'd just love to see that availability, if it exists, to be advertised more. I guess its because I get the same feeling around software released for my OS of choice, where Windows and Mac are prominently advertised, and Linux is at best, if it's offered at all, the classic step-child stuffed in a closet. As an aside, I never can figure out the argument that "we don't offer support for Linux because the market is so small, it isn't worth it for us" - well, if everyone keeps saying and doing that, what do you think will ultimately occur? Do you think that market will grow, stay the same, or shrink?
In Firefox Reality
Not sure what the situation is for tabbed browsing in this. "Viewing multiple pages concurrently" issue repeatedly mentions tabs as something that needs to be designed https://github.com/MozillaReality/FirefoxReality/issues/635, in May saying "Will keep this issue open for designing Tabs. Feel free to make changes to track the design + engineering." But then in June it's "Closing this in favor of new meta bug #1319" And #1319 does not mention tabs anywhere. https://github.com/MozillaReality/FirefoxReality/issues/1319 Maybe tabs have been implicitly bundled into "multiwindow" when they're talking about that? Can't check myself because the Quest version doesn't have any multiwindow support, it looks like they're working on a crash issue for it. I tried a dev build sideloaded last week on the Quest and being in a single-window no-tab environ
Read the rest
ment where you can only have one page open at a time is very limiting. But as soon as that's worked out, I'll be switching to this as the main browser. I wonder if it will be possible for someone to patch Oculus Home so that the Browser button opens this instead.
In Firefox Reality

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.