[License-review] For Approval: The Cryptographic Autonomy License

Bruce Perens bruce at perens.com
Fri May 10 21:29:26 UTC 2019


Holochain is a blockchain financial system (and may be other sorts of
blockchain things), and the typical user pays or receives funds and
interacts with other users through the program, with their output
distributed to *all users, *as is typical for blockchain. So, they are
potentially performing to everyone and at least performing to whoever they
directly connect to, and they have received data of anyone who put data
into the blockchain before their transaction.

In the case of Holochain, compliance may be fulfilled by simply
distributing the entire blockchain to the public. Which you had to do
anyway, blockchain isn't any good if people don't pass it on.

In the case of any other software under the CAL, we have no guarantee what
the scale of the technical and legal burden of compliance is.

> I guess I didn't note that portion. But in general, something being
difficult to access does not seem like it would excuse non-compliance.

This is the lack of sympathy for the user which I am having a problem with.

> Can you explain more of what you mean about "hard to access"? In
practice, the data portability provision is mostly applicable in the SaaS
context, where you also have a registered account associated with any
provided material. That is the 99.9% common use case.

No, we can't explain this reliably, because we don't know what kind of
software will exist under this license. So, you are asking for a forecast.
You are assuming that with 99% probability the operator is SaaS, has a
significant income from the business, and can raise the resources necessary
for compliance. We can have no guarantee that this is the case.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20190510/46815afe/attachment.html>

More information about the License-review mailing list