[Opensim-users] Announcement of inventory tool (MyInventory), mostly of interest to grid operators/grid nauts

[Snowcrash Short]

Diva ....

In so many ways I believe we have the same vision of what the metaverse
should be. But we disagree on a few details on implementation.

In my vision the user does not need to run a simulator, all he or she needs
is a storage location for inventory content and assets, and contact
information (friends). Whether the user decides to house that storage in
"the cloud" or on a local computer is - even today - completely irrelevant
to my implementation.

Using Robust as a basis for storing a users personal inventory and assets
(legally licensed naturally) is asking too much of the average user in my
personal opinion, it needs to be simpler.

I am not against Robust, it was a big step forward compared to UGAIM, but
not for users.

As for bots, there is no doubt that it is easy to detect bots, the real
question is whether blocking for MyInventory - as long as it isn't used for
copyright infringement - is doing the user base a dis-service or not? I am
definitely not trying to belittle content creators, they do a very
important job, but with out a solid and strong user base, what purpose -
beyond the pleasure of creation - serves the process of content creation?

MyInventory is foremost designed to be a tool for end users, and the
roadmap I envision is based on user needs. I won't delve to much on the
plans since they are worthless unless they are backed by code. Users need
content creators and Content creators needs users and easy - controllable
and manageable  - distribution channels, users need content, easy
distribution channels and regions.

I hope that clarifies why I have opted to stay away from writing code for
Robust.

Best regards
Snowcrash

On Mon, Nov 19, 2012 at 8:08 PM, Diva Canto <diva at metaverseink.com> wrote:

> On 11/19/2012 10:21 AM, Diva Canto wrote:
>
>> What you want to do, the inventory download and upload, can be done in a
>> way that doesn't upset anyone.
>>
>
> After I wrote this, I realized that maybe the reason why you did your tool
> the way you did it is because you don't know how to do it in any other way.
> So let me explain what's the "right" way of doing it. ("right" meaning that
> you won't upset anyone; on the contrary, you'll be thanked)
>
> You should develop a robust-bound service that packs and unpacks
> inventory, and that can accomodate a variety of export policies. The tool
> that runs in people's computers would then interact with that piece of
> server-side code directly. It's not hard to do.
>
> Doing it this way, the people who run these services have choices. For
> example, Fleep would likely run that service in FleepGrid using its most
> permissive policy (all items). Melanie would run that service in Avination,
> maybe, using its most strict policy (only items created by the user). Some
> other commercial grids might not run the service at all. When we finally
> have the export flag, that can also be taken into consideration. Etc.
>
> The way you are doing it, you give grid operators no choice, because
> you're exploiting the viewer channel using libomv hacks. The lack of choice
> upsets people. You're right that you didn't create libomv, and that what
> you did can, indeed, be done by others. I am on the camp of those who think
> that using the viewer channel for accessing grid resources should be done
> only and exactly by person-driven viewers, and that therefore grids should
> refuse service to ALL client bots, even those that are embedded in the
> viewers -- bots are not hard to detect, especially if they want to do
> things as fast as they must. Don't be surprised if you see bot-kicking
> opensim extensions coming soon, rendering your tool (and others') useless.
>
> OpenSim is open source and has a great plugin architecture; practically
> everything you can envisioning doing can be done by extending the
> server-side with useful features, which can then be used or not by whoever
> runs these worlds.
>
>
> Diva
>
> ______________________________**_________________
> Opensim-users mailing list
> Opensim-users at lists.berlios.de
> https://lists.berlios.de/**mailman/listinfo/opensim-users<https://lists.berlios.de/mailman/listinfo/opensim-users>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://opensimulator.org/pipermail/opensim-users/attachments/20121119/22622fe2/attachment.html>