3 ms·

Very cool. Two questions: 1. How do you plan to make money with this? 2. If the data is owned by me, is there also an easy way to get all my blog posts out of

Very cool. Two questions: 1. How do you plan to make money with this? 2. If the data is owned by me, is there also an easy way to get all my blog posts out of the system in a usable format (e.g. so I could put it on my own server later)?

jhunter1016 8y ago
Thanks for the questions! Quite honestly, we may not ever charge for this product. But some ideas are: -Provide a custom Gaia Hub with encrypted storage that has higher limits than the default Blockstack hub. -Charge for additional features (integrations, team publications, etc) -Just charge a small amount for access and allow those who don't want to pay that the option to clone the open source repo and deploy it themselves An export feature will be built into Graphite Publishing (much like the one that already exists in Graphite). But one of the core tenets of data ownership is you should not need to rely on the app to access your data. In that vein, there is still work to be done. But it is already possible to use the command line to export all your data without ever touching Graphite Publishing. All content is in HTML format, so it should be usable in many different apps.
stdcli 8y ago
You own your own data in a "gaia hub" where apps have to have permission to write this data to your hub, permitted you give it to them. This way, if you ever leave graphite, or any other app in the eco system, you still have your data in the gaia hub. You can use the gaia cli to list all the files you have. You can host your own gaia hub, or have a default hosted configuration, but still it is associated with your username/identity. We are working on gaia hub migrations so you can easily migrate data from one place to the other. Soon we will have images to auto launch on most cloud hosting platforms. The docker-compose files should allow for setup on a local server as well. I am prioritizing users hosting gaia hubs on their own servers over any cloud host provider. Let me know if you have any more questions. But yes, the entire idea is centered around #2.

jhunter1016 8y ago

Thanks for the questions! Quite honestly, we may not ever charge for this product. But some ideas are: -Provide a custom Gaia Hub with encrypted storage that has higher limits than the default Blockstack hub. -Charge for additional features (integrations, team publications, etc) -Just charge a small amount for access and allow those who don't want to pay that the option to clone the open source repo and deploy it themselves An export feature will be built into Graphite Publishing (much like the one that already exists in Graphite). But one of the core tenets of data ownership is you should not need to rely on the app to access your data. In that vein, there is still work to be done. But it is already possible to use the command line to export all your data without ever touching Graphite Publishing. All content is in HTML format, so it should be usable in many different apps.

stdcli 8y ago

You own your own data in a "gaia hub" where apps have to have permission to write this data to your hub, permitted you give it to them. This way, if you ever leave graphite, or any other app in the eco system, you still have your data in the gaia hub. You can use the gaia cli to list all the files you have. You can host your own gaia hub, or have a default hosted configuration, but still it is associated with your username/identity. We are working on gaia hub migrations so you can easily migrate data from one place to the other. Soon we will have images to auto launch on most cloud hosting platforms. The docker-compose files should allow for setup on a local server as well. I am prioritizing users hosting gaia hubs on their own servers over any cloud host provider. Let me know if you have any more questions. But yes, the entire idea is centered around #2.