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

Jon Watte <jwatte@gmail.com> Mon, 23 February 2009 21:49 UTC

Return-Path: <jwatte@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 44B863A6A76 for <mmox@core3.amsl.com>; Mon, 23 Feb 2009 13:49:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.526
X-Spam-Level:
X-Spam-Status: No, score=-2.526 tagged_above=-999 required=5 tests=[AWL=0.073, 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 zUdqybLwiYMD for <mmox@core3.amsl.com>; Mon, 23 Feb 2009 13:49:55 -0800 (PST)
Received: from mail-gx0-f174.google.com (mail-gx0-f174.google.com [209.85.217.174]) by core3.amsl.com (Postfix) with ESMTP id 2ECD23A6A75 for <mmox@ietf.org>; Mon, 23 Feb 2009 13:49:54 -0800 (PST)
Received: by gxk22 with SMTP id 22so5808908gxk.13 for <mmox@ietf.org>; Mon, 23 Feb 2009 13:50:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=x5PqggUci8w9BIo4vW43l9xTys5kXYCvIqBHtFT+RuI=; b=gbopczAKMpTyyVNwMQ33MyuqVD84vlpPmA1CrulN+0qhupyh1rj7/ydqeeR7i2Akby LZ/9CW6As66h2vTKG8GwdkREYOcUewYZXPnRS+X3xssTK4Tm/P4QuajpxQIFyqpknzmG eQcuBhPvUKv0WG5U5e5BZIcBIHWXDdZWuuq20=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=veJEJzClSCryuqg/C2dp4A639fxbfeRUOfYLiz6Dz8wgIvxWVFPQy95NlxszEjvR+y YBD1pBGvTFlKh+ujVPOHQTPrU2kGAhj6W1reTAVsRourDUSxask6cfZH+2q3PDImjY4y z72B3q6om6B0ThWRuPXeOoQcXlmrAdOrvAyJs=
Received: by 10.100.138.17 with SMTP id l17mr2635275and.2.1235425812612; Mon, 23 Feb 2009 13:50:12 -0800 (PST)
Received: from ?192.168.168.111? (smtp.forterrainc.com [208.64.184.34]) by mx.google.com with ESMTPS id b32sm702479ana.55.2009.02.23.13.50.11 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 23 Feb 2009 13:50:11 -0800 (PST)
Message-ID: <49A31A11.2000503@gmail.com>
Date: Mon, 23 Feb 2009 13:50:09 -0800
From: Jon Watte <jwatte@gmail.com>
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: Dan Olivares <dcolivares@gmail.com>
References: <20090223.155250.2225.0@webmail24.vgs.untd.com> <a768bcd90902231319o568d866bx39f1f91cc1f7a31c@mail.gmail.com>
In-Reply-To: <a768bcd90902231319o568d866bx39f1f91cc1f7a31c@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: mmox@ietf.org, "dyerbrookme@juno.com" <dyerbrookme@juno.com>
Subject: Re: [mmox] mmox Digest, Vol 1, Issue 113
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: Mon, 23 Feb 2009 21:49:56 -0000

Dan Olivares wrote:
> "In the There.com/Forterra context, customer content is cleared
> through a centralized clearing house and must be approved by the
> company before it can be uploaded; customers are in a subordinate
>   

Just to be clear: There.com (operated by Makena Technologies) and OLIVE 
(sold by Forterra Systems) are different products, with very different 
customers and very different processes. There.com has a central 
clearinghouse. Forterra Systems does not -- each customer of the OLIVE 
platform decides how and what content goes into their installation.

The There.com model is "we provide a PG-13 safe environment with some 
degree of content protection, and we implement it through a content 
review system" (and now the iPhone store does the same thing).

The OLIVE model is "let the customer decide, although we can help you 
with that if you need help."

Sincerely,

jw