The greatest weakness of our virtual environment is that it must ultimately be rendered within the confines of a viewer application to make the world visible on our computer screens. This, by its very nature, makes it impossible to protect any content whatsoever.<br>
<br>It's like all the copyguards surrounding video. they all work well and great when attempting media to media copying, as in disc duplication. However, the moment the video is rendered on a screen then it is ultimately vulnerable to exploitation.<br>
<br>One of the easiest, fastest and most sure-fire ways to "steal" a new movie in the theaters is by simply using a video camera in the theater to record the video as it plays on-screen.<br><br>With virtual worlds, the fact that everything must ultimately be rendered so that we can see and enjoy it, also means that circumventions can easily exist to exploit the rendering and thus be "recorded" and saved by an unscrupulous pirate who can then do whatever they wish with the end result.<br>
<br>- Len<br><br><div class="gmail_quote">On Wed, Feb 24, 2010 at 8:43 PM, Master_Mirage <span dir="ltr"><<a href="mailto:mirage123@verizon.net">mirage123@verizon.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Actulay ill dabble in a bit of what IF here. 1st off blocking users or<br>
clients isant the problem and as we know not effective really.<br>
The problem is the content it selph has no safegurds.<br>
In my way of thinking at this stage of opensimulator dev. We can add in<br>
some.<br>
One could be what ill call a 3rd state of perms. for example: I make a chair<br>
i set it no copy. That could also set a 3rd state that sets a NO EXPORT FLAG<br>
to the assest server. Now lets say i do want to give it away to anyone. So i<br>
set it so anyone can copy. It would then drop the no export flag from the<br>
oject and insted add the users water mark. That item can now be exported and<br>
be traceable at the same time.<br>
<br>
Other Opensimulators can test for the watermark and export flag used to<br>
decide if it can be imported. (might help keep fakes out). Watermarks could<br>
be portable for the user that can be used to authenticate them as the<br>
creator and where it was 1st made evan if its on another grid.<br>
<br>
Im shure i havent thought this thru well enough but i still feel protection<br>
of content has to be part of the content its selph. At least the abuilty to<br>
do things like that would give Opensimulator the tools to make a good 1st<br>
step twords anti-content theft.<br>
<br>
I know all this is alot more complicated todo than it sounds and thats why<br>
its just a What If .<br>
<br>
<br>
:-)<br>
<font color="#888888">--<br>
View this message in context: <a href="http://n2.nabble.com/Speaking-of-Content-Theft-How-About-Our-Own-Backyard-tp4622175p4630118.html" target="_blank">http://n2.nabble.com/Speaking-of-Content-Theft-How-About-Our-Own-Backyard-tp4622175p4630118.html</a><br>
</font><div><div></div><div class="h5">Sent from the opensim-users mailing list archive at Nabble.com.<br>
_______________________________________________<br>
Opensim-users mailing list<br>
<a href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-users" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-users</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>- Len W. Brown <br> <a href="mailto:lenwbrown@gmail.com">lenwbrown@gmail.com</a> <br> <a href="http://www.lenfocenter.com">http://www.lenfocenter.com</a> <br>