When you onboard with the Blockstack browser, your data gets stored automatically to Blockstack PBC’s default Gaia hub. This is due to the way the sign-in process works in Blockstack – before you can edit your profile or sign into any apps, you need to be able to store data somewhere. This means you need a Gaia hub running somewhere before you can do anything else.
To make it easier for users to get started using apps, Blockstack PBC simply provides a Gaia hub for general use. Unfortunately, but also predictably, this resulted in nearly every user using the default Gaia hub, which caused them all to be affected by the default Gaia hub’s SSL outage. Let me be clear about this–this is not the outcome any of us, especially us at Blockstack, want to live in.
What we’re trying to figure out instead is how to reconcile the need for users to have a good on-boarding experience with the need for users to keep their data in different Gaia hubs. This is already supported at the protocol level, but it isn’t easy to get users to do this since they don’t have any incentive to run their own hubs. I have a few ideas about how to provide better incentives, but I’d also like to hear from the community. What would it take to get you to run your own Gaia hub?