Talk:Hypergrid - Revision history

Maria Korolov: /* A Different Use Case: Organic Hypergrid Growth Based on Business and Individuals */ new section

2009-11-26T17:08:14Z

‎A Different Use Case: Organic Hypergrid Growth Based on Business and Individuals: new section

Ktweedy1: /* My Vision for Asset/Inventory Servers */

2009-02-06T14:53:41Z

‎My Vision for Asset/Inventory Servers

Aiaustin: /* Federated Virtual Worlds with Different Properties */ corrected a few typos

2009-02-05T21:49:52Z

‎Federated Virtual Worlds with Different Properties: corrected a few typos

Ktweedy1: /* My Vision for Asset/Inventory Servers */

2009-02-05T16:09:59Z

‎My Vision for Asset/Inventory Servers

Ktweedy1: /* My Vision for Asset/Inventory Servers */

2009-02-05T16:09:15Z

‎My Vision for Asset/Inventory Servers

Ktweedy1: /* My Vision for Asset/Inventory Servers */

2009-02-05T16:07:37Z

‎My Vision for Asset/Inventory Servers

WWWench at 04:35, 5 February 2009

2009-02-05T04:35:04Z

Dalien: /* Back to Reality */

2009-02-05T00:21:44Z

‎Back to Reality

Dalien: /* Back to Reality */

2009-02-05T00:04:53Z

‎Back to Reality

RalfHaifisch: /* Content Security */

2009-02-04T22:53:06Z

‎Content Security

← Older revision		Revision as of 17:08, 26 November 2009
Line 157:		Line 157:

	So to me, Opensim should never consider elimination of instance asset storage and HG should be promoted.		So to me, Opensim should never consider elimination of instance asset storage and HG should be promoted.
		+
		+	== A Different Use Case: Organic Hypergrid Growth Based on Business and Individuals ==
		+
		+	Another potential use of hypergrid-enabled grids is that of the hyperlink-enabled Website -- to allow businesses, organizations, and individuals to set up sites that others can visit.
		+
		+	At first -- just as on the early Internet -- visitors will be limited to invited guests because they have the address of the grid, or instructed on how to arrive on the company's Website. Then some of the more interesting destinations will be written up in blogs or magazines, or listed in directories, or have hypergates pointing to them on other grids.
		+
		+	Directories are important during this early stage because there are too few sites for search engines to work yet -- and few enough to organize in a directory.
		+
		+	Finally, we'll see the rise of search engines that index sites by tracking inbound links -- either from the Web itself, or from other grids. It may also be possible to track traffic through browser-plugins or other tools that travelers would bring with them as they traverse the hypergrid.
		+
		+	Before any of this happens, though, we'll need to fix the 4096-teleportation bug -- it does more to hurt hypergridding than anything else out there, even though it's actually a hypergrid problem.

← Older revision		Revision as of 14:53, 6 February 2009
Line 79:		Line 79:

	A. I see content distributors very similar to content creators. I see these guys as avatar login providers or asset/inventory servers that content creators can use. If they are avatar servers then as I buy stuff and have it in inventory it will need to maintain copies of them and serve them as well as references to other asset servers and inventory servers that I have license use of content from.		A. I see content distributors very similar to content creators. I see these guys as avatar login providers or asset/inventory servers that content creators can use. If they are avatar servers then as I buy stuff and have it in inventory it will need to maintain copies of them and serve them as well as references to other asset servers and inventory servers that I have license use of content from.
		+
		+	B. Be able to sell or delivery content from other content providers. An example of this would be a mall. The purchase of the content may go through my region services but end need to either be deliveryed to the consumer by this point of contact or be delivery by a grid hosting the assets that are being purchased.

	'''3. Content Consumers/Users'''		'''3. Content Consumers/Users'''

@@ Line 107: / Line 107: @@
 The Hypergrid concept seems to be very well placed to allow for the wide range of types of topology, security management and asset exchange or mappings that will be needed in future for virtual worlds to be practically management and evolved.
-It would be interesting to explore if the following could all be sported by the prop sowed architecture and mechanism:
+It would be interesting to explore if the following could all be sported by the proposed architecture and mechanism:
-* Ability to move between grids managed and served by separate communities (as now;
+* Ability to move between grids managed and served by separate communities (as now);
-* Ability to limit regions open or closed to hypergrid travellers not authenticated directly on the visited grid (other preferably just seeing void spaces water);
+* Ability to limit regions open or closed to hypergrid travellers not authenticated directly on the visited grid (others preferably just seeing void space/water);
 * Ability to go into Grid with different capabilities (e.g. concierge supported meeting zones optimized for larger groups/conferences, etc.);
 * Ability to enter a RexServer (rich 3D mesh) supported region from a standard region;
@@ Line 120: / Line 120: @@
 '''RalfHaifisch says:'''
 == Content Security ==

@@ Line 94: / Line 94: @@
 A. As a content viewer I may want to get information on the source of the asset so I can go there and look at the assets to buy them.  Talk to the creator even if they so not have an account in the grid I am looking at the content in.
-So I know I am presenting more than I am solving but mostly trying to expand the vision of what asset/inventory servers can be.  Technically I know there are lots of issues to doing this.  To me SL will not progress their viewer fast enough so I believe that there needs to be a new viewer that will support these concepts capabilities.
+So I know I am presenting more than I am solving but mostly trying to expand the vision of what asset/inventory servers can be.  Technically I know there are lots of issues to doing this.  To me SL will not progress their viewer fast enough so I believe that there needs to be a new viewer that will support these concepts and capabilities.
 First time I have posted something on the site.  Hope you guys find this interesting and helpful.

@@ Line 90: / Line 90: @@
 '''4. Content Viewers'''
-These are people that only have rights to view the content while they are in the sim or view the content of another avatar will it is in range.  Their license has to be defined when they enter the grid that says their limited use of the content.  (Note I think this is an issue in the current hypergrid in that when I hypergrid anywhere I am not required to accept a terms of use like I do if I make an account some where.
+These are people that only have rights to view the content while they are in the sim or view the content of another avatar while it is in range.  Their license has to be defined when they enter the grid that says their limited use of the content.  (Note I think this is an issue in the current hypergrid in that when I hypergrid anywhere I am not required to accept a terms of use like I do if I make an account some where.
 A. As a content viewer I may want to get information on the source of the asset so I can go there and look at the assets to buy them.  Talk to the creator even if they so not have an account in the grid I am looking at the content in.

@@ Line 76: / Line 76: @@
 '''2. Content Distributors'''
-A person that resells, distributes or host other people's content.  XStreetSL could be this, but also Renderosity, RuntimeDNA some day and many new ones that will be coming.  Also Avatar hosting services where you login to start your avatar and start running around on various grids.
+A person that resells, distributes or host other people's content.  XStreetSL could be this, but also Renderosity, RuntimeDNA some day and many new ones that will be coming like XRGrid.com.  Also Avatar hosting services where you login to start your avatar and start running around on various grids.
 A. I see content distributors very similar to content creators.  I see these guys as avatar login providers or asset/inventory servers that content creators can use.  If they are avatar servers then as I buy stuff and have it in inventory it will need to maintain copies of them and serve them as well as references to other asset servers and inventory servers that I have license use of content from.

← Older revision		Revision as of 04:35, 5 February 2009
Line 141:		Line 141:

	however, if something like rights management is only possible in the mid term - great. better take the time needed to investigate some frameworks.		however, if something like rights management is only possible in the mid term - great. better take the time needed to investigate some frameworks.
		+	-----------------------
		+	'''Brianna says'''
		+	== Growth Features ==
		+
		+	Hypergrid allows two important elements that do not exist at the present time.
		+
		+	A viable shopping mall implemented via the V$ monetary system, available to all regardless of grid.
		+
		+	A performance oriented set of regions where grid asset servers and neighbor regions influence can be totally eliminated.
		+
		+	The grid storage presently for asset management favors a lots of data flowing in every direction for the viewability of a wandering Avatar, The associated lag is very difficult to balance but a HG enabled 'cloud' can better suit heavy loaded situations such as a mall or a sailing regatta.
		+
		+	So to me, Opensim should never consider elimination of instance asset storage and HG should be promoted.

← Older revision		Revision as of 00:21, 5 February 2009
Line 24:		Line 24:
	* A coarse-grained selection via the concept of Suitcase (explained [[Hypergrid_Inventory_Access \| here]]). This is the simplest thing to do, it doesn't require any changes to the viewer.		* A coarse-grained selection via the concept of Suitcase (explained [[Hypergrid_Inventory_Access \| here]]). This is the simplest thing to do, it doesn't require any changes to the viewer.

−	~~-------------------~~
−	~~'''dalien says:'''~~
−
−	* a client-side proxy, which would serve as a "region" for the viewer, and would serve as a "client" for the region, and would Y-split the traffic from the LL viewer ? The upside is it is as effective as a "separate viewer". Also, theoretically (?) it might allow to interop with multiple viewer types. The downside is that it is darn much more complex compared to flipping a bit (and is horribly close to NAT(for the networking types). But there's one more unrelated upside - this would allow in the future to tackle the IPv6 support pretty trivially and step by step.

	------------------		------------------

← Older revision		Revision as of 00:04, 5 February 2009
Line 24:		Line 24:
	* A coarse-grained selection via the concept of Suitcase (explained [[Hypergrid_Inventory_Access \| here]]). This is the simplest thing to do, it doesn't require any changes to the viewer.		* A coarse-grained selection via the concept of Suitcase (explained [[Hypergrid_Inventory_Access \| here]]). This is the simplest thing to do, it doesn't require any changes to the viewer.

		+	-------------------
		+	'''dalien says:'''

		+	* a client-side proxy, which would serve as a "region" for the viewer, and would serve as a "client" for the region, and would Y-split the traffic from the LL viewer ? The upside is it is as effective as a "separate viewer". Also, theoretically (?) it might allow to interop with multiple viewer types. The downside is that it is darn much more complex compared to flipping a bit (and is horribly close to NAT(for the networking types). But there's one more unrelated upside - this would allow in the future to tackle the IPv6 support pretty trivially and step by step.

	------------------		------------------

← Older revision		Revision as of 22:53, 4 February 2009
Line 120:		Line 120:
	We are preparing our own Hypergrid accessible grid, but it does need more thought on how to mange the areas we want open and those we want to remain limited. The group management framework within Opensim needs to mature before we can set that up better, and prevent accidental (or deliberate) loss or messing up of builds.		We are preparing our own Hypergrid accessible grid, but it does need more thought on how to mange the areas we want open and those we want to remain limited. The group management framework within Opensim needs to mature before we can set that up better, and prevent accidental (or deliberate) loss or messing up of builds.

		+	'''RalfHaifisch says:'''
	== Content Security ==		== Content Security ==