[cap-talk] Fwd: [cors] TAG request concerning CORS &Next Step(s)
benl at google.com
Fri Sep 4 01:34:45 PDT 2009
On Fri, Sep 4, 2009 at 6:08 AM, David Barbour <dmbarbour at gmail.com> wrote:
> Another feasible design is to use time-expiry caps... i.e. offering a
> capability to use Google's ticker for a period of time, with regular renewal
> from Acme. Acme would be free to cut off the expenditure at any time if a
> user is discovered to abuse it, and can use a small pool of caps for a
> larger group of users (using more than one cap allows them to quickly
> discover abusers, but avoiding one cap per user keeps the communications
> price down).
> That's the approach I've been pondering for a related problem, anyway: in
> ocap-secured gaming, how do you ensure that players who obtain an ocap at
> one point - e.g. to listen to the audio feed for a region, or see the
> contents of a room - will lose that cap upon the avatar leaving the region?
> My thought was that the environment would regularly broadcast caps to
> avatars in the region, allowing the older caps to expire. This would reduce
> the incentive for 'cheating' because a cheating client could not maintain a
> cap without the cooperation of the broadcast source... but it would also
> have a relatively low overhead.
I'm curious how you know an avatar is "in the region" for this model?
> On Thu, Jun 25, 2009 at 2:42 PM, <ihab.awad at gmail.com> wrote:
>> Attached is a PDF with my formulation of the problem.
>> The core conclusion is that the distinction between the two approaches
>> is a social one: do we want a model where everyone has one account at
>> Google (and one of a small number of other centralized sites), and all
>> mashups are just one-level layers on top of these centralized sites?
>> Or do we envision a truly distributed web of cooperation?
>> Ihab A.B. Awad, Palo Alto, CA
>> cap-talk mailing list
>> cap-talk at mail.eros-os.org
> hubris and humility compose
> perfectionism, paralysis, a curse
> cap-talk mailing list
> cap-talk at mail.eros-os.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cap-talk