Linux Lingam <[EMAIL PROTECTED]> writes:

> 
> [SNIP]
> 
> >
> > So if the uploader's beautiful, Osho-nice naturescapes bliss out video
> > becomes a background to a toilet paper advert, he can still give the video
> > out to others via blip.tv or whatever - he just can't do it from Youtube.
> 
> HAHAHAHA! splendid anal-ogy... PJ, leading to sudden creative-commons
> and muft and mukt enlightenment. 

I thought I was just papering over the cracks in the argument.
Butt enough. These innuendos are rearly scraping the bottom.

> [snip]>
> > Anyway, probably a sensible way to distribute content would be for the
> > uploader to put up some content on Youtube, and a superset of that content
> > on blip.tv (and suggest on Youtube that people pick up the full content
> > from blip.tv).
> 
> depends on the creativecommons-license.
> if i publish under a cc-by-nd-sa 3.0 license,
> or a cc-by-nd-nc 3.0 license,
> these automatically break the youtube EULA.

The impression you give from this is that once you give your original content
from your machine to youtube, then give the same original content from your
machine to blip under those cc-* licences, you break the youtube EULA.
That's not so. Even if the digital content is exactly the same, the youtube
EULA is *not* broken by this. 

(On the other hand, for clarity: You would break the EULA if you sourced
the content from youtube and then put it in blip under those CC-*s. Even if
the digital content were exactly the same.

I don't know if youtube adds its own bits to the content and locks it that
way though).

 
> to take this discussion forward, PJ, see you at freed.in in february 2008.
> http://freed.in

Yeah, maybe I'll manage to find your talk this time ;-)




_______________________________________________
ilugd mailinglist -- ilugd@lists.linux-delhi.org
http://frodo.hserus.net/mailman/listinfo/ilugd
Next Event: http://freed.in - February 22/23, 2008
Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi 
http://www.mail-archive.com/ilugd@lists.linux-delhi.org/

Reply via email to