Hi Snowcrash,<div><br></div><div>I'm looking forward to seeing the full functionality and feature set of your tool to have a more informed opinion, but from my original email in this thread, I still think the better approach would be to default to the most restrictive TPV-like setting and let grids who want to offer the less restrictive options contact you. Opt in rather than opt out. I really fear that you would be opening yourself to a dangerous legal nightmare if the tool is designed with the current approach, for all the reasons we've discussed in this thread.</div>
<div><br></div><div>We both know that this would likely result in most grids only having the more restrictive functionality, at least initially, but it still seems like the safest approach to me - safer for you as the developer and for grids who need to protect their users' content. I also think you'd be more likely to get buy in and support from the community with this approach, so people could feel comfortable that the default mode will at least do no more harm than what's already permitted in existing tools like Second Inventory, etc. Perhaps from that starting point, and seeing the other benefits your tool provides, more grids would be interested in going to a more permissive setting in the future.</div>
<div><br></div><div>Sincerely,</div><div><br></div><div>- Chris/Fleep</div><div><br></div><div><br></div><div>Chris M. Collins (SL/OS: Fleep Tuque)</div><div>Center for Simulations & Virtual Environments Research (UCSIM)</div>
<div>UCIT Instructional & Research Computing</div><div>University of Cincinnati</div><div>406A Zimmer Hall</div><div>315 College Drive</div><div>PO BOX 210088</div><div>Cincinnati, OH 45221-0088</div><div><a href="mailto:chris.collins@uc.edu">chris.collins@uc.edu</a></div>
<div>(513) 556-3018</div><div><br></div><div><a href="http://ucsim.uc.edu">http://ucsim.uc.edu</a></div><div><br></div><div><br><br><div class="gmail_quote">On Sat, Nov 17, 2012 at 2:47 AM, Snowcrash Short <span dir="ltr"><<a href="mailto:snowcrash.short@gmail.com" target="_blank">snowcrash.short@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br><br><div class="gmail_quote"><div class="im">On Thu, Nov 15, 2012 at 3:50 PM, What Virtual World - Martin Forster <span dir="ltr"><<a href="mailto:blackberry@forsterinternet.nl" target="_blank">blackberry@forsterinternet.nl</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div bgcolor="#ffffff">
<div><font face="Arial">Hello Snowcrash,</font></div>
<div><font face="Arial"></font> </div>
<div><font face="Arial">I think it is good having software to backup your
items but....</font></div>
<div><font face="Arial">As melanie sayed before, the ability to backup
"Any" item would not be a good idea as your software will be banned from major
grids due to this.</font></div>
<div><font face="Arial">To be honest we would also blacklist your software
if we think it can be at harm for the creators in our grid.</font></div>
<div><font face="Arial"></font> </div>
<div><font face="Arial">Please think if this:</font></div>
<div><font face="Arial">Most people can not make a "copybot vieuwer" as the
things people need for that are available but also complicated to build if you
dont have any experiance.</font></div>
<div><font face="Arial">If your software is easy to compile without any
knowledge it will be a base for people to create these "copybot's"
with.</font></div>
<div><font face="Arial">This will not be the best advertisment for your
software in my believe.</font></div>
<div> </div>
<div><font face="Arial">I think it will be best not to make it an
opensource project .. but just distribute only in binary
form.</font></div>
<div><font face="Arial">Also making it TPV compliant will be even
better.</font></div>
<div><font face="Arial">If it protects content from beeing ilegaly
copied on "any grid" we will support it for sure.</font></div>
<div><font face="Arial"></font> </div>
<div><font face="Arial">Just my two cents ...</font></div>
<div><font face="Arial"></font></div></div></blockquote></div><div>The backup feature, which really is only a small part of the overall featureset, currently operates in one of two modes, TPV compliant mode and unrestricted mode. MyInventory forces the download component to be TPV compatible when connecting to any known Linden Labs grid (and similar protection is underway for other grids), My original mail had two topics.</div>
<div><br></div><div>1) Which grids would like to have the same hardcoded protection level against unrestricted download as Linden Labs</div><div>2) This tool may - if it becomes popular - create a lot of duplicate assets, therefore I came up with a suggestion on how to alleviate this problem.</div>
<div><br></div><div>Going closed source is simply "security by obscurity" under a different name, the "black hatters" already have the ability to take what they want, claiming that content creators assets are safe is simply not true, and that fact holds for Linden Labs grids as well.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#ffffff"><div> </div></div></blockquote><div>Even if you decide to block MyInventory, the blocking tools are so inadequate in these days of fast recycling DHCP servers, that all you will manage to do is to block out legitimate users, the "black hatters" can easily get around these limitations. And is that really what you want?</div>
<div><div class="h5">
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#ffffff">
<div><font face="Arial">Best regards,</font></div>
<div><font face="Arial"></font> </div>
<div><font face="Arial">Martin Forster</font></div>
<blockquote style="PADDING-RIGHT:0px;PADDING-LEFT:5px;MARGIN-LEFT:5px;BORDER-LEFT:#000000 2px solid;MARGIN-RIGHT:0px"><div>
<div style="FONT:10pt arial">----- Original Message ----- </div>
<div style="BACKGROUND:#e4e4e4;FONT:10pt arial"><b>From:</b>
<a title="snowcrash.short@gmail.com" href="mailto:snowcrash.short@gmail.com" target="_blank">Snowcrash Short</a> </div>
<div style="FONT:10pt arial"><b>To:</b> <a title="opensim-users@lists.berlios.de" href="mailto:opensim-users@lists.berlios.de" target="_blank">opensim-users@lists.berlios.de</a>
</div>
</div><div><div><div style="FONT:10pt arial"><b>Sent:</b> Thursday, November 15, 2012 10:44
AM</div>
<div style="FONT:10pt arial"><b>Subject:</b> [Opensim-users] Announcement of
inventory tool (MyInventory), mostly of interest to grid operators/grid
nauts</div>
<div><br></div>Hi
<div><br></div>
<div>I've been working on a client side tool for decentralizing user
inventories, which I will release as an open source tool in two weeks, some of
the features may be relevant to grid operators.</div>
<div><br></div>
<div>The basic premise of the tool is that the inventory and the backing
assets of the inventory items really should be controlled by the user. The
tool is born out of a frustration of having visited a number of grids. Each
visit to a new grid presents me with an empty inventory, and I can then spend
time searching for suitable item, clothing, attachments and
other accessories.</div>
<div><br></div>
<div>For this purpose I have created a tool which will allow me to backup my
inventory to a local cache and then upload the contents to another grid.</div>
<div><br></div>
<div>If my tool becomes popular, both the upload and download mechanisms may
have some impact on the grid-operators, hence this email to serve as a
notice.</div>
<div><br></div>
<div>The basic architecture is pretty simple, consisting of a number of import
agents, which can import the users inventory and backing assets to a local
database, and a number of upload agents which can upload inventory content to
a specific account.</div>
<div><br></div>
<div>Backup/Import</div>
<div>There are two import agents, one which will import .iar files and one
which works very much like I believe "Stored Inventory" works, which can
backup the inventory of an avatars inventory. Avatar backup/Import is governed
by a policy. Currently there are two policies, one complying with a
very restrictive interpretation of the Linden Labs policy on backups, and a
completely unrestricted policy, where anything that can be downloaded will be
downloaded.</div>
<div><br></div>
<div>When a new account is registered in MyInventory it checks if the account
is for a Linden Lab grid and limits the choices of policies to policies
suitable for LL's TOS, I cannot and do not know if other grids have similar
policies, I can well imagine that Avination has a similar restrictions, and
would like similar logic implemented to restrict the download. Any grid
operator which would like to have backup governed by a more restrictive
policy are invited to notify me and I will attempt to implement the
policy prior to the first release of the source code. or supply patches at a
later time.</div>
<div><br></div>
<div>Upload/Export</div>
<div>MyInventory supports two mechanisms for uploading inventory
content, traditional upload using UDP/CAPS and direct access to the
inventory and asset web-services.</div>
<div>Due to limitations in the UDP/CAPS protocol each upload will create new
assets, and as of my latest read of the Open Simulator code the asset store
does not support "single instance assets", i.e. it does not use a checksum to
verify if the asset already exists, for this reason MyInventory prefers to
upload using direct access to asset and inventory web-services.</div>
<div><br></div>
<div>I would propose that the grids which chooses to support MyInventory
augment their "GridInfoService" entries with the url's for the asset and
inventory web-services, e.g.</div>
<div>
<div><br></div>
<div>[GridInfoService]</div>
<div> assets = <a href="http://assets.osgrid.org" target="_blank">http://assets.osgrid.org</a></div>
<div> inventory = <a href="http://inventory.osgrid.org" target="_blank">http://inventory.osgrid.org</a></div></div>
<div><br></div>
<div>Best regards</div>
<div>Snowcrash</div>
</div></div><p>
</p><hr><div>
<p></p>_______________________________________________<br>Opensim-users
mailing
list<br><a href="mailto:Opensim-users@lists.berlios.de" target="_blank">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></div>
<p></p></blockquote></div>
<br>_______________________________________________<br>
Opensim-users mailing list<br>
<a href="mailto:Opensim-users@lists.berlios.de" target="_blank">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></blockquote></div></div></div><br>
<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></blockquote></div><br></div>