[License-review] For approval: The Cryptographic Autonomy License (Beta 2)

[Bruce Perens]

Josh,

OK, you are trying to say that the user stupidly trusted their geospatial
data to you, and you won't give it back, and that's the problem the
software license should protect the user from.

At the risk of being flip, it's not our responsibility to protect the user
from their own conduct. In a broader context, there is a perception that
the user can not function in modern society without providing their data to
software-as-a-service providers, and they can't do so in a way that they
could retain a copy or get it back by themselves. But I am still having a
hard time seeing their incapability of preserving their own access to their
own data as a factual statement.

On Thu, Aug 22, 2019 at 2:18 PM Bruce Perens <bruce at perens.com> wrote:

>
>
> On Thu, Aug 22, 2019 at 1:41 PM Josh Berkus <josh at berkus.org> wrote:
>
>>
>> As an example, imagine that I have a geodata processing program, which I
>> support by running a hosted version, and all user data is PK-encrypted
>> using a key only I control.  If the software is under the GPL (because
>> it depends on, say, PostGIS), the user still doesn't have the freedom to
>> run the software themselves unless they are willing to recreate all of
>> their data.  The CAL would protect user freedom in this case.
>>
>
> Maybe I will understand this if you state it better. It sounds like you
> own the data, it's under your key, and you are arguing that if you used
> another license you would be forced to provide the data to others, and that
> this would be a good thing. One would think that the user would have the
> freedom to create their own geospatial data as you did. The way you state
> it, it sounds like the user should have a right to work that you did,
> arbitrarily. Perhaps you can explain this more clearly?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensource.org/pipermail/license-review_lists.opensource.org/attachments/20190822/b61b2e3c/attachment-0001.html>