Talk:Virtual World Model

Simulator Trust Domain definition
It currently states: "One or more simulators that completely trust each other, operated by one single authority." Does it really need to be operated by a single authority? Could I not say I fully and completely trust sims operated by John Smith and/or he fully and completely trusts sims operated by me? --DaveCoyle 11:40, 20 April 2009 (UTC)

Yes, you are right. I changed the definition. Basically, I think what you're getting at is that each simulator, or each seed trust domain, can extend trust to other trust domains, and this is not transitive: you trust W, but you don't necessarily trust the sims that W trusts. Needs more thinking. --Diva 07:50, 20 April 2009 (PST)

OSGrid and trust domains
There seems to be continued disagreement regarding OSGrid and trust domains, so let's discuss it here. Charles, you removed the sentence "For example, OSGrid has, by nature and intent, several hundred simulator trust domains." I disagree with its removal, and based on the -dev list thread everyone doesn't seem to be on the same page on this point. So let's talk it out.

I am a region operator on OSGrid. I fully trust sims operated by myself. I fully trust sims operated by a handful of others who I believe will not do anything nefarious to me, my communications, my inventory, etc. I neither trust nor don't trust sims operated by most others, as I neither know them nor have reason to believe they'll do bad things. I do not trust some regions (e.g. DNCH).

Sounds like multiple trust domains to me. --DaveCoyle 11:31, 20 April 2009 (UTC)

I would really like to hear more from the OSGrid community about wishes for the future, 1 year ahead. The only reason why I am making that subtle distinction between Grid and Trust Domain is OSGrid. I mention LL grid, but, really, I have no idea what their plans are, that's just speculation. OSGrid, however, exists. Unifying the concept of Grid with that of trust domain will make the model a whole lot simpler and easier to implement, so if that is what's on the map for OSGrid, it would be good to know. --Diva 09:45, 20 April 2009 (PST)

We have 15 regions on osgrid and our role is one of applying the tech that others are developing. When i need to explain what a grid is to an end-user it is a "world of regions" - the world map is my metaphor. Also, as an "application provider", I would probably prefer grid "safety" to be controlled as much as possible by the person who is providing the opensim.exe instance rather then the grid manager. Just my thoughts. Casias Falta Aug. 19, 2011

The meaning of safety
There seems to be an important reference left undefined in this useful page. Various paragraphs refer to "safely exchange messages", "unsafe teleports", and "safe simulator connectivity", but nowhere is the meaning of "safety" explained or illustrated. I can imagine a variety of possible considerations that can give rise to a verdict of "safe" versus "unsafe", such as the desire to safeguard assets, or protect system integrity, or prevent abuse, or simply to disallow unauthorized access, but which of these were intended here? Perhaps all of them? Or does "safety" have a specific meaning in this context?

I think it's worth spending a little time defining what is meant here, because the foundational idea of "trust domain" is currently being described in terms of a fuzzy concept that obscures rather than explains. Yes, we all love the motherhood and apple pie implied by "safe", but what does it actually mean in this specific context, for the purposes of model definition? :-) Morgaine 12:37, 10 June 2009 (UTC)