[cc-community] Identi.ca - my new Creative-Commons-enabled microblogging service

Matthew J. Agnello matt.agnello at gmail.com
Mon Jul 7 20:25:12 EDT 2008


Terry Hancock wrote:

> "Force" is a curious term to use here. If you don't like the "By"
> license, then don't use the site, it's as simple as that.
>
> Having a single license makes the site useful to the reader/user of the
> material. This is destroyed if you don't require a certain license of
> people who post (and remember that ALL SITES impose _some_ kind of
> license on you, or they couldn't publish your work legally).


Definitely true. But remember that Twitter, as an example, doesn't claim any
ownership to your content. It's yours the same way that a video you upload
to YouTube is yours, with all the little "we can republish this so other
people on the Internet can see it" clauses. So, for practical purposes,
there are as many licenses on Twitter as users, since every user owns his or
her Twitter feed, and as far as I know there haven't been any IP problems.

There might be in the future, though. We'll see.

The point being, a site can operate with multiple content licenses, so the
question becomes, what's the advantage of using just one? As you said, one
is to the user of the material: you know what you can do with it, and you
don't have to hunt around for that information. Also, it sets a tone
(subtly) for the purpose of the site. You don't want to post 140 character
chunks of the poetry you'd like to publish and make money off of to
identi.ca. You should use it for things you don't want to hold onto, because
the site license doesn't let you hold onto it. A site that lets you choose a
license for your feed would have a different purpose.

So I suppose there really is no "best" license for microblogging. It just
depends on the purpose of your microblogging site.

// Matt

--
Matthew J. Agnello
http://hungryfilmmaker.com/

On Mon, Jul 7, 2008 at 1:53 PM, drew Roberts <zotz at 100jamz.com> wrote:

> On Monday 07 July 2008 14:57:31 Rob Myers wrote:
> > Matthew J. Agnello wrote:
> > > For me, BY is fine; I really just want more data portability
> > > out of identi.ca <http://identi.ca>, since I currently use Twitter.
> So,
> > > keep up the great
> > > work, Evan!
> >
> > I am a very strong proponent of copyleft but I think identica's use of
> > BY is a perfect fit for:
> >
> > a) Data portability in a federated network of microblogging sites.
> >
> > b) Quoting and replying to other people's comments.
>
> One of the problems I see is actually quoting something from outside of the
> system.
>
> So, would it be possible to adopt a convention that anything in quotes in
> not
> under the BY license? With a possible addition of a license code in
> brackets
> after the quote? (after the first quote?)
>
> Another is quoting myself from a work intended as a whole to be under a
> different license.
>
> This concern could just be due to my ignorance so here is a hypothetical:
>
> I have a song lyric, three verses and a chorus. License; cc BY-SA.
>
> Over time, I end up quoting the whole thing but only ever one line at a
> time.
> So single lines are BY but the song is BY-SA. Can someone take all of the
> BY
> licensed lines and treat the song as BY? Or is the ordering of the lines
> covered by the BY-SA even though all the lines on their own are now BY? (Is
> this clear?)
> >
> > So I'd go so far as recommending that standard copyright be dropped
> > rather than more licences be added, but I can see the pragmatic reasons
> > for keeping it.
> >
> > identi.ca is absolutely brilliant.
> >
> > - Rob.
> >
> > PS -Danny o'brien mentioned identica as an example in his talk about
> > freeing the cloud at OpenTech in London last Saturday.
>
> all the best,
>
> drew
>
>
>
> _______________________________________________
> cc-community mailing list
> cc-community at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/cc-community
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ibiblio.org/pipermail/cc-community/attachments/20080707/de85d198/attachment-0001.htm 


More information about the cc-community mailing list