4 ms·

Those are properties of Git, indeed. The difference is in the "in this way" part of the sentence. I've written a lot about what we are doing and why and the pro

Those are properties of Git, indeed. The difference is in the "in this way" part of the sentence. I've written a lot about what we are doing and why and the proof is in the puddin', MSL is available to download and run in our Nebula product. Here's the website with full documentation and downloads. http://nebula.mimix.io http://nebula.mimix.io

basch 5y ago
Admittedly having only given the whitepaper a brief scan, I have two questions. Is it distributed, or are you hosting the whole instance yourself? Does it use any other academic component of the bitcoin suite besides linked logs? https://queue.acm.org/detail.cfm?id=3136559 https://queue.acm.org/detail.cfm?id=3136559 I ask because a hashed merkle tree probably isnt what comes to everyone's mind when they hear blockchain, even if it is the literal definition. The author of the article is using it to be a distributed ledger between untrusted parties. If your product isnt that, its sort of an apples to oranges comparison to say you have a use case for something different than what he is dismissing.
- mimixco 5y ago
  Thank you for those excellent questions! The entire tech is open source and can be used on-premise, in the cloud, or in any kind of hybrid. Today, we are offering Nebula which is an integrated engine and viewer with no outside dependencies, but everything is there for anyone to deploy it on a server and separate the parts. It's designed for that. Coming very shortly are MSL Notebook and MSL.js which are UI components and a Typescript library for working with MSL and adding it to your own apps, wherever they live. We also have a "headless" MSL engine that lives in the cloud which will soon be public so you can play with it through MSL Notebook or use it to test and develop your own apps. We are not using Bitcoin or any component of it. Our idea is based on the old skool meaning of "blockchain" in that it is a chain of records whose order can be proved by hashing. That is the only component of the blockchain concept that applies here. We use it to hash individual edits within a document, as opposed to hashing entire documents.
- mimixco 5y ago
  I see your edit so let me address that also. Yes, our use for the blockchain is to provide verifiable information to untrusted parties. Instead of information about transactions and balances, it's information about text edits. In a simple scenario, every edit you make to a document is recorded individually and hashed with the hash of the previous edit. This forms the chain. The chain itself can be stored anywhere. It's useless if you don't have the document. But if you do have the document or any fragment, you can instantly tell what version you have and if it has any differences from the original -- without seeing the original.

basch 5y ago

Admittedly having only given the whitepaper a brief scan, I have two questions. Is it distributed, or are you hosting the whole instance yourself? Does it use any other academic component of the bitcoin suite besides linked logs? https://queue.acm.org/detail.cfm?id=3136559 https://queue.acm.org/detail.cfm?id=3136559 I ask because a hashed merkle tree probably isnt what comes to everyone's mind when they hear blockchain, even if it is the literal definition. The author of the article is using it to be a distributed ledger between untrusted parties. If your product isnt that, its sort of an apples to oranges comparison to say you have a use case for something different than what he is dismissing.

mimixco 5y ago
Thank you for those excellent questions! The entire tech is open source and can be used on-premise, in the cloud, or in any kind of hybrid. Today, we are offering Nebula which is an integrated engine and viewer with no outside dependencies, but everything is there for anyone to deploy it on a server and separate the parts. It's designed for that. Coming very shortly are MSL Notebook and MSL.js which are UI components and a Typescript library for working with MSL and adding it to your own apps, wherever they live. We also have a "headless" MSL engine that lives in the cloud which will soon be public so you can play with it through MSL Notebook or use it to test and develop your own apps. We are not using Bitcoin or any component of it. Our idea is based on the old skool meaning of "blockchain" in that it is a chain of records whose order can be proved by hashing. That is the only component of the blockchain concept that applies here. We use it to hash individual edits within a document, as opposed to hashing entire documents.
mimixco 5y ago
I see your edit so let me address that also. Yes, our use for the blockchain is to provide verifiable information to untrusted parties. Instead of information about transactions and balances, it's information about text edits. In a simple scenario, every edit you make to a document is recorded individually and hashed with the hash of the previous edit. This forms the chain. The chain itself can be stored anywhere. It's useless if you don't have the document. But if you do have the document or any fragment, you can instantly tell what version you have and if it has any differences from the original -- without seeing the original.