Metadata process

Details

Loading 3D content will be a bootstrap process each time. Since all content is statically referenced from the blockchain. Default control mechanisms(viewing on HMD, Desktop, or Mobile), profile defaults(do you watch movies by the ocean, or by a campfire), and a reference to a 360 capture of the starting camera placement, that overflows to a other assets that may have been posted from other DApps(load a video from d.tube to your screen by a campfire... that you can drag around and place for however you are sitting).

Simply put, the more content we can deliver to VR the better. Building handlers that:

• if 720hash -> trigger videoCanvas(hash, args)
• if 480hash -> trigger videoCanvas()
• if 240hash -> ...
• if VR -> load sciptshash / assetshash

Feel free to challenge yourself, any data pulled can be represented in 3D, Just a matter of placing a dynamic container.

Components

Modify main.getPostAndComment() to point to various load scipts for dtube/ipfs content(parallel construction).

Help design router.post('/create-dluxpost', ...) to close the loop between content creation and delivery.

Commit: Pull request#1 has two starting points commented

Deadline

This is a central part of delivering an experience. Hopefully, the ability to load D.Tube/Dlive content, as well as basic VR content by April 5th

Communication

Available on discord, or by email or the preferential dlux on discord