4 ms·

> A CRM built in this way might enable multiple "thin clients" to build and an ecosystem to develop around it. Let's parse this. CRM = customer relationship m

by mayank 8y ago

> A CRM built in this way might enable multiple "thin clients" to build and an ecosystem to develop around it. Let's parse this. CRM = customer relationship management, usually in the context of sales. The sales relationship is often hard won and closely guarded, because it makes people money. You're proposing putting information about this relationship on a public blockchain (because a "private blockchain" here is just an internal database), so not only is this highly guarded customer data now public, but it's also open to other relationship management platforms to manipulate? What am I missing? Because this seems like a spectacularly bad idea for anyone who has actually done any sales. I think you owe it to yourself as a blockchain "believer" to play your own devil's advocate and try to first figure out conventional solutions to the problems you believe that the blockchain solves.

chrisco255 8y ago
I did not say public. Private blockchains are a thing. And it's not just an internal database. They are forkable and potentially run by the customer themselves or in their own AWS private cloud or wherever. But by following the protocol, they could easily switch providers, or integrate several clients that provide different features around the same data. The customer can truly own their data and the side chain can interact with the main chain where it makes sense. Lots of technical problems there, that's why I say it's a ways off. But it's all doable.
- MBCook 8y ago
  Why would a customer fork their own blockchain? If it’s not public what’s the point of using a blockchain? How is it not just a secured database? Databases can be moved between providers. You can choose where/how to interact with them.
- mayank 8y ago
  > But by following the protocol, they could easily switch providers, or integrate several clients that provide different features around the same data. What you're suggesting is solvable by an open data standard and export/import features on software. A blockchain provides none of those by virtue of being a blockchain.

by mayank 8y ago

chrisco255 8y ago

I did not say public. Private blockchains are a thing. And it's not just an internal database. They are forkable and potentially run by the customer themselves or in their own AWS private cloud or wherever. But by following the protocol, they could easily switch providers, or integrate several clients that provide different features around the same data. The customer can truly own their data and the side chain can interact with the main chain where it makes sense. Lots of technical problems there, that's why I say it's a ways off. But it's all doable.

MBCook 8y ago
Why would a customer fork their own blockchain? If it’s not public what’s the point of using a blockchain? How is it not just a secured database? Databases can be moved between providers. You can choose where/how to interact with them.
mayank 8y ago
> But by following the protocol, they could easily switch providers, or integrate several clients that provide different features around the same data. What you're suggesting is solvable by an open data standard and export/import features on software. A blockchain provides none of those by virtue of being a blockchain.