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:26:05 +01:00
parent a92e6c1404
commit 859c3f918e
1 changed files with 4 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
index.html
View file

@ -507,10 +507,13 @@ In contrast, <b>(bottom-up) XR hypermedia</b> offers a more cost-efficient path.
<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>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> <br><Br>
<b>Q: What is the 'XR at rest' criteria? <b>Q: What is the 'XR at rest' criteria?</b><br>
<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>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> <br>
<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.<br>
<div class="footer"> <div class="footer">
<small>Jump to:</small> <small>Jump to:</small>