The metaverse could be successful but it needs to be a protocol not a proprietary product by one company, least of all Facebook.
Right now anyone can make a website if they know how to program one. It can be hosted on any number of services or you can host it yourself if you have the hardware. Your website can look like anything, have any functionality you want, be as complex as you want, be as large as you want. You can use website builders or you can go entirely custom. There is a huge range of options.
What now needs to happen is that same thing for the metaverse. It needs to be a standard programming language or set of programming languages that people can learn, that will enable them to build experiences. Those experiences should be hostable on any old server and a routeing protocol needs to be developed so that people can access them without having to worry about the underlying infrastructure. Second Life does a very good job of modifying the web URL concept to work for virtual worlds, just copy that. There also needs to be a standardised API for returning feedback responses and querying available interfaces (vibration motors, speakers, lights, force resistance motors etc) that all headsets and interaction devices use.
Perhaps some kind of federation service that enables different servers to interact with each other for transferring items from one environment to another and making sure that they make sense in all environments.
The metaverse could be successful but it needs to be a protocol not a proprietary product by one company, least of all Facebook.
Right now anyone can make a website if they know how to program one. It can be hosted on any number of services or you can host it yourself if you have the hardware. Your website can look like anything, have any functionality you want, be as complex as you want, be as large as you want. You can use website builders or you can go entirely custom. There is a huge range of options.
What now needs to happen is that same thing for the metaverse. It needs to be a standard programming language or set of programming languages that people can learn, that will enable them to build experiences. Those experiences should be hostable on any old server and a routeing protocol needs to be developed so that people can access them without having to worry about the underlying infrastructure. Second Life does a very good job of modifying the web URL concept to work for virtual worlds, just copy that. There also needs to be a standardised API for returning feedback responses and querying available interfaces (vibration motors, speakers, lights, force resistance motors etc) that all headsets and interaction devices use.
Perhaps some kind of federation service that enables different servers to interact with each other for transferring items from one environment to another and making sure that they make sense in all environments.
Another underlying aspect is the dimensionality:
Going from nD to 3D, is a step back, and even when people don’t realize it consciously, they’ll keep falling back to the superior webpage solution.
Until someone puts the nD mobility into 3D worlds, there is no chance for them to take over.
Third Room by matrix.org does all of this.
Like VRML from the 90s? https://en.wikipedia.org/wiki/VRML?wprov=sfla1