(Here's the transcript taken from the Rodeo Repeater Event, local chat was removed.)
PART 1
Cory Linden: ok, I suspect that we have a lot of ground to cover, so why don't we get going?
Torley Torgeson:
Cory Linden: I have some general comments from the various blog discussions
Cory Linden: that we'll hit first and then we can talk about issues
Cory Linden: the idea being that we'll do the usual Q&A but stay on specific issues longer than usual
Cory Linden: First off, a bit of background as to why we're talking about changing permissions
Cory Linden: and it isn't because we want more stuff to work on
Cory Linden: the first concern is the legal one . . . right now you all have real world copyrights in your creations
Cory Linden: but the current permissions aren't actually forcing buyers/recipients to agree to licenses that match the abilities granted within the license
Cory Linden: as we grow and you all are creating items of greater and greater value, more and more issues could appear
Cory Linden: such as - you want to make a graphic novel of your avatar, sell a chair design to Design Within Reach, etc
Cory Linden: so we need to make changes to clean up the legal issues
Cory Linden: Second, the current persmissions are strongly biased to the creators (this will be a topic of discussion I suspect)
Cory Linden: but economic growth and innovation, two absolutely critical pieces of SL's long term success
Cory Linden: have historically tied to the cost of information
Cory Linden: this is an important concept, ok?
Cory Linden: cost of information determines how quickly innovations occur and the more limits that are placed on information transfer
Cory Linden: the more innovation is slowed
Cory Linden: slower innovation is bad for Second Life.
Cory Linden: If you look at the historical roots of intelletual property law in the US (and around the world)
Cory Linden: they are always a balance between limited monopolies for creators (which means that creators can sell there stuff for more)
Cory Linden: and the societal good of shared information.
Cory Linden: All of these stresses apply to SL as well.
Cory Linden: So, we wanted to look at how to find a better balance between creators and consumers than we currently have.
Cory Linden: In looking at this, we focused on fair use and the right to tinker.
Cory Linden: We saw an opportunity to allow the buyer to make choices about whether they wanted the rights that
Cory Linden: are usually keyed to first sale doctrine -- such as the right to resell or give away something -- and fair use rights
Cory Linden: like modification, tinkering, &c.
Cory Linden: So, that's the general background. I assume that you've all been on the blog, so let me run
Cory Linden: through some of the questions quickly
Cory Linden: <takes breath>
Cory Linden: everyone brought up the critical nature of a smooth transition and converting content from the old to the new system
Cory Linden: Part of the reason that we're talking about this so early is to ensure that we can do that
Cory Linden: I don't have a full proposal for conversion yet (mainly because I suspect that your feedback will cause changes to the proposal)
Cory Linden: But a quick first pass looks something this
Cory Linden: nomod/nocopy/trans => (c)
Cory Linden: nomod/copy/trans => cc
Cory Linden: mod/nocopy/trans => cc
Cory Linden: mod/copy/trans => cc
Cory Linden: note that several of these become more restrictive, but that is balanced by the wrapper concept and its ability to tweak stuff you own
Cory Linden: the tricky cases are the "no transfer" cases of mod/copy/notrans and nomod/copy/notrans
Cory Linden: the new plan doesn't actually have a "no transfer" permission (which I think that we'll talk about)
Cory Linden: so the situation would likely be that those would become (c) + no transfer, a special case for old content
Cory Linden: this is a good moment to talk about no transfer.
Cory Linden: Several of you brought this up and it is an interesting question. Right now, the plan is to not have that permission anymore.
Cory Linden: In thinking about it, we were thinking about real world rights and it seemed like a far more natural fit that if you owned something you could pass it along.
Cory Linden: Will propogation into sub parts (the creator changing permissions) be supported?
Cory Linden: Yes
Cory Linden: Right now the plan means that you can't make unique objects anymore. Several of you raised good points about that.
Cory Linden: The tension is that unqiue objects break some of the fundamental properties that make digital items, well, digital.
Cory Linden: However, I understand that games, collectables, &c are important, so there are some options
Cory Linden: such as the scripting language being able to detect broken wrappers, hashes, &c.
Cory Linden: Should creators be able to create anonymous content in SL? I don't think so, but it is an interesting question. Basic Chair: Right click me and choose 'Sit Here' to sit down
Cory Linden: One final bit, then we;ll open things up.
Cory Linden: Not all licenses play nicely with each other.
Cory Linden: The most obvious example is the GPL which, by its nature, tends to "infect" other content that it touches. We had originally planned to offer GPL rather than BSD, but
Cory Linden: since it doesn't integrate cleanly with Creative Commons, that was a non-starter.
Cory Linden: There is also a possiblity that CC as written can't be used within SL (long legal discussion that is somewhat beyong this meeting) but a modified version of CC would work.
Rathe Underthorn: it is for the betterment of us all
Rathe Underthorn: if we stand together
Cory Linden: Rather, could you wait until I'm done, please? ALso, could you sit down?
Cory Linden: Rathe, that is
Cory Linden: Thanks!
Cory Linden: moral rights are another issue
Cory Linden: in some nations, the creator has the right to determine how her creations are used
Cory Linden: ok, that's the overview and list . . . before we get started and the fur and pixels start flying, I'd like to thank you all for caring about this.
Cory Linden: These are complicate issues that don't have obvious or simple answers. Your participation speaks to your thoughtfulness and intelligence.
Cory Linden: So, Haney do you want to hand off questions?
Haney Linden: so that everyone doesnt talk at once, please IM me and we'll go in turn
Haney Linden: Tiger Crossing: Point on scripts detecting broken wrappers and disabling objects that would allow cheating at games (etc)... This may need to be incorportaed into the breaking ritual: "Breaking the wrapper may disable or damage this obejct. Do you want t
Haney Linden: Do you want to continue?"
Cory Linden: THat's an excellent point. Clearly the "Wrapper Breaking" event is important and needs to be made clear to the owner.
Skunken Gascoigne: Unfortunately, I'd like to discuss, but I have to go. A pity that this town
hall had to happen just minutes before my Weight Watcher's meeting. x_x G'bye.
Cory Linden: James Grimmelmann of LawMeme had a good point as well
Cory Linden: He suggested thinking about the "wrappers" as mattress tags that you can tear off.
Cory Linden: Although in this case the mattress police won't come and invade your home.
Max DeGroot: *snicker*
Haney Linden: Oz Spade: A question is raised about having all items transferable, if someone makes a vehicle and sells it, coudln't someone turn around and resell or give away for free that vehicle?
Cory Linden: So, in the real world, if I buy a car from you, I can resell it or give it away. In SL (perhaps) you also have the ability to modify it or copy it.
Cory Linden: So the idea is that the buyer can either preserve the ability to give it away *or* they can copy it/modify it. (For full (c) permissions)
Haney Linden: Tiger Crossing: Can permissions remain seperate on linked objects, to be later pulled apart, or willlinking "fuse" them together, with a lingering taint after separation?
Cory Linden: I like the "tainted permission" concept . . . that's a great question and I don't know the correct answer yet.
Cory Linden: The intial feeling was that fusing them was simpler but several folks on the blog have shown examples of why keeping them distinct would be useful.
Cory Linden: I suspect that we'll end up more on the hierarchical side.
Haney Linden: Jennyfur Peregrine: Will there be a new function in the permissions settings that allows the texture to be locked so a clothing item can be modified but the texture will not show so that no one can take a screen shot and rip the work off?
Cory Linden: That's a great question. Obviously, any texture that gets displayed can have a screen shot taken.
Cory Linden: This is the "analog hole" in the real world of DRM and copy protection.
Cory Linden: I think that we can take steps to discourage people. You: Have a seat and get comfortable...
Cory Linden: However, you can't completely stop this . . . you can just do things that make the screen shot lower quality.
Haney Linden: CrowCatcher Valen: any plans on a URL blocking tool so people cant take the stream from your land?
Cory Linden: oh, so you want to stream to yourself but not to others?
Haney Linden: CrowCatcher Valen: no CrowCatcher Valen: people can take streams we pay for
Haney Linden: CrowCatcher Valen: we dont want them too CrowCatcher Valen: now anyone can
Cory Linden: oh, wait, I see you want to make it so that only people on your land get it
Cory Linden: the problem, of course, is that if you are streaming at them, they can sniff the packets to see where it's coming from
Haney Linden: CrowCatcher Valen: so that it's not visable, sorry
Cory Linden: but I agree that hiding the url makes that harder
Cory Linden: sort of a similar problem to the texture question.
Haney Linden: By the way, if you are here you can chat out followups to your own questions
Cory Linden: these are both examples of the core issues, right? Digital data is easy to move around, copy, &c.
Cory Linden: The internet is good for moving it and computers are good at rendering it.
Cory Linden: But, free markets are built on the tension between property rights and information cost, so we're trying to find the best balance.
Haney Linden: Kathy Dayton: With this change,, will it still be possible to buy gifts for people and transfer them (for example offlline)?
Cory Linden: Sure, first sale is preserved unless you want to copy a (c) item or modify it, then you lose the ability to transfer it.
Haney Linden: Bakuzelas Khan: if you take away no transfer, if people can transfer, people will buy stuff cheap and sell it again for high prices - so everyone will have to charge crazy prices for stuff to prevent that and make sure they get a fair deal.
Haney Linden: Bakuzelas Khan: If people can see a low quality texture of the work, then they will just make a low quality knock off of it and try to get a refund from you, or sell it to someone else claiming it's made by you.
Cory Linden: To the first question, I'm not sure that I agree. If I can buy a shirt for $10 or $100 (and it's the same shirt) then I'll pick the $10 shirt, right?
Cory Linden: I agree that more features to find and sell items are an important piece in making that decision.
Haney Linden: Bakuzelas Khan: If people can see a low quality texture of the work, then they will just make a low quality knock off of it and try to get a refund from you, or sell it to someone else claiming it's made by you.
Haney Linden: sorry
Haney Linden: Bakuzelas Khan: but how will they know? lol
Cory Linden: this goes to the question of finding things in world. I don't want to get too far afield, but that is clearly important. Again, information flow is a good thing.
Cory Linden: To your second question, clearly "copying by inspection" is a problem (just like the real world).
Cory Linden: However, if there is good information flow, I know that better quality items sell for more than cheap knockoffs (again, like the real world)
Haney Linden: Leran Charlton: Haney, Im concerned as a merchant that furniture I make such as chairs can simply be copied for more. How does this affect my ablilty to sell my product? If I make a dining set containing 4 chairs, the buyer need only buy one and make
Cory Linden: This is a good question and I don't have an immediate answer . . .
Cory Linden: I wish I could just say "ok, creators can control how many copies are made" but I am concerned
Cory Linden: that everyone will just make that choice and ultimately decrease learning and innovation inside SL
pancake Stryker: whats up here
Cory Linden: But I agree that we need to debate that question very carefully because I understand the issue
Cory Linden: I guess the question back to you is: "Can you just sell the set of 4?"
Haney Linden: Cid Jacobs: what happens to items that r previously sold with copy permission, will they be given transfer as well? if so that will put me out of biz
Cory Linden: wait, can I get an aswer from Leran?
Basic Chair: Right click me and choose 'Sit Here' to sit down
Cory Linden: who's not even here I guess
Cory Linden: ok, cid . . .
Cory Linden: no
Cory Linden: one option is that they become cc or (c) and lose copy, but the owner can break the wrapper to regain the copy permissions (and lose transfer in the process)
Cory Linden: The other option for stuff already out there is to respect current permissions and to allow migration to appropriate new permissions
Cory Linden: this would allow creation with old stuff and slowly phase out the old permissions
Haney Linden: Leran Charlton: Haney, selling it as a set of 4 is fine and can certainly be done, but, not everyone wants 4 chairs. especially if they have a small place
Cory Linden: OK, so we're not going to decide on the unique item question this instant. The thing for the creators to think carefully about . . .
Cory Linden: is whether uniqueness is really a good thing or not . .. I know that many of you already allow copying because it's what your customers want
Cory Linden: after all, your customers want more freedoms not less
Haney Linden: Gwyneth Llewelyn: ask Cory about "co-creation" ie. having a prim/texture/script authored by different people and/or groups. What I read on the blog was not clear to me on how "co-creation" will be implemented or propagated.
Cory Linden: right, that isn't clear yet, although its related to the linked question
Cory Linden: short term, there will probably need to be a single "creator" even if that person allows multiple people (in a group for example) to edit the item
Cory Linden: it it different pieces combined, then this goes back to one wrapper or many, which I agree we all need to consider (especially the tradeoffs between simplicity and completeness)
Haney Linden: Fargon Millhouse: Reverse engineering is a problem in the Real World...how can you assure owners of intellectual property that this will not be dont in SL....since you can choose to "break" the wrapper, copy and redistribute?
Haney Linden: Fargon Millhouse: also.........I often PAY (IN RL & SL) a programmer to develop scripts which I then own and intend to copyright...can you explain how this will work..since I am a bit fuzzy on this right now...
Cory Linden: First question . . . Cory Linden: I can't assure you of that. The current permissions system doesn't and the real world doesn't. What I can assure you is
Cory Linden: you have legal recourse (just like in the real world)
Cory Linden: oh, wait, just noticed a misunderstanding . . .
Cory Linden: if you break the wrapper, you lose the ability to redistribute . . . that's one of the core ideas
Cory Linden: trading off freedom to tinker with first sale concepts
Cory Linden: however, laws and societal norms are ultimately way better at dealing with infringement
Cory Linden: on the second question, if you make a contract with the programmer in the real world then you're set
Cory Linden: they give you the text and you make the (c) script
Haney Linden: Kim Anubis: Q: So you're essentially going to force us to put a "site license" on our creations?
Cory Linden: I'm not sure what you mean by that . . .
Cory Linden: we currently allow you to keep a full (c) on everything that you make in world
Haney Linden: Kim Anubis: You can't use multiple copies of a program you buy at once, irl
Haney Linden: Kim Anubis: You can't use multiple copies of a program you buy at once, irl
Cory Linden: well, right now if you by something with no copy set that's what's being enforced
Cory Linden: the new system allows your customer to choose if they want the freedome to tinker with or copy the item.
Haney Linden: Kim Anubis: but here, you're talking about making everying copyable Kim Anubis: so one chair seats 12 or 20 Kim Anubis: one scripted item could be used by the owner on 10 parcels Kim Anubis: etc. Kim Anubis: at the same time.
Cory Linden: That's the current proposal, yes
Cory Linden: However, once they decide to use that option, they are losing the ability to resell the chairs, give away the script, &c
Cory Linden: Much like IP in the real world, we need to make decisions about what the best path is for our world.
Cory Linden: The real world has opted for "strong copyight"
Cory Linden: unfortunately, history has shown that strong copyright hurts innovation, hurts markets, hurts technology growth and hurts customers.
Cory Linden: We have an opportunity to do better.
Haney Linden: Jillian Callahan: Q: On a script with a "broken wrapper", is there anything that would prevent copy-paste outright duplication?
Cory Linden: The (c) scripts never show their text for exactly that reason.
Cory Linden: Again, a tradeoff
Cory Linden: buyers can choose to buy scripts that they can see because learning the scripting language is important to them.