All data is stored in the storage hub of the user's choosing rather than being stored in a database centralized to Graphite Publishing. In fact, Graphite Publishing doesn't have access to anyone's data.
But you're right, a blockchain is not necessary for decentralized blogging and is not used for data storage at all in this app.
I suspect most users don't like dealing with multiple services for the same thing.
Logging in with Google or Facebook or any other third party service is probably the biggest problem with traditional apps. Perhaps more so than them storing your data. Sure, they can (and have sold user data), but if these providers are the owners of your digital identity, they also control whether or not you have access.
Slack, Twitter, Google, et al have been known to lock people out of their accounts without warning.
edit: sorry for reply to wrong post. Should have responded to jhunter1016 below.
if Bitcoin was under 51% attack, then we would simply accept the name state on the best fork. To learn more about how we would handle this case, you can look here: https://forum.blockstack.org/t/bitcoin-network-disruption/13...
Blockstack Core implements BNS and Atlas, the storage routing system for Gaia. Blockstack Core nodes form the backbone of the Blockstack network. Each node indexes the Bitcoin blockchain and maintains a full replica of all names, public keys, and storage routing information. This makes the Blockstack network particularly resilient to node failure---applications only need to talk to a single Blockstack Core node to work, and a new or recovering node can quickly reconstruct all of its missing state from its peers.
All Atlas nodes lie on top maintain a 100% state replica, and they organize into an unstructured overlay network. The unstructured approach is easier to implement, has no overhead for maintaining routing structure and is resilient against targeted node attacks. When a new Atlas node boots up, it first gets the index of all data keys and hashes of values stored in the blockchain. After getting the index, Atlas nodes talk to their peers to fetch key/value pairs they dont have. The Atlas network implements a K-regular random graph.
Let us know if you have any more questions.
Does blogging need block chain? Can't you be decentralized and encrypted without BC? From what I'm aware, the benefit of BC is that you get an audit-able history. Do we need that here? Like I get that it can serve as a backup, but does that work in practice? By using BC here can I roll back my blog (like in git)? And do you really need a full history? Couldn't you do just like 10 revisions? I'd even argue that a complete history could be dangerous.
This is a fundamental question that I have with block chain. It seems really cool, but from what I understand, there are other tools that solve these problems, don't require as many resources, and work faster.
Am I wrong in this? If so can someone explain?
If I'm right, can someone expand?