<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<small><span class="Apple-style-span" style="border-collapse:
separate; color: rgb(0, 0, 0); font-family: 'Times New Roman';
font-style: normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: 2;
text-indent: 0px; text-transform: none; white-space: normal;
widows: 2; word-spacing: 0px; font-size: medium;"><span
class="Apple-style-span" style="font-family: arial,sans-serif;
font-size: 16px;"><span title="" style="background-color:
rgb(230, 236, 249); color: rgb(0, 0, 0);"></span></span></span>Marck
Hi, thanks for your suggestion, the idea that you propose to raise
in osgrid-forums sounds interesting as a way to do this in osgrid
provisional, but this should be realized, only allow that
functionality in osgrid, and not at all other small or large grids
that may arise or exist. I think the basic idea is more
interesting if provided as a configurable option in opensim.ini
and each grid or network operator may determine if this
functionality is allowed or not in the grid, for example with
something like </small><small>"EnableWormHoleRegion =
true/false". </small><small>Finally given the opportunity to use
this feature, each operator may decide to allow or disallow
relevant. There would be more interesting?<br>
I want to clarify that my point is not a request for the
development team, but an idea thrown on the table as a possibility
that perhaps many would consider interesting and they might wish
to use. Personally I have linked allGrids that I know registered
in thehypergates on the map of my grid, some people get my grid to
use as a gateway to other grids. <br>
Greetings and thanks for answering :)<br>
<br>
<br>
---<br>
Hola Marck, gracias por tu sugerencia, la idea que tu propones de
plantearlo en osgrid-forums suena interesante como una forma
provisional de lograrlo en osgrid, pero esto, en caso de hacerse
realidad, solamente permitiría dicha funcionalidad en osgrid, y no
en todos los demás grids grandes o pequeños que puedan surgir o ya
existen. Pienso que la idea de fondo es mas interesante si se
brindara como una posibilidad configurable en opensim.ini y que
cada operador de grid o red pudiera establecer si dicha
funcionalidad es permitida o no en su grid, por ejemplo con algo
como "EnableWormHoleRegion = true/false". Finalmente brindada la
posibilidad de utilizar esta funcionalidad, cada operador podría
decidir pertinente permitirlo o no permitirlo. No seria mas
interesante?</small><br>
<small>Quiero hacer la aclaración de que lo que planteo no es una
petición para el equipo de desarrollo, sino una idea tirada arriba
de la mesa como una posibilidad que quizás muchos podrían
considerar interesante y quizás desearían utilizar. En lo personal
yo tengo linkeados todos los grids que conozco a travez de
thehypergates en el mapa de mi grid, algunas personas llegan a mi
grid para usar como gateway a otros grids. <br>
Saludos y gracias por responder :)</small><br>
<br>
<br>
El 26/10/10 05:22, Marck escribió:
<blockquote cite="mid:4CC6819E.3080501@nexgo.de" type="cite">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.
<br>
<br>
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.
<br>
<br>
Maybe you want to suggest the addition of such a "wormhole"
service in the OSgrid forums?
<br>
<br>
<br>
Mentolyptus wrote:
<br>
<blockquote type="cite">Diva:
<br>
I understand what you say, I'm glad you understand Spanish, it's
<br>
frustrating difficulty of the language, even attempt to learn
English
<br>
but it is hard:)
<br>
The whole issue of the idea of wormholes has been streaky and
maybe I
<br>
did not find a way to explain properly.
<br>
There are things that give de facto, for example, you may
perhaps osgrid
<br>
not want to have a direct link to my regions?, But in fact it
does,
<br>
because I have a server running mode osgrid registered
gridhypergrid
<br>
this connected to link -region with my main server that operates
in
<br>
Hypergreen. This region in osgrid all we have is a teleport that
leads
<br>
to my main server outside osgrid. :] Is doing the work that I
propose
<br>
for a wormhole-region.
<br>
The initial idea of wormholes is simple, can be summed up as
Shaun said
<br>
when he said: "It sounds like What He Wants Is for Foreign grids
to link
<br>
to a historical region in grid, so users from That Can Get That
grid to
<br>
historical , Without him
<br>
HAVING to Maintain a grid region in the Other. "
<br>
I can have a region in osgrid registered, and many other regions
in
<br>
other grids that allow me to and from these regions to advertise
or
<br>
redirect to my server that is outside of these grids with a
teleport. It
<br>
actually raised is given. The only difference is that I need to
do a
<br>
server-mode opensim in gridhypergrid connected to each of these
grids
<br>
hacieno bridge, consuming resources, and forcing the visitor to
make a
<br>
stop before reaching my final region directly. Means?
<br>
In contrast, the wormhole-region could do the same job by simply
<br>
recording a "virtual region" or region of linkage between both
grids,
<br>
and this without consuming resources or at least consume fewer
<br>
resources, since no region would be a real physical terrain,
objects, or
<br>
even user database or only a mark on the map as a link-visible
region
<br>
that would redirect the server end. That's why I compared it to
a
<br>
redirection of a web page. Maybe just a crazy idea XD
<br>
True, there are grids that do not have to want to link to the
grid for
<br>
others, but the fact is that almost all standard grids are
beginning to
<br>
use Hypergreen and are open to traffic in return. and everything
<br>
provided to travelers coming and going quality improvement
experience.
<br>
This may make travel less cumbersome. As things now are
sometimes
<br>
necessary to make several stops to reach a destination.
<br>
The wormhole-region simply serve a gateway function visible on
the map
<br>
that would allow to have a grid in a given region without having
to
<br>
actually have a region in the grid.
<br>
Thanks for replying, did not think were going to devote much
time to
<br>
meet my crazy O:)
<br>
<br>
-Mento
<br>
<br>
<br>
El 25/10/10 15:55, Diva Canto escribió:
<br>
<blockquote type="cite">I don't think it's lost in translation
as I can read and understand
<br>
Spanish -- it's funny that the translator transforms Hypergrid
into
<br>
Hypergreen :-)
<br>
<br>
You seem to be mixing many different things. The Linden viewer
has its
<br>
own version of http redirects. When we have virtual worlds on
the
<br>
regular web browser, the Hypergrid will use http redirects, no
more no
<br>
less. (I have a version of the Hypergrid that does exactly
that)
<br>
<br>
But Hypergrid without control on the part of grid operators
would be a
<br>
really bad idea. Not all virtual worlds want to be part of it.
And
<br>
just because your grid links to, say, osgrid doesn't mean that
osgrid
<br>
wants to link back to yours. Just like on the web: just
because your
<br>
site links to, say, Slashdot doesn't mean that Slashdot wants
to link
<br>
back to your site. The static hyperlinks reflect social
dynamics, like
<br>
on the web or even like on twitter.
<br>
The process to discover virtual worlds that aren't linked
needs
<br>
additional services, like search or directories.
<br>
<br>
On 10/25/2010 10:21 AM, Mentolyptus wrote:
<br>
<blockquote type="cite">I regret the poor quality of my
English, and need to use a
<br>
translator, I think this merely to explain clearly the idea.
<br>
Diva, I understand basically how it works Hypergrid,
although it is a
<br>
certainty that I do not understand as well as you. Anyway,
what I
<br>
propose is not a criticism of the current operation of
hypergrid, but
<br>
an idea looking for a way to allow the unification of
hypergrid. I
<br>
think the basic idea has been misunderstood.
<br>
Thanks for replying, and thanks to all the development team
for the
<br>
excellent work they do for us. If some of the idea put
forward has
<br>
been going around in someone's head, who knows, maybe it is
recycled
<br>
into something good :)
<br>
if there is anyway so there will be many good things.
<br>
<br>
A Hypergreen free, united without borders, where all grids
are joined
<br>
into one, sounds like a good idea
<br>
----------------------------------
<br>
<br>
Yo lamento la mala calidad de mi ingles, y necesitar usar un
<br>
traductor, pienso que esto limita poder explicar claramente
la idea.
<br>
Diva, entiendo basicamente como funciona hypergrid, aunque
es una
<br>
certeza que no lo comprendo tan bien como usted. De todas
formas lo
<br>
que propongo no es una critica al actual funcionamiento de
hypergrid,
<br>
sino una idea a futuro para una forma de permitir la
unificacion del
<br>
hypergrid. Pienso que la idea de fondo se ha malentendido.
<br>
Gracias por responder, y gracias a todo el equipo de
desarrollo por
<br>
el excelente trabajo que hacen por nosotros. Si algo de la
idea
<br>
planteada ha quedado dando vueltas en la cabeza de alguien,
quien
<br>
sabe, quizas se recicle en algo bueno :) si no es asi de
todas formas
<br>
habra muchas cosas buenas.
<br>
<br>
Un hypergrid libre, unificado sin fronteras, donde todos los
grids se
<br>
unen en uno solo, suena como una buena idea
<br>
<br>
<br>
<br>
El 25/10/10 14:50, Diva Canto escribió:
<br>
<blockquote type="cite">If that's all, then ... ok. I
thought I heard wishes of a technical
<br>
nature, and that, perhaps, he doesn't understand how
link-region
<br>
works, and what it does. Perhaps he only knows HG TPs
through the
<br>
map or something. (all hg link UIs end up placing
hyperlinks on the
<br>
maps, but all except link-region end up placing them very
far away
<br>
from the main cluster of regions)
<br>
<br>
On 10/25/2010 9:42 AM, Shaun T. Erickson wrote:
<br>
<blockquote type="cite">Diva,
<br>
<br>
He doesn't (necessarily) want to link to them - he wants
them to
<br>
link to him. So that in that foreign grid, the link to
his grid
<br>
acts in that grid, like a hyperlink to your webpage does
on someone
<br>
else's page.
<br>
<br>
It seems to me that all he needs to do is contact the
foreign grid
<br>
operator and see if they'd be willing to link to a sim
in his grid.
<br>
<br>
-ste
<br>
<br>
On 10/25/10 12:38 PM, Diva Canto wrote:
<br>
<blockquote type="cite">That's how the HG works. HG 1.5
is on a grid-basis. The entrance to
<br>
grids is directed at the Gatekeeper service.
<br>
When you link to, for exmple, hg.osgrid.org:80 you are
requesting the
<br>
Gatekeeper of osgrid to link to whatever the default
region entry
<br>
is in
<br>
OSGrid, consequently being able to visit all regions
in OSGrid that
<br>
allow foreign visitors. When you link to
hg.osgrid.org:80:Some Region
<br>
you are requesting th Gatekeeper to link to a specific
region on that
<br>
grid, permissions allowing.
<br>
<br>
Maybe I'm still missing something.
<br>
<br>
On 10/25/2010 9:19 AM, Shaun T. Erickson wrote:
<br>
<blockquote type="cite">It sounds like what he wants
is for foreign grids to link to a
<br>
region
<br>
in his grid, so that users from that grid can get to
his, without
<br>
him
<br>
having to maintain a region in the other grid.
<br>
<br>
-ste
<br>
<br>
On 10/25/10 12:16 PM, Jor3l Boa wrote:
<br>
<blockquote type="cite">Yes diva, but his idea is
when you tp to that region actually
<br>
switch
<br>
grids (tp-to-grid instead of tp-to-sim), actually
makes sense if
<br>
you
<br>
want people visit a bunch of regions with one
entrance
<br>
<br>
2010/10/25 Diva Canto <<a class="moz-txt-link-abbreviated" href="mailto:diva@metaverseink.com">diva@metaverseink.com</a>
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:diva@metaverseink.com"><mailto:diva@metaverseink.com></a>
<br>
<a class="moz-txt-link-rfc2396E" href="mailto:diva@metaverseink.com"><mailto:diva@metaverseink.com></a>>
<br>
<br>
Maybe I'm missing something, but what you're
describing is how the
<br>
Hypergrid works, redirect and all. It's not an
http redirect,
<br>
because the viewer doesn't do that protocol, but
it's
<br>
TeleportFinish, which is the Linden equivalent of
an http redirect.
<br>
<br>
If you use the link-region console command you
place a region on
<br>
your map (you see it on your map) that belongs to
another grid.
<br>
</blockquote>
</blockquote>
</blockquote>
_______________________________________________
<br>
Opensim-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a>
<a class="moz-txt-link-rfc2396E" href="mailto:Opensim-dev@lists.berlios.de"><mailto:Opensim-dev@lists.berlios.de></a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
<br>
<br>
</blockquote>
<br>
_______________________________________________
<br>
Opensim-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a>
<a class="moz-txt-link-rfc2396E" href="mailto:Opensim-dev@lists.berlios.de"><mailto:Opensim-dev@lists.berlios.de></a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
<br>
</blockquote>
<br>
<br>
_______________________________________________
<br>
Opensim-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a>
<a class="moz-txt-link-rfc2396E" href="mailto:Opensim-dev@lists.berlios.de"><mailto:Opensim-dev@lists.berlios.de></a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
<br>
</blockquote>
<br>
<br>
_______________________________________________
<br>
Opensim-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a>
<a class="moz-txt-link-rfc2396E" href="mailto:Opensim-dev@lists.berlios.de"><mailto:Opensim-dev@lists.berlios.de></a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
<br>
</blockquote>
<br>
<br>
<br>
_______________________________________________
<br>
Opensim-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
<br>
</blockquote>
_______________________________________________
<br>
Opensim-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
<br>
</blockquote>
<br>
</body>
</html>