Meta Shell

The HTML holding the iFrames

DOT FROM lambda-browsing

~

codefrau 🦩 via discord […] Our main focus is on the collaborative nature of our worlds, building the tools, and defining the meta shell protocol (which will allow interoperability with non-croquet worlds too). […]

codefrau 🦩 via discord Oh for sure, we can have something but it won't be as pretty or secure as when using iframe compositing. Right now, neither the meta shell (the html holding the iframes) nor the iframes (running each world) depend on being trusted, they execute completely isolated, and only minimal information is exchanged between them. If a frame was to send a screenshot to the shell or to another frame that could be a potential privacy violation – and something that is entirely avoidable by visual compositing in the browser.

The above conversation discusses the concept of a "Meta Shell" and its relationship with secure and sandboxed iframes. The main focus of the discussion is on the collaborative nature of the worlds, building tools, and defining the meta shell protocol. The meta shell is described as the HTML that holds the iframes, and the iframes are responsible for running each world. The communication between the meta shell and the iframes is currently minimal and isolated to maintain security and privacy.