Development of Creative Commons licenses

[drew Roberts <zotz AT 100jamz.com>]

On Fri, 10 Aug 2012 14:25:59 -0400, Anthony <osm AT inbox.org> wrote:
> On Fri, Aug 10, 2012 at 12:49 PM, Gregory Maxwell <gmaxwell AT gmail.com> 
> wrote:
>> On Fri, Aug 10, 2012 at 8:57 AM, Anthony <osm AT inbox.org> wrote:
>>> Yes, this is worth pointing out.  Through a quick look the restriction
>>> appears to be "You may not restrict the ability of a recipient of the
>>> Work from You to exercise the rights granted to that recipient by the
>>> terms of this Public License, including through the imposition of any
>>> effective technological measures."
>>>
>>> Still, I think the question of "can I distribute the work using
>>> https??" applies.
>>
>> I'm not sure how we can have a productive conversation starting from
>> this kind of basic misunderstanding.
>>
>> There is simply nothing in the text of the license which I can see
>> would allow someone to draw the conclusion that distributing content
>> in HTTPS would be problematic.  Please help me understand how you're
>> coming up with that— and perhaps we can hammer out some little tweak
>> that prevents that kind of misunderstanding that we can suggest.
> 
> The quote is right there.  HTTPS is a technological measure.  I'm not
> sure what "effective" means, so I don't know if HTTPS is "effective"
> or not.
> 
Party 1 send an unprotected file to party 2 via https or scp. It goes
in one end unprotected and comes out the other end the same way. The
protection is against third party snooping on the transfer, it does not
make it so that party 2 has reduced abilities with respect to party 1
because of the use of https or scp.

all the best,

drew