, US (<ahref="https://www.state.gov/wp-content/uploads/2022/04/Declaration-for-the-Future-for-the-Internet.pdf"target="_blank">DFI</a>), and Canada (<ahref="https://ised-isde.canada.ca/site/innovation-better-canada/en/canadas-digital-charter-trust-digital-world"target="_blank">DC</a>), narrowed down to <b>OpenSource</b> XR experiences via <b>link traversal</b>.<br>
<buttononclick="alert('Hi there!\nPlease send a mail to\n\nleonvankammen+xrhf @ isvery.ninja\n\nthanks!')"style="padding:30px;margin:20px">Contact us</button>
<b>Biggu's Gate</b> is self-hostable web-software to remix simple pedagogical XR games. Learners themselves can then, together with parents and teachers.
JanusWeb's <b>XR translators</b> spatialize the web, embedding webstandards like (RSS/HTML) and popular fediverse platforms (peertube/mastodon e.g.).<br>
AFRAME-verse was a XR Hypermedia network-experiment which traverses crossdomain AFRAME XR experiences seamlessly. The learnings became the fundament for the XR (URI) Fragments.<br>
<divclass="desc">URL-linked virtual worlds (JanusVR) by James McCrae (incl. URL portalsystem). Rebrands in 2020 to (opensource) <b>JanusXR</b> with focus on <ahref="https://github.com/jbaicoianu/janusweb"target="_blank">janusweb</a>. First <b>convincing</b> VR-headset-compatible <b>user-operated</b> spatial web, used by more than thousands of users.
<divclass="desc">NLnet #NGI #EU funds <ahref="https://xrfragment.org"target="_blank">XR URI Fragments</a> by Leon van Kammen. Standardisation of spatial anchors in <b>URI's</b>. It got adopted by startups like Alkebulan, and was coincedentally (already) implemented by <ahref="https://github.com/jbaicoianu/janusweb"target="_blank">janusweb</a> (independent simultanious innovation 💡).
<divclass="desc">First ever in-WebXR Terminal running an actual Linux ISO. This researchproject basically brings the opensource linux ecosystem to otherwise closed proprietary headsets. Aerospace engineers have reported to be using it.</div>
<ahref="https://han.nl">HAN University</a> uses <ahref="https://xrfragment.org"target="_blank">XR (URL) Fragments</a> while researching VR accessibility. One of the results of this collaboration is the addition of <ahref="https://xrfragment.org/doc/RFC_XR_Fragments.html#two-button-navigation"target="_blank">2-button navigation</a> to the XR Fragments spec.
<ahref="https://xrforge.isvery.nl">XRForge</a> streamlines the design, collaboration, deployment, hosting, and integration of portable XR experiences - and thus further simplify embedding, cross-platform support and hosting, as well as add vendor specific support.
ELFA, a suite of local-first applications with VR/XR integration, got funded by EU's <ahref="https://commission.europa.eu/funding-tenders/find-funding/eu-funding-programmes/horizon-europe_en"target="_blank">Horizon Europe</a>.
♥️ = janusweb has the highest local-first XR hypermedia-support, see <ahref="https://coderofsalvation.github.io/janus-guide/#/wiki/translators"target="_blank">translators</a>, <ahref="https://coderofsalvation.github.io/janus-guide/#/wiki/polyglot-files"target="_blank">polyglot</a> and <ahref="https://coderofsalvation.github.io/janus-guide/#/wiki/addressibility"target="_blank">addressibility</a> and runs on desktop/phone/headset all-at-once.
A much more interesting is <b>seamless XR hypermedia</b> surfing: by interlinking 3D files <b>immersively</b> via <ahref="https://xrfragment.org"target="_blank">(XR Fragment) URLs</a> or <ahref="https://coderofsalvation.github.io/janus-guide/"target="_blank">JanusWeb</a>.<br>See the difference below:<br><br>
<b>A:</b> It depends, The value of a digital common lies in its liquidity. If you wrap public-domain content in restrictive security layers (like heavy DRM or complex access controls), you destroy the "common" aspect. Since the content is meant to be seen and shared, there is no "secret" to protect. Attempts to ensure it isn't maliciously altered are saluted. Scripting languages as part of the content are hypermedia-'killers' as they are a huge attack-vector (eventually turning browsers into a unuseable banking-grade security sandboxes). Open fileformats like `.gltf` and their extensions are at the safest side of the spectrum.
<b>A:</b> Not really, regarding <b>payments</b> the issues currently are: price volatility and regulatory/AML compliance hurdles. Privacy mechanisms like <ahref="https://www.taler.net/en/index.html"target="_blank">TALER</a> can be discussed though. <br>
<b>Minting virtual parcels via crypto-transactions</b>: unfortunately this does not qualify as 'local-first', and (un)intentionally enables rentseeking and first-mover-advantage.
<buttononclick="alert('Hi there!\nPlease send a mail to\n\nleonvankammen+xrhf @ isvery.ninja\n\nthanks!')"style="padding:30px;margin:20px">Contact us</button>
<b>Q: How do you identify "XR interoperability-washing"?</b><br/>
<b>A:</b><i>"XR interoperability-washing"</i> is akin to greenwashing; it occurs when companies aggressively <b>market a commitment to open standards</b> while their top-down corporate structures make true interoperability technically impossible. It also partially explains why <b>XR interop</b> historically creates <b>top-down</b> talkshops, instead of actual <b>bottom-up</b> interop (like JanusXR).<br>
Characteristics:
<ul>
<li>Top-down B2B-interop (instead of bottom-up)</li>
<li>complex SDKs and proprietary integrations</li>
<li>proprietary servers as essential component</li>
While these methods may offer limited connectivity, they fall short of providing a sustainable, seamless "world-to-world" browsing experience (XR hypermedia).<br>
In contrast, <b>(bottom-up) XR hypermedia</b> offers a more cost-efficient path.<br>
By removing the need to protect stakeholders, centralized user bases, or specific crypto-wallets, it flips the traditional power structure. <br>In this model, the user—not the corporate stakeholder—is the starting point and operator of the network.
<b>NOTE:</b> XRHF is not anti-business, it's just that many online businesses don't have the 90s internet-mindset like DNS-companies (the network is the market, not the users).
<b>A:</b> Basically that XR experiences should be cheap to archive and reproduce: the 'XR at rest' criteria dictates that immersive experiences should ideally exist as persistent, static files rather than being dependent on active, power-hungry server processes.<br>By decoupling the XR space from continuous compute requirements, these experiences remain accessible even when the original hosting infrastructure or company servers are powered down. <br>This approach leverages a 'cacheable' hypermedia architecture, allowing virtual environments to be served and cached much like standard web pages.<br> Ultimately, this ensures the long-term preservation and interoperability of the spatial web, preventing "digital decay" common in traditional live-service gaming models.
<b>Q: What is the 'credible exit' criteria?</b><br>
<B>A:</b> A credible exit ensures that users are never trapped within a single ecosystem, allowing their digital identity, assets, and progress to remain functional even if they switch platforms.<br> By prioritizing data portability and interoperable file standards, developers protect the user's long-term investment and prevent the loss of personal data if a service is discontinued.<br> Ultimately, providing a clear path to move data elsewhere fosters trust and is a fundamental requirement for building a truly open and decentralized XR landscape.
