coderofsalvation/xrhf
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

🔧 master: work in progress [might break]

Browse source
This commit is contained in:
Leon van Kammen 2026-02-22 11:17:13 +01:00
parent ae3d565452
commit a92e6c1404
1 changed files with 13 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
index.html
View file

@ -490,21 +490,26 @@
<hr/> <hr/>
<b>Q: How do you identify "XR interoperability-washing"?</b><br/> <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.<br>These entities often promote:<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> <ul>
<li>Top-down business2business-interop (instead of bottom-up)</li> <li>Top-down B2B-interop (instead of bottom-up)</li>
<li>complex SDKs and proprietary integrations <li>complex SDKs and proprietary integrations</li>
<li>proprietary servers as essential component</li> <li>proprietary servers as essential component</li>
<li>designed to "lock in" their user base</li> <li>designed to "lock in" their user base</li>
<li>no credible exit (run content elsewhere e.g.)</li> <li>no credible exit (run content elsewhere e.g.)</li>
</ul> </ul>
<blockquote>
<b>Metaphor:</b> XR interoperability-washing is similar to a DNS-company (which allows you to register a domain) without a 'transfer a domain'-feature.
</blockquote>
While these methods may offer limited connectivity, they fall short of providing a sustainable, seamless "world-to-world" browsing experience (XR hypermedia).<br> 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. 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).
<br><Br>
<b>Q: What is the 'XR at rest' criteria?
<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.
<br>
<div class="footer"> <div class="footer">