The four hard problems any Metaverse framework will have to solve are transactions, data persistence, code isolation, and forward compatible code evolution. And it will have to solve them at vast scales of concurrency. Nothing even remotely resembling this exists yet.
-
-
-
Looks a lot like Vivaty, Lively, SmallWorlds, and lots of others. What's different about it structurally?
- 2 more replies
New conversation -
-
-
But virtually all commonly described use cases rely on aggregation of large volumes of data: layers of geoannotations for every square inch, object histories, etc. Large data stores will be a major center of gravity for any design, hard to avoid.
-
There’s also the fact that we only need around 10%-20% of connected entities to be able to gather data on the entirety...
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.