[Opensim-dev] Wormhole in OpenSIM?

Tue Oct 26 07:22:06 UTC 2010

Mentolyptus, to achieve what you want with these "wormholes", you must convince the operator/administrator of the grid to set a link-region to one of the regions in your own grid/standalone. Hence I think there is not a need to have this functionality implemented in OpenSim core (because it's already there) but rather have the grid operator provide a service which creates such a link.

If we take OSgrid as an example, they could offer a functionality on their website that allows you to enter both a hypergrid address and region coordinates; with these specified data, a link-region would then be created on OSgrid.

Maybe you want to suggest the addition of such a "wormhole" service in the OSgrid forums?

Mentolyptus wrote:
> Diva:
> I understand what you say, I'm glad you understand Spanish, it's
> frustrating difficulty of the language, even attempt to learn English
> but it is hard:)
> The whole issue of the idea of wormholes has been streaky and maybe I
> did not find a way to explain properly.
> There are things that give de facto, for example, you may perhaps osgrid
> not want to have a direct link to my regions?, But in fact it does,
> because I have a server running mode osgrid registered gridhypergrid
> this connected to link -region with my main server that operates in
> Hypergreen. This region in osgrid all we have is a teleport that leads
> to my main server outside osgrid. :] Is doing the work that I propose
> for a wormhole-region.
> The initial idea of wormholes is simple, can be summed up as Shaun said
> when he said: "It sounds like What He Wants Is for Foreign grids to link
> to a historical region in grid, so users from That Can Get That grid to
> historical , Without him
> HAVING to Maintain a grid region in the Other. "
> I can have a region in osgrid registered, and many other regions in
> other grids that allow me to and from these regions to advertise or
> redirect to my server that is outside of these grids with a teleport. It
> actually raised is given. The only difference is that I need to do a
> server-mode opensim in gridhypergrid connected to each of these grids
> hacieno bridge, consuming resources, and forcing the visitor to make a
> stop before reaching my final region directly. Means?
> In contrast, the wormhole-region could do the same job by simply
> recording a "virtual region" or region of linkage between both grids,
> and this without consuming resources or at least consume fewer
> resources, since no region would be a real physical terrain, objects, or
> even user database or only a mark on the map as a link-visible region
> that would redirect the server end. That's why I compared it to a
> redirection of a web page. Maybe just a crazy idea XD
> True, there are grids that do not have to want to link to the grid for
> others, but the fact is that almost all standard grids are beginning to
> use Hypergreen and are open to traffic in return. and everything
> provided to travelers coming and going quality improvement experience.
> This may make travel less cumbersome. As things now are sometimes
> necessary to make several stops to reach a destination.
> The wormhole-region simply serve a gateway function visible on the map
> that would allow to have a grid in a given region without having to
> actually have a region in the grid.
> Thanks for replying, did not think were going to devote much time to
> meet my crazy O:)
>
> -Mento
>
>
> El 25/10/10 15:55, Diva Canto escribió:
>> I don't think it's lost in translation as I can read and understand
>> Spanish -- it's funny that the translator transforms Hypergrid into
>> Hypergreen :-)
>>
>> You seem to be mixing many different things. The Linden viewer has its
>> own version of http redirects. When we have virtual worlds on the
>> regular web browser, the Hypergrid will use http redirects, no more no
>> less. (I have a version of the Hypergrid that does exactly that)
>>
>> But Hypergrid without control on the part of grid operators would be a
>> really bad idea. Not all virtual worlds want to be part of it. And
>> just because your grid links to, say, osgrid doesn't mean that osgrid
>> wants to link back to yours. Just like on the web: just because your
>> site links to, say, Slashdot doesn't mean that Slashdot wants to link
>> back to your site. The static hyperlinks reflect social dynamics, like
>> on the web or even like on twitter.
>> The process to discover virtual worlds that aren't linked needs
>> additional services, like search or directories.
>>
>> On 10/25/2010 10:21 AM, Mentolyptus wrote:
>>> I regret the poor quality of my English, and need to use a
>>> translator, I think this merely to explain clearly the idea.
>>> Diva, I understand basically how it works Hypergrid, although it is a
>>> certainty that I do not understand as well as you. Anyway, what I
>>> propose is not a criticism of the current operation of hypergrid, but
>>> an idea looking for a way to allow the unification of hypergrid. I
>>> think the basic idea has been misunderstood.
>>> Thanks for replying, and thanks to all the development team for the
>>> excellent work they do for us. If some of the idea put forward has
>>> been going around in someone's head, who knows, maybe it is recycled
>>> into something good :)
>>> if there is anyway so there will be many good things.
>>>
>>> A Hypergreen free, united without borders, where all grids are joined
>>> into one, sounds like a good idea
>>> ----------------------------------
>>>
>>> Yo lamento la mala calidad de mi ingles, y necesitar usar un
>>> traductor, pienso que esto limita poder explicar claramente la idea.
>>> Diva, entiendo basicamente como funciona hypergrid, aunque es una
>>> certeza que no lo comprendo tan bien como usted. De todas formas lo
>>> que propongo no es una critica al actual funcionamiento de hypergrid,
>>> sino una idea a futuro para una forma de permitir la unificacion del
>>> hypergrid. Pienso que la idea de fondo se ha malentendido.
>>> Gracias por responder, y gracias a todo el equipo de desarrollo por
>>> el excelente trabajo que hacen por nosotros. Si algo de la idea
>>> planteada ha quedado dando vueltas en la cabeza de alguien, quien
>>> sabe, quizas se recicle en algo bueno :) si no es asi de todas formas
>>> habra muchas cosas buenas.
>>>
>>> Un hypergrid libre, unificado sin fronteras, donde todos los grids se
>>> unen en uno solo, suena como una buena idea
>>>
>>>
>>>
>>> El 25/10/10 14:50, Diva Canto escribió:
>>>> If that's all, then ... ok. I thought I heard wishes of a technical
>>>> nature, and that, perhaps, he doesn't understand how link-region
>>>> works, and what it does. Perhaps he only knows HG TPs through the
>>>> map or something. (all hg link UIs end up placing hyperlinks on the
>>>> maps, but all except link-region end up placing them very far away
>>>> from the main cluster of regions)
>>>>
>>>> On 10/25/2010 9:42 AM, Shaun T. Erickson wrote:
>>>>> Diva,
>>>>>
>>>>> He doesn't (necessarily) want to link to them - he wants them to
>>>>> link to him. So that in that foreign grid, the link to his grid
>>>>> acts in that grid, like a hyperlink to your webpage does on someone
>>>>> else's page.
>>>>>
>>>>> It seems to me that all he needs to do is contact the foreign grid
>>>>> operator and see if they'd be willing to link to a sim in his grid.
>>>>>
>>>>> -ste
>>>>>
>>>>> On 10/25/10 12:38 PM, Diva Canto wrote:
>>>>>> That's how the HG works. HG 1.5 is on a grid-basis. The entrance to
>>>>>> grids is directed at the Gatekeeper service.
>>>>>> When you link to, for exmple, hg.osgrid.org:80 you are requesting the
>>>>>> Gatekeeper of osgrid to link to whatever the default region entry
>>>>>> is in
>>>>>> OSGrid, consequently being able to visit all regions in OSGrid that
>>>>>> allow foreign visitors. When you link to hg.osgrid.org:80:Some Region
>>>>>> you are requesting th Gatekeeper to link to a specific region on that
>>>>>> grid, permissions allowing.
>>>>>>
>>>>>> Maybe I'm still missing something.
>>>>>>
>>>>>> On 10/25/2010 9:19 AM, Shaun T. Erickson wrote:
>>>>>>> It sounds like what he wants is for foreign grids to link to a
>>>>>>> region
>>>>>>> in his grid, so that users from that grid can get to his, without
>>>>>>> him
>>>>>>> having to maintain a region in the other grid.
>>>>>>>
>>>>>>> -ste
>>>>>>>
>>>>>>> On 10/25/10 12:16 PM, Jor3l Boa wrote:
>>>>>>>> Yes diva, but his idea is when you tp to that region actually
>>>>>>>> switch
>>>>>>>> grids (tp-to-grid instead of tp-to-sim), actually makes sense if
>>>>>>>> you
>>>>>>>> want people visit a bunch of regions with one entrance
>>>>>>>>
>>>>>>>> 2010/10/25 Diva Canto <diva at metaverseink.com
>>>>>>>> <mailto:diva at metaverseink.com>
>>>>>>>> <mailto:diva at metaverseink.com>>
>>>>>>>>
>>>>>>>> Maybe I'm missing something, but what you're describing is how the
>>>>>>>> Hypergrid works, redirect and all. It's not an http redirect,
>>>>>>>> because the viewer doesn't do that protocol, but it's
>>>>>>>> TeleportFinish, which is the Linden equivalent of an http redirect.
>>>>>>>>
>>>>>>>> If you use the link-region console command you place a region on
>>>>>>>> your map (you see it on your map) that belongs to another grid.
>>>>> _______________________________________________
>>>>> Opensim-dev mailing list
>>>>> Opensim-dev at lists.berlios.de <mailto:Opensim-dev at lists.berlios.de>
>>>>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>>>>
>>>>
>>>> _______________________________________________
>>>> Opensim-dev mailing list
>>>> Opensim-dev at lists.berlios.de <mailto:Opensim-dev at lists.berlios.de>
>>>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>>
>>>
>>> _______________________________________________
>>> Opensim-dev mailing list
>>> Opensim-dev at lists.berlios.de  <mailto:Opensim-dev at lists.berlios.de>
>>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>
>>
>> _______________________________________________
>> Opensim-dev mailing list
>> Opensim-dev at lists.berlios.de  <mailto:Opensim-dev at lists.berlios.de>
>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>
>
>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev