Re: [mmox] mmox Digest, Vol 1, Issue 45

Jesrad <jesrad@gmail.com> Thu, 19 February 2009 10:57 UTC

Return-Path: <jesrad@gmail.com>
X-Original-To: mmox@core3.amsl.com
Delivered-To: mmox@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 49BCC28C210 for <mmox@core3.amsl.com>; Thu, 19 Feb 2009 02:57:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W999S32NHwY0 for <mmox@core3.amsl.com>; Thu, 19 Feb 2009 02:57:37 -0800 (PST)
Received: from mail-bw0-f161.google.com (mail-bw0-f161.google.com [209.85.218.161]) by core3.amsl.com (Postfix) with ESMTP id A4EDC28C20C for <mmox@ietf.org>; Thu, 19 Feb 2009 02:57:36 -0800 (PST)
Received: by bwz5 with SMTP id 5so912259bwz.13 for <mmox@ietf.org>; Thu, 19 Feb 2009 02:57:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=xSfoGxXOT2iQP0vUGMnuL+5ObkhJBTC0G1BHi5AAj58=; b=pVuhhaLgn/wHS9N9UmvWYfi9Ca+xCTg/4Zva6XButnXfPygov4heh8UcFaYGvQQcNb B/BaBSmEw03NvKV3TGiwMKy0XW98zq/qhumUUr3ZwhFD8oGrzzznkd21e+FmGIRkoeFB toZBwd88nb5ImCKf5eiVxBb5o1dJWbITGogPM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=RjqMcntjot0K3e1WhS8iZUPtELpdiZmJJLmNFhf5c4tLA+aPBe71R+nNq7MB7bDa8l NswlvYamAsou2yWUW+czGuMEcAv5Ku0iMMCIZQcWbPOjMocSXT0PhcwmsPQUu3bZP59s DxGwxdQou+O2FxS9lj6xv/J1C5hNp2Q856zJw=
MIME-Version: 1.0
Received: by 10.181.201.18 with SMTP id d18mr160689bkq.125.1235041067969; Thu, 19 Feb 2009 02:57:47 -0800 (PST)
In-Reply-To: <20090219.014758.23973.0@webmail04.vgs.untd.com>
References: <20090219.014758.23973.0@webmail04.vgs.untd.com>
Date: Thu, 19 Feb 2009 11:57:47 +0100
Message-ID: <53cd6c2e0902190257u37e957e7se4f208975dfadd64@mail.gmail.com>
From: Jesrad <jesrad@gmail.com>
To: mmox@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [mmox] mmox Digest, Vol 1, Issue 45
X-BeenThere: mmox@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Massively Multi-participant Online Games and Applications <mmox.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmox>
List-Post: <mailto:mmox@ietf.org>
List-Help: <mailto:mmox-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmox>, <mailto:mmox-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Feb 2009 10:57:38 -0000

Just a few remarks:

On Thu, Feb 19, 2009 at 7:47 AM, dyerbrookme@juno.com
<dyerbrookme@juno.com> wrote:
> At one point, some AWG members introduced a JIRA (feature proposal wiki) motion to have a check-off box on SL-made objects offering consent or non-consent for an object to travel to other grids. There was a heated discussion about this and the author withdrew the proposal, regrettably:
> http://jira.secondlife.com/browse/MISC-1272

I expect that interoperability/conversion of content from one grid to
the other will be limited by technical constraints so it won't apply
broadly and suddenly, but the point remains that some way to prevent
that conversion on behalf of the owner of it should exist. Though here
we disagree philosophically on exactly who this owner is and how,
that's something I can fully get behind. I certainly wouldn't like it
if my newest model of airship was disclosed with full-permissions and
copied over to a third-party sim simply because someone from the
OpenGrid TPed to my sim and had a look (that includes looking through
a sim border) while I was working on it.

> You're also suggesting that users who "care about interoperability" should "choose not to purchase that content" -- i.e. you're essentially demanding that creators share their content into grids that do not protect their IP, or face boycotts if they don't go along with this forced march. What's that all about?

I think this was more a statement of fact than one of ideological
position, really. The resident chooses what client software runs on
his/her machine and how, it cannot be trusted to respect
legal/contractual bounds by technique, and that's got nothing to do
with how the server software works - and the point here I think is
that the same applies to server operation with regards to
interoperability protocol. This is akin to international agreements
between sovereign states: neither side has the authority to reasonably
enforce them over the other. And merely stating that they should
ideally limit themselves to bounds they are eager to respect is not
the same as saying that all international agreements are to be
considered void from the get-go.

That said, yes, welcoming visitors from third-party grids and selling
them things, that should be and remain the resident's ultimate choice.
But that's an implementation detail for LL to build into their code,
so it's probably out of the scope of this discussion list.

> (Creative Commons follows much the same logic, making it possible to opt for a license to offer your creations to be copied for credit, but not opt for a license to copy for cash, and urging everyone to give away content for free, and not making a mechanism to get paid for content, i.e. integrating micropayments with content distribution as SL does).

I'm not sure what you mean here by "mechanism to get paid for
content". For months already I've been getting paid as an independant
content provider in SL for creating full-perm works. I have the exact
opposite claim to yours: my CC-like license cannot be enforced
correctly due to the permissions system in SL, and that's disrupting
my trade to a fortunately small extent, whenever someone buys stuff
from me then slaps restrictions on it that are illegitimate. To me the
permissions system is hampering the rights-model that I'm becoming
reliant on for earning a living (fortunately the model is robust
enough to severly limit this hampering), and I wish I could "opt-out"
my works from the permissions system to fix that.