The Hypermediatic Experience ================================ <style type="text/css"> .reveal .slide-background{ background: #FFF; } h1,h2,h3,h4{ color:#08f !important; } h1.raw.part{ font-size:40px;} </style> <img src="https://hackmd.io/_uploads/rJmaKN_xa.png" style="width:90%"/> --- ## XR redefining hypermedia * hypermediatic (HyperX?) * reasoning backwards (future to past, realities to text) --- ## Q: Which came first: text or images --- ## Q: Which came first: hypertext or hypermedia? --- ## A: through a symbolic lens they appear to be the same. --- ## A: through an XR lens they appear to be the same. --- <center> <img src="https://hackmd.io/_uploads/B1vd0VOgp.png" style="width:80%"/> </center> --- ## Through the lens of reality-to-text synthesis ---  --- ## Hyper connectivity  ---  --- <center> <img src="https://hackmd.io/_uploads/BkvpCVdgp.png" style="width:80%"/> </center> --- ## TikTok, Youtube Great video-databases, hypermedia-like, but not really hypermediatic > can I click a table inside a video? or click on a person in a podcast? user-curated webrings? --- ## For hypermediatic XR synthesis The textual **public carrier seems to be the URL**, and its modulators are other **(hypermedia) URLs** <br> --- ## The URL is textual time-space encoding/decoding the invisible cognitive ETHER which adresses and connects symbolic experiences between humans. --- <h2>Let's get drunk on URLs, Mcluhan-style</h2> --- <div style="position:relative;text-align:left"> <img src="https://hackmd.io/_uploads/rJ_kQBdla.png" style="width:35%"/> <div style="position:absolute;top:0%; left:38%;"> <b>The URL is the message</b><br> HTML is JUST a (hyper) text/media format <br> </div> </div> --- <div style="position:relative;text-align:left"> <img src="https://hackmd.io/_uploads/rJ_kQBdla.png" style="width:35%"/> <div style="position:absolute;top:0%; left:38%;"> <b>The URL is the message</b><br> HTML is JUST a (hyper) text/media format The browser is JUST an app. <br> </div> </div> --- <div style="position:relative;text-align:left"> <img src="https://hackmd.io/_uploads/rJ_kQBdla.png" style="width:35%"/> <div style="position:absolute;top:0%; left:38%;"> <b>The URL is the message</b><br> HTML is JUST a (hyper) text/media format The browser is JUST an app. The HTTP protocol is JUST a protocol. <br> </div> </div> --- <div style="position:relative;text-align:left"> <img src="https://hackmd.io/_uploads/rJ_kQBdla.png" style="width:35%"/> <div style="position:absolute;top:0%; left:38%;"> <b>The URL is the message</b><br> HTML is JUST a (hyper) text/media format The browser is JUST an app. The HTTP protocol is JUST a protocol. In XR, Hypertext is JUST a hypermedia fileformat. <br> </div> </div> --- <div style="position:relative;text-align:left"> <img src="https://hackmd.io/_uploads/rJ_kQBdla.png" style="width:35%"/> <div style="position:absolute;top:0%; left:38%;"> <b>The URL is the message</b><br> HTML is JUST a (hyper) text/media format The browser is JUST an app. The HTTP protocol is JUST a protocol. In XR, Hypertext is JUST a hypermedia fileformat. The OS (apps) are the (nested) browser. <br> </div> </div> --- # Migrate URL to OS Opportunities ### protocol://foo.fileformat#view * OS as the browser * protocol-store for OS/apps * fileformat-store for OS/apps * hypermedia viewing-hints for apps > this allow URL-friendly XR hypermedia-first apps and games, in a thin-client way --- <video src="https://coderofsalvation.github.io/xrfragment.media/xrfragment.bumper2.mp4" style="width:100%" play autoplay controls loop/> --- # Example: the XRWG [xrfragment.org] <img src="https://i.imgur.com/KDukd0v.gif" style="width:100%"/> --- # Thank you leonvankammen@gmail.com lvk@mastodon.online xrfragments.org --- # reality vs perception <img src="https://i.imgur.com/9mLQ1x9.png" style="width:90%"/> --- # Thank you --- ## Questions 1. Until which point is HTML holding back high performant hypermedia-surfing of images/sound/video/3D? 2. Why are web browsers poorly supporting other file formats & protocols using URLs? And when should the individual (not) decide which file formats / protocols are deferred to the browser-extension backseat? 3. Why are hypermedia file formats not encouraged to support the outbound/embedded hyperlink-paradigm like HTML? 4. Why are operating systems not supporting/encouraging outbound/embedded links in file formats out of the box? (liquid information/hyperwords e.g.) 5. Is a scriptinglanguage, embedded into documents an anti-pattern for hyperlinking / hypereconomy / hypernavigation? --- the hypertext-first-hypermedia-later vision which most web browsers and operating systems seem to share. From an historical perspective this makes sense (it was easier to project text than images back in the days). However, it also means that whatever fileformat is consumed in the web browser, gets served through this lens, through HTML, or indirectly via browser extensions. This however, makes hasslefree native hypermedia experiences a second-class citizen, because the web browser doesn’t seem to motivate the user: ● To browse to an URL inside an image (when surfing to foo.com/bar.png e.g.) ● To browse to an URL inside a video (when surfing to foo.com/bar.mp4 e.g.) ● To browse to an URL inside audio (when surfing to foo.com/bar.mp3 e.g.) ● To switch mediatype (switch from surfing audiolinks to videolinks e.g.) --- 2. A GPS URL: ://somefile.extension#q=<latitude>,<longitude> It is very interesting why our browsers are not motivated enough to standardize URLs towards spatial ‘globe’ browsing. This could encourage people on a local level to annotate/capture/map their environment, and add hyperlinks to other topics/places/photo URLs etc. We don’t need ALL gps metadata at our fingertips, just a globe. On this globe, surfed documents would just appear on certain coordinates on the go. 3. A 4D URL: ://somefile.extension#pos=0,0,0&rot=0,0,0&t=1,0,100 ---