I'm struggling with the same question as I look at how we may move my metaverse for sports company (https://ayvri.com https://ayvri.com) to a distributed model.

I'm struggling with the same question as I look at how we may move my metaverse for sports company (https://ayvri.com https://ayvri.com) to a distributed model. I think GPS data is a good model for moving to a distributed environment because people are often uploading to multiple different apps, and of course, they want to move things from one app to another. Strava has been a good custodian of GPS data in the sports world, but they are not above removing API access for apps which they view as competitive (they've did it to relive.cc and others). We have no value in being the owner of your GPS data, I'd much rather see an environment where you can take your workout data and use it in whatever platform you chose by giving access to your wallet and a common API which can be developed in public, with input from the community. I'll be taking some time over the xmas break to understand how to accomplish this. We are a revenue generating company, but the revenue generating component is not the distributed web3 part. Though I'm not absolutely sure that needs to be a major part of the revenue component, just as SQL isn't the "revenue generating" part of Shopify or Slack. Definitely keen to hear thoughts on this, and if anybody can point to a good community to learn more.