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

Bruce Perens bruce at perens.com
Fri May 10 21:48:09 UTC 2019

On Fri, May 10, 2019 at 2:19 PM VanL <van.lindberg at gmail.com> wrote:

> I am not sure how to respond when the hypothetical is "I am a person
> providing a network service, but I have no idea what I am doing, and I
> won't ask for help, so I might do something wrong."

Your customer is implementing a blockchain as a distributed service in
which all users interact peer-to-peer or broadcast (one-to-everyone).  All
are providing a network service, simply by spending the money in their
cryptographic wallets or making income. They are all just users. There is
no central operator theorized for Holochain.

And it's not that they are *afraid *to ask for help. It's that they can not
afford the help.

The license can be used in other contexts, besides Holochain, where the
user naively offers a network service simply by running the program

I'll reiterate: For the ordinary developer, the CAL means:
> 3) a copy of any of the data used with software that the person has given
> to you, should that data still be available.

 This is entirely assuming that the software is not used in a networking
context where users are peer-to-peer. In that case they can not be assumed
to know what the data is or what their obligations are.


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

More information about the License-review mailing list