<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16850" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>I am sorry to hear this will be available as
opensource.</FONT></DIV>
<DIV><FONT face=Arial size=2>Many small grids will not have the ability to aviod
and monitor the usage of these kind of applications.</FONT></DIV>
<DIV><FONT face=Arial size=2>Content protection should be a high
priority.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I do think all private assets ( made by the
individual ) should be allowed to be backed up from inworld.</FONT></DIV>
<DIV><FONT face=Arial size=2>Copying "Any Full perm" and distribute it through
all grids is somthing i am strongly against.</FONT></DIV>
<DIV><FONT face=Arial size=2>The permisions are given inside a grid and should
stay there.</FONT></DIV>
<DIV><FONT face=Arial size=2>The idea to give access to asset servers and let
the "people" be responsible for the content is a mad idea.. sorry to say
so.</FONT></DIV>
<DIV><FONT face=Arial size=2>The service giving Grid is allways responsible
for all content they host.</FONT></DIV>
<DIV><FONT face=Arial size=2>When i read about this at first i thought it had
potential......</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Please think about what you are making and
what the concequences will be for small starting grids and also for the people
that will be using it.</FONT></DIV>
<DIV><FONT face=Arial size=2>Also know that most "proper" grids will disable
your tool from logging in so it will be worthless at the end.</FONT></DIV>
<DIV><FONT face=Arial size=2>Probably your tool will end up in people getting
banned from there worlds, i dont think that is the idea behind such a
appliaction.</FONT></DIV>
<DIV><FONT face=Arial size=2>Please take this in concideration as we will also
permanatly ban this tool when it does not protect our creators.</FONT></DIV>
<DIV><FONT face=Arial size=2>* i know a lot of other grids will do the same in
the current situation.</FONT></DIV>
<DIV><FONT face=Arial size=2>We just want to give our creators fair change
for there hard work, and we will do everything needed to protect
that.</FONT></DIV>
<DIV><FONT face=Arial size=2>I hope you understand our point of vieuw, and you
will think about how to implement that into your application.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Best regards,</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Martin Forster</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV> </DIV>
<DIV>----- Original Message ----- </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=snowcrash.short@gmail.com
href="mailto:snowcrash.short@gmail.com">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">opensim-users@lists.berlios.de</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, November 15, 2012 9:26
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [Opensim-users] Announcement
of inventory tool (MyInventory), mostly of interest to grid operators/grid
nauts</DIV>
<DIV><BR></DIV><BR><BR>
<DIV class=gmail_quote>On Thu, Nov 15, 2012 at 9:00 PM, Melanie <SPAN
dir=ltr><<A href="mailto:melanie@t-data.com"
target=_blank>melanie@t-data.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<BR>
<DIV class=im><BR>On 15/11/2012 19:33, Snowcrash Short wrote:<BR>> Closed
source is just another word for security through obscurity, which
we<BR></DIV>> - hopefully - all know really doesn't provide any security.
[...]<BR><BR>Closed source means that it's not trivially possible to modify
the<BR>tool to assume the open policy for all grids and then put
the<BR>modified tool in the wild for all and sundry to abuse.<BR>Most
existing tools are either hacking tools sold through dubious<BR>channels,
difficult to use or lack important features. There is to<BR>this day no
free, widely available, open source, easy to use content<BR>ripping tool.
Your project is bound to become that tool if it is<BR>released as open
source.<BR></BLOCKQUOTE>
<DIV>There is no if about it, the code is ready for release, currently I'm
working on a windows installer and documentation. Initially the code will be
released under AGPL, once the code base is more mature I intend to change the
licence to BSD. </DIV>
<DIV><BR></DIV>
<DIV>I have decided to wait for two weeks after my initial announcement,
because I wanted to give grid operators a heads up before releasing the
code.</DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<DIV class=im><BR>> Atleast it will be very simple for the administrator
to determine if assets<BR>> are being duplicated, especially if
MyInventory is being used in a mode<BR>> where it accesses the asset
service directly.<BR><BR></DIV>No closed grid will ever be able to provide
direct asset service<BR>connections because these also allow to extract any
and all content,<BR>in full quality and without restrictions. This would
include script<BR>sources - an unacceptable situation.<BR>
<DIV class=HOEnZb>
<DIV class=h5><BR></DIV></DIV></BLOCKQUOTE>
<DIV>Not really, it would be almost trivial to implement an asset service
which restricted access to assets, at least in a non hyper-grid scenario. The
only worry would be rouge simulators which could be attached to an existing
grid.</DIV>
<DIV><BR></DIV>
<DIV>On a similar note it would almost as easy to implement a fully
distributed asset server, which retrieved assets from the users local asset
store, "My Suitcase" is clearly an example that such a scheme is not only
feasible but almost fully implemented in the existing code base. The
only question is whether grid operators are willing to surrender control of
assets, and leave those assets to be the responsibility of the visiting users.
This distributed asset store, where asset are fetched from individual users'
asset stores would very likely - and counter intuitively - be the one that
offered the greatest amount of protection against asset theft compared to a
hypergrid enabled grids asset store.</DIV>
<DIV>/Snowcrash</DIV>
<DIV><BR></DIV>
<DIV> </DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<DIV class=HOEnZb>
<DIV class=h5>-
Melanie<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>
<P>
<HR>
<P></P>_______________________________________________<BR>Opensim-users
mailing
list<BR>Opensim-users@lists.berlios.de<BR>https://lists.berlios.de/mailman/listinfo/opensim-users</BLOCKQUOTE></BODY></HTML>