The metaverse is the internet we just need a bit of linking it all together, one company building it top down isn't going to beat out the obvious open internet approach.
The metaverse is the internet we just need a bit of linking it all together, one company building it top down isn't going to beat out the obvious open internet approach.
Anyway, back to what you said, I agree that seamless transition is the very big factor. IMO, "metaverse" requires seamless transition between assets not worlds. Current VR experience, even assuming a perfect browser, means that you switch between world when switching between websites. I believe that most usages would be that pages are mostly assets, not whole worlds. Kinda frames I guess. I don't think there is any specification at the moment for such a thing.
(Now I'm daydreaming of a VR RSS reader, where I move in my various news. Nope that doesn't sound like a good UX)
https://en.wikipedia.org/wiki/Vrml
> VRML (Virtual Reality Modeling Language, pronounced vermal or by its initials, originally—before 1995—known as the Virtual Reality Markup Language) is a standard file format for representing 3-dimensional (3D) interactive vector graphics, designed particularly with the World Wide Web in mind. It has been superseded by X3D.
https://en.wikipedia.org/wiki/X3D
X3D is a royalty-free ISO/IEC standard for declaratively representing 3D computer graphics. File format support includes XML, ClassicVRML, Compressed Binary Encoding (CBE) and a draft JSON encoding. X3D became the successor to the Virtual Reality Modeling Language (VRML) in 2001.[1] X3D features extensions to VRML (e.g. CAD, geospatial, humanoid animation, NURBS, etc.), the ability to encode the scene using an XML syntax as well as the Open Inventor-like syntax of VRML97, or binary formatting, and enhanced APIs.
There's also OpenXR: https://www.khronos.org/registry/OpenXR/specs/1.0/html/xrspe...
For example with the web the interoperability is really between the browser and websites rather than between websites. Although a few do interoperate. This is more similar to how Roblox or Steam works where one program lets you join lots of different games and maintains some common state than common ideas of interoperability in the metaverse.
I think the Zuck use case was buying a t-shirt for a virtual avatar and I want to use that t-shirt in other applications. There is a matter of interoperability required at the level of the data that sits behind both applications as it pertains to the user that sits on the other side of those applications. (meaning just sharing data isn't enough, there is user level context as well).
And if you reduce interoperability to a single entity owned platform (like Steam), well other platforms will exist and the interoperability problem will be recreated.
To me the issues that require addressing are things like standardization, general uniqueness proofs, Cross-app total order broadcast, identity and service discovery, to just name a few.
My feeling is that the internet does not solve these problems, especially at the application layer, and therefore interoperability is a technical solution that is required for a metaverse like vision.
I believe the path to those soltuons does lie on the road of ubiquitous and dynamic technical interoperabity for web applications.