[cap-talk] Fwd: [cors] TAG request concerning CORS &Next Step(s)
David Barbour
dmbarbour at gmail.com
Thu Sep 3 22:08:26 PDT 2009
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.
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
>
> --
> Ihab A.B. Awad, Palo Alto, CA
>
> _______________________________________________
> cap-talk mailing list
> cap-talk at mail.eros-os.org
> http://www.eros-os.org/mailman/listinfo/cap-talk
>
>
--
hubris and humility compose
perfectionism, paralysis, a curse
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.eros-os.org/pipermail/cap-talk/attachments/20090903/271fbbd6/attachment-0001.html
More information about the cap-talk
mailing list