You totally misunderstand my intentions. What I have proposed does not require any feat of computer vision or engineering magic. Its actually very simple. People assign inventory and items into categories all the time. You do it everytime you register an item at SLX. sure this system would be a bit more complicated, but not by much. <br>
<br>Are you always so insulting?<br><br>You don't see how modelling an international economy would have any educational value? Im not going to comment on that any more than that question. I'll let the question stand with the rest of the community.<br>
<br><br><div class="gmail_quote">On Wed, Mar 5, 2008 at 11:52 AM, Diva Canto <<a href="mailto:diva@metaverseink.com">diva@metaverseink.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
Todd,<br>
<br>
You're expecting too much from technology. What you are saying is 100
times harder to do (close to impossible, really) than encrypting things
so that only authorized people can see them. There is no way that one
can automatically distinguish Star Trek's Enterprise from a horse
carriage. Meta-info like name and description is unreliable, because
one can name a carriage "Star Trek Enterprise". What you are asking for
goes into the field of computer vision, one that is still in its early
infancy.<br>
<br>
Negotiations like that must be done at some other level. Good old human
communication, over a simple Access Control List facility, can take you
99.99% of the way. So if you want to enforce the theme of your
role-playing virtual world,
either close it down so that only your trusted friends can enter, or
have
it open under a ToS that explains the rules of the game and the
consequences of breaking them ("you must be 18 years old or older" etc
:-). Note that you will have the freedom to write a ToS that is very
specific to your role-playing world, not the generic one that LL has.
You can make it as restrictive as you want. Enforcing it is another
issue altogether... So if you really really don't want to be bothered
by mood-breaking off topic avatars, ever, close things down, make your
world accessible only to the people you trust.<br>
<br>
OpenSim is trying to figure out how to support surfing of avatars among
grids, because that is something that lots of people want for
conducting real business and outreach in virtual worlds; but, like on
the web, that kind of openness stops in sites/grids that have an Access
Control in place. The option of closing things down to authorized
accounts is not only a well-practiced concept on the internet, but one
that OpenSim supports at the very core.<br>
<br>
I must say, though, that I don't see any connection between the
concrete thing that you said and education, except, perhaps, the Police
Academy :-)<br>
<br>
On a technical note, the Inventory is harmless. All assets in Inventory
are sitting nicely on some hard disk, doing absolutely nothing. It's
only when people attach them or rez them that they may become a problem
-- these actions move the objects from the disk where they are sitting
to the memory of the server, where everyone can see them and where they
can run scripts, if allowed. <br>
<br>
Diva / Crista <br>
<br>
Todd Adams wrote:
<blockquote cite="http://mid2560615f0803050425q7f64abcl115ffad66ff6d770@mail.gmail.com" type="cite"><div><div></div><div class="Wj3C7c"><span>@</span>
Cristina<br>
<br>
Along the lines of permissions between grids...<br>
<br>
There are people who are going to want to set up specialty grids for
role-play. If they are creating a fantasy medieval world, they sure do
not want people bringing in the latest CCC spaceship or BFG 2000
particle beam weapon into that world. Maybe it should just be flagged
so its grayed out in inventory until arriving at a world the item is
compatible with. On the flipside, people role-playing a Star Trek
universe are not going to appreciate newcomers arriving with a +6
Vorpal Broadsword...<br>
<br>
Beyond allowing/disallowing, certain inventory items could be
embargoed or taxed in the local currency. A flexible enough system
would be an excellent learning tool for college and high school
economic classes.<br>
<br>
<br>
<div class="gmail_quote">On Wed, Mar 5, 2008 at 3:04 AM, dr scofield
<<a href="mailto:DrScofield@xyzzyxyzzy.net" target="_blank">DrScofield@xyzzyxyzzy.net</a>>
wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">Cristina Videira Lopes wrote:
<blockquote type="cite">
<div>
<div>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Burnman,</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">Technically
your comments are off, as Michael already pointed
out. They are so off that I think they are directed at the Open Sourced
LL viewer,
i.e. at the ability for clients to get complete information about the
objects inworld to the point of being able to store them locally and to
replicate
them. Note that this has nothing to do with OpenSim, strictly speaking.
But let
me comment on that.</span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
</div>
[...]
<div><br>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"></span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p><span style="font-size: 11pt; color: rgb(31, 73, 125);">While
the solution is technically feasible, what sense would it
make to go around the world seeing garbage everywhere?? Plus anyone who
wanted
to see the decrypted objects would have to use an extended version of
the LL
viewer, one that does decryption. Not to mention the added performance
overhead.
… Again, I doubt massive adoption, but this could definitely be done,
technically.</span></p>
</div>
</div>
</blockquote>
completely agree with that. the point of a virtual world is that you
*can see the virtual world* --- again, this is the core fallacy of DRM:
you want keep your content a secret but at the same you need to give
your customers access to the content otherwise why would they pay for
it???<br>
<br>
let face facts (and i'm repeating arguments others and i have made, i
know):<br>
<ul>
<li>clients will have to be told about the shape and texture of
virtual world objects --- *otherwise they won't be able to render it*</li>
<li>scripts can be kept on server, clients don't get access to
them
(unless you own the object or share it)</li>
<li>in a future interconnected grid of grid (let's call that a
virtual universe), you could add "permissions" that let you specify to
which grids an object may be exported, that way you could say, i trust
the LL grid, i don't trust dr scofield's grid because, oh, i don't
know, she doesn't agree with me on DRM and VW ;-)</li>
</ul>
that last approach will have consequences for your customers though:
they won't be able to take the objects they bought from you with them
to dr scofield's grid. some won't care, some won't like it --- and
probably not be return customers. but that then is something you as a
content provider have to come to terms with.
<div><br>
<br>
cheers,<br>
dr scofield<br>
<pre cols="80">--
dr dirk husemann, mathmatics and computer science, ibm zurich research lab
SL: dr scofield ---- <a href="mailto:drscofield@xyzzyxyzzy.net" target="_blank">drscofield@xyzzyxyzzy.net</a> ---- <a href="http://xyzzyxyzzy.net/" target="_blank">http://xyzzyxyzzy.net/</a>
RL: <a href="mailto:hud@zurich.ibm.com" target="_blank">hud@zurich.ibm.com</a> - +41 44 724 8573 - <a href="http://www.zurich.ibm.com/%7Ehud/" target="_blank">http://www.zurich.ibm.com/~hud/</a>
</pre>
</div>
</div>
<br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de" target="_blank">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div></div><pre><hr size="4" width="90%"><div class="Ih2E3d">
_______________________________________________
Opensim-dev mailing list
<a href="mailto:Opensim-dev@lists.berlios.de" target="_blank">Opensim-dev@lists.berlios.de</a>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
</div></pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br></blockquote></div><br>