[Opensim-dev] Interrelated difficult problems related to asset portability

[Belxjander Serechai]

I see the seperation and modularization of the opensim differently

my personal view is this...

each "grid" has own "U G" and "A I" are decoupled,

  Users from any Grid can use Asset services from one or more,
  and the U service for OpenSIM is like "customs" for the G managed Regions,

Inventory is localized for on-grid asset and inventory but each "User"
  has provision for use of a non-local "Inventory" service...

an example,

User A from Grid A wants access to Grid B

  User A approachs Grid B and obtains a "passport" sign-in for Grid B,
  then User A would need to travel an "inter-connect" between grids

Each "Grid" being like a Glass walled garden... you can sign-up and view
  using a "blank" AV for that Grid... but the Interconnect is where
  content and Users can "crossover" between grids

Ive already got a sketch for this written up and I am currently trying
to sort out
  getting two machines to independantly run standalone UGAIR of a single region
  to experiment with making this work,  having an AV for each able to
cross to the other.

I see the "interconnect" as a similar mechanism to International Customs...
  a policy agreement between grids is required... and the interconnect
cant just let "anything" go through
  which also mandates some kind of grid-local "Garbage collector" system

There is a LOT of cross-over between the interconnection of grids and
the mass-access of content,
  but each "interconnect" setup is going to require that there is some
kind of "iptables ruleset"
  in scripting was is permitted and what is denied with the final say
being down to some kind of administrative
  policy... the technology needs to allow for flexibility in what
policy decisions can be made.


2008-05-23 (金) の 08:30 -0700 に Diva Canto さんは書きました:
Dr Scofield Wrote:
> > > be people willing to pay. Maybe. There's certainly a [small] market
> > for
> > > clone detection in source code and other artifacts that are time-
> > consuming to produce.
> > >
> > i think there's a huge market out there. and it will grow with the
> > growth of VWs.
>
> Very possible.
>
> People have different needs when it comes to asset protection, and one model
> doesn't fit all. This should be configurable at server init time. Here are
> three of the most prevalent models, the third one being a hybrid.
>
> 1 - People want all their inworld assets protected from being copied. This
> means that there should be a lot of guards upfront. It's conceivable that
> someone might develop a DRM module for OpenSim; but I don't think that
> should be in the OpenSim core, because this kind of protection, besides
> being a conceptual quagmire, is not a universal need. A more lightweight
> manner of addressing this need is to use the walled-garden model of grids,
> which somewhat restricts who has access to the inworld assets, and then have
> people sign a very strict ToS, and enforce that with severe real-world
> penalties. Example on the Web: facebook.
>
> 2 - People don't care much about their inworld assets being copied by
> hackers, what they care most is to attract lots of visitors to their sites,
> or even just expressing themselves in public. So free access to images, etc,
> are a tool for traffic, it puts their message out there; not just people
> traffic but all sorts of backend info gathering traffic, for example
> crawlers for search engines. In this scenario, there is no need for backend
> asset copy-protection mechanisms, just front-end protection and declarations
> of copyrights. This is the prevalent model of the [public] Web.
>
> 3 - People care somewhat about their inworld assets being copied, while at
> the same time caring to attract visitors, therefore benefiting from
> operating in open grids and open sims. A lot of web sites fall on this
> category. This is the model that would benefit from having open access to
> assets along with a monitoring system for detecting copyright violations. As
> Dr. Scofield said, some people care to do this on the public web too.
>
> Note that all of these models can work with the techniques that we were
> talking on this thread -- REST access, pulling UAI out of the OpenSim core.
> For walled-gardens, it's "just" a matter of authenticating the callers. This
> kind of ACL is routine on the Web, session keys, etc., so it should be
> feasible in OpenSim too. I think this is possible without having to change
> the viewer.
>
> (As an important aside, assets and inventory are not the same thing.
> Inventory should always be private and protected. My use of the word asset
> means inworld object.)
>
>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev