Tuesday, June 30, 2009

0
A Virtual World like Polka-dot Flypaper

Recently, the popular Second Life blogger Hamlet Au made a post raising a point of contention against Chris Abraham's remarks unfavorably highlighting the differences between SL and Twitter.  The specific point Hamlet took issue with went roughly as follows. Twitter is not like Second Life in and of the fact that it is "cheap, light, and open."  In essence Chris is pointing out several truths regarding the major differences between Twitter and Second Life.  It is true that Twitter is cheap, its free.  It's also true that twitter is light on system resources in comparison to SL, one is a text-based app, the other is a dynamic real time 3D environment.  Additionally it is also true that in relative terms Twitter is far more open than SL.  The potency of Twitters' API has been on prominent display throughout the #Iranelection crisis.  SL has a long way to go before it can boast such a promiscuous architecture.   

In response, Hamlet listed off a series of advantages SL has over Twitter.  To his mind SL has the advantages of being "unique, sticky, and profitable."  Unique in the fact that there is no real direct competitors to SL, aside from the Opensim grids.  Sticky in how much time users spend using the different services.  For this Hamlet points to statistics showing the huge lead in minutes per month spent on-platform SL enjoys over Twitter.  The last point, profitability is almost a gimme, in and of the fact that Twitter is completely funded by venture capital whereas Linden Labs makes a tidy profit off leasing land to residents.  

For the full post, you can read it here.  Honestly I'm not going to take sides on this one because while I view the argument as rather immature and the comparisons a bit sketchy, the truth is that both of them are right on all points.  What both of them are doing amounts to two blind men feeling up different sides of a elephant.  In this case lets call that elephant The Killer Social Platform.  In order to be effective and pervasive, this platform would have to be open, light, cheap, and unique.  In order to be sustainable, it would have to be sticky and profitable.  In more whimsical terms, the Killer Social Platform has got to be like polka-dot flypaper.  It has to be cheap and pervasive enough that its everywhere you want it to be, and compelling and unique enough to keep users hooked once they've tried it.  

Maybe the solution isn't text based like Twitter, or 3D like SL. Maybe it resides in the middle.  Perhaps the solution is a open, hostable 2D virtual world that utilizes ubiquitous lightweight technology like Flash.  It might be isometric like Metaplace, but my hunch is that a side scrolling style world would spread far faster, as its far easier to create content from a side view.  To be fair to Metaplace, they do a excellent job simplifying the task of bringing content reliably into a isometric world, something I applaud.  Flash is lightweight enough and ubiquitous enough that it could be embedded practically anywhere, and website embedding could allow non-users a window into the world prior to actually signing up to participate.  This is one of Twitters' strong points, as anyone can follow a conversation without signing up, effectively selling the receptive to the platforms' utility.  With persistent hosted environments comes the opportunity for profit, whether through hosting fees as SL does or through advertising. 

Additional profit can come from the sale of additional functionality, or the capacity to handle that functionality. Ownable persistent virtual property has definite inherent stickiness to it, especially when coupled with strong traditional social networking services such as groups, events, and content sharing.   The visual, location based aspect of SL coupled with its ability to allow the user to participate simultaneously in larger discussions is a large contributing factor to its stickiness.   In regards to openness, that is genuinely a structural business decision that must be made early in a product's development.  

The degree of that openness is debatable, as some will lean towards a completely open virtual framework for anyone to host, while others will inevitably prefer the hosted API route of Twitter.  Either way, the current trends point toward openness as a key element to widespread adoption.  Now we're left with uniqueness.  The fact of the matter is that a system that can pull all of the other elements off, and do it well, will be unique.  Sure, there may be competition, everyone believes they can invent a better wheel. Competition need not be viewed as a bad thing though. Historically competition has always been a excellent motivator for innovation.  

I'll give the topic a rest for now, mostly due to the fact I am beginning to lose my train of thought in a haze of sleep deprivation.  I'll probably come back and describe this platform some more in the future, gotta tease this string out to see what unravels.

Continue Reading

Monday, June 29, 2009

0
Sketchbook Dump Highlight Post




If you follow me on Deviantart, you'll know that I recently did a two part marathon sketchbook dump that ended with nearly twenty new pictures being uploaded.  From this I learned two things. One, I need a dedicated flatbed scanner, because taking snapshots of each sketch just doesn't cut it when it comes to quality.  Two, I have a weird obsession with drawing heads.  Maybe this has to do with the fact I'm insecure about my ability to effectively draw faces, so in response I just draw a lot of them.  Instead of spamming you with all the pictures, I'll give you a sampling of my personal favorites from the batch.  To see all of them, feel free to check out my deviant page.


A fun little cartoon beastie I did while 
experimenting with combinations of art styles.
This was an attempt to merge art nouveau and 
hispanic chibi (if that's even a style)


Not everything was cute, however.  These
are a couple of pen sketch concepts of some
generic cyberpunk/horror characters.



One of my absolute favorites from 
the set was also the last I uploaded.  
I think I have a thing for biomech vehicles.
Whether I'm any good at drawing them 
is a completely different matter.

Hope you take a look at the full dump, and please feel free to let me know what you think!  This artist loves feedback.

Continue Reading

0
Joomla for the Metaverse

I recently posted this question on Twitter and Plurk: if Opensim is the Apache of the Metaverse, then what will be the Joomla of the Metaverse?  Clearly I need to work on my grammar when tweeting/plurking, but I was being serious.  This isn't a idle or rhetorical question, its something which has to be answered if Metaverse solutions like Opensim are ever going to truly become the next incarnation of the Web.  

While it is true that the Web grew through its infancy without much in the way of content management software, it has become a essential ingredient to its continued growth.  Even in its early years, the growth of the web was spurred by programs and services like Geocities and Dreamweaver. These served to sufficiently lower the bar of entry into the world of web design to allow those with little or no technical knowledge quickly create a web presence.  This created a primordial sea of amateur designers and content from which the committed and skilled graduated to create bigger and better things.  

Right now the Metaverse scene is currently in the AOL stage, with a few centralized services offering walled garden experiences wherein they hold the monopoly on content and users.  A few pioneers (OSGrid, ReactionGrid, Openlife) cling to the fringes, boldly attempting to create more open alternatives.  However on their own they cannot compete on the scales of content and user population that the walled gardens offer.  This is why the developments in cross grid transportation in Opensim are so widely hailed, because in many ways they are the equivalent to the most powerful element of the Web: the hyperlink.  Once a critical mass of grids become connected and standards arise for commerce and content sharing, this new web of grids will begin to eclipse the walled garden providers.  But this critical mass must exist.

This is where the question of content management becomes so crucial.  Without tools and services to lower the barrier of entry, the growth of the open Metaverse will be stunted.    The open Metaverse will need its Geocities, its Dreamweaver, and its Joomla.  The barrier of entry must be lowered, which means making the deployment and management of entire grids simple, pain-free, and dirt cheap.  When the barrier of entry is lowered, it will open the gates to a stampede of amateur Metaverse creators seeking their slice of the pie.  Now to be clear, most of these amateurs will not create great virtual environments.  Just like the web now, most of the content will be mediocre. 

A Metaverse Geocities will probably offer free hosting for simple one-sim grids, with a simple template-based creation tools.  Revenue will most likely be provided in much the same way Geocities provided it, embedded ads for free accounts, or a monthly cost for those who chose to upgrade.  An astute observer will note some similarities between this and grid services currently provided, sans the advertising.  One of the primary differences will again be in the linking, as users of such a service will occupy a grid of their own, populated only with their own sims and any hypergrid sims that they should choose to link to.  

A Metaverse Dreamweaver will most likely provide a world creation tool set based heavily off of the tool sets currently used by MMOG developers to layout large environments.  When augmented with a marketplace function (much like a pan-grid XStreetSL perhaps), it will facilitate a drag-and-drop style of world creation.  Much in the same way Dreamweaver simplified complex web functionality into a WYSIWYG interface, its Metaverse cousin must do as well.  Commonly occurring complex scripted objects would be abstracted into click-and-place entities.  Any fine tuning of these worlds would most likely be performed in-world, the Metaverse equivalent to hand-rolling HTML and Javascript. 

Finally, a Metaverse Joomla would abstract and simplify the maintenance of large, complex grids in much the same way Joomla simplifies and abstracts the maintenance of large complex websites:  by providing high-level editorial, publishing, and management tools.  In the case of the Metaverse variant, this would entail on-the-fly creation of template based sims, the ability to monitor real-time activity, permissions based administrative controls, and the ability to extend the grid to include third-party functionality and themes.

I cannot begin to stress how important these services will be to the growth of a open Metaverse. I've listed these three comparisons in this order for a reason.  It is most likely the order in which they must occur.  Right now the major battles of cross-grid content transfer loom just over the the horizon, as the first transfer mechanics are just now being created.   While that battle rages, a Metaverse Geocities can be introducing the world at large to the idea of being a virtual world maker.  Inevitably some compromise will be reached, and a Metaverse Dreamweaver would capitalize from whatever content marketplace system emerges.  As these worlds grow and mature, and the need for simple dynamic management of large scale grids emerges, a Metaverse Joomla can fill the need.

So the question remains: if Opensim is the Apache of the Metaverse, what will be its Joomla?

Continue Reading

0
Quick thoughts on motivation in MMO design

I wanted to take a quick break from my talks on technology and more serious stuff to share with you a couple thoughts I've just had regarding social dynamics in MMOs, and online games in general. I hit upon them reading this article from WebWorkerDaily, which mulls the sociological and psychological consequences of looking for a job in a crowded job market. The basic thrust of the article is that as the number of potential candidates for a freelance position increases, an individual's confidence in getting that position drops dramatically. This immediately reminded me of the psychological effect know as the "Diffusion of Responsibility". This effect is tragically exemplified by the murder of Kitty Genovese, a young women who was stabbed to death on a New York street.

What makes her case noteworthy and tragic is the fact that there were dozens of people who either witnessed the murder or heard it occuring, and yet nobody took the initiative to save her or even call the police. In both cases we see a parallel behavioral trait emerging. In situations where there is a clear goal which requires a active commitment, a persons' willingness to engage is negatively impacted by the size of the crowd present. This is a important effect that designers of online games must take into consideration when crafting both collaborative and competitive scenarios. This may be one of the reasons why random matchmaking is so effective at spurring competition. By limiting the scope of competitors any one player will encounter in a play session, the concept of winning becomes psychologically acceptable.

Collaboration is a much trickier system to balance, but the basic principle still holds true. Smaller teams tend to be far better at organizing to the task at hand than larger ones. This would suggest that systems which allow for high levels of stratification in leadership would be the most successful at promoting collaborative play. The trick comes in the assignment and enforcment of tasks, something which often is a stumbling block for many systems. For instance, Planetside utilizes a highly stratified leadership structure with player groups consisting of squads, platoons, outfits, and armies in order of ascending permenance and scope. Often however, there is a serious lack of organization and discipline within these rather stratified systems because there is very little by way of carrots and sticks to encourage unit cohesion. A top level "general" can demand focus be given to a certain region until they're blue in the face, but without any adequate method of incentivizing that focus, their orders come across far more as a suggestion than a imperitive.

Another factor worth considering is the perceived cost of acting. In most online games this cost is time. If a player perceives a activity with a high desirability but a large time commitment, and another activity with a moderate or low desirability but with little or no time commitment, a large portion will inevitably go with the latter option. From a competitive side, this is one of the big drawbacks to random matchmaking, as it requires all the participants to wait long enough for a match to fill enough slots to be worthwhile. From a collaborative end, it means that when given a choice regarding several available collaborative tasks that will help the team, the trend will be for players to choose the action with the least time cost, even if it is detrimental to a teams' overall chances of success. In the case of Planetside, there very well may be incentives in place, but if it is not immediately and inutitively accesible to the commanding players in a way that encourages its use, then inevitably those palyers will take the route which requires less time and simply rage on the chat channel.

So what are the lessons here?
  1. Keep group sizes small to keep competiton and collaboration fresh and personal
  2. Create stratified levels of leadership to prevent task overload for any one player or role
  3. Be mindful of the impact of large groups and how they can effect competition and collaboration
  4. Ensure that the cost of actions, be it real or perceived is balanced in a way that promotes the kind of behavior that is desired.
  5. Create leadership functions which allow for painless task assignment and role enforcement
Ok, enough with my ramblings. Back to building characters in Flash!

Continue Reading

Saturday, June 27, 2009

2
Sourcery: Transparency for Stuff

Today I want to talk to you about stuff. Real stuff, products you buy and use every day in life. In specific I want to talk about where it comes from and how its made. Let's start this off with a little exercise.

Look around you and identify/pick up something in your proximity. In my case it's a wireless USB mouse. If it's name-brand, then you should be able to identify the company that made it with relative ease. My mouse is made by Logitech, a company whose products I've traditionally trusted but recently I've become frustrated with. Now for some this name-brand identification is enough, but let's dig deeper. If your object contains more than one piece, its fair to say that someone made those pieces. Its also fair to assume that in a complex object like a wireless mouse, that the pieces were made by different companies, using different materials and methods. In turn the materials used to make these components While we can know this truth, for most this is where our knowledge ends. for instance, I don't know who made the plastic casing on my mouse, or even what its made out of. Similarly, I don't know anything about the methods used to make these pieces, what company made them, and what their practices as a company might be. For all I know, I'm using a mouse that is powered by the soul of a baby seal clubbed over the head with a rod of plutonium. While I certainly hope this is hyperbole, it illustrates my point.

Shouldn't we, in a world of connected and relational data, be able to easily discover what is in our products so that we can buy intelligently? As a informed and concerned consumer I would love to be able to know with relative confidence where everything in my mouse has come from, whether it contains any materials I would rather avoid, and that it is indeed radioactive-baby-seal free. For granola-munching progressives like myself there are obvious advantages to this system, as it allows people to truly see what goes into the making of the things they buy should they chose to do so. However this kind of system would be of utility of anyone concerned about the how, what, and where. For example, informed parents would be far less likely to buy a product for their child if they knew that one of the manufacturers of one of the components used a chemical in the process that has been clinically proven to negatively impact children. Someone with hometown pride may favor a one product over another if they knew that it contained a component made in their home town. This concept may seem like a bit of a stretch, but its worth noting that there are several forward thinking companies which have already begun self-reporting on their sourcing. Their logic is that by being transparent to their customers, they not only hold themselves accountable as to what goes into their products, but also establish a trusted relationship with customers who will in turn reward them with brand loyalty.

So what would this system (lets call it Sourcery, because it makes me feel clever) look like Clearly this is too much data for one company to maintain with any semblence of agility or accuracy. A single edition of such a report would take years to compile and would be woefully out of date from its release date onward. So instead I look towards the Wikipedia model. Like Wikipedia, Sourcery has to be agile and decentralized, self-editing, and contain a tolerable level of credibility. Entries in Sourcery would be divided into three categories: products, companies, and materials. Product entries would list materials used in their manufacture, other sub-component products, and the company of manufacture. Company entries would contain a list of products produced by the company. Material entries would contain basic information on the properties of the material, and a description of how the material is created. Sourcery should be open enough that anyone willing to contribute knowledge can, but also allow companies the ability to officially confirm and validate the information contained on entries pertaining to their products. Herein lies the largest challenge of the entire system. Individuals should have the power to openly participate, as with Wikipedia, yet in order to be fair the system must allow companies to differentiate between factual information and baseless claims. At the same time, companies must be limited in their power to censure information, otherwise the system completely loses its utility. Perhaps the method lies in differentiating the powers of users and company representatives. Anyone can sign up to edit the articles, thus allowing the company the same level of access as everyone else. Companies can sign up for a official representative account, which adds the power to tag various information as officially confirmed or contested by the company. The official account would not allow for the deletion or wholesale censoring of information, but would instead simply allow for the company to add its position to any claims contained in regards to their products. Occasionally a company will want to protect its intellectual property, especially when it comes to proprietary materials. They should be allowed to do this, but with the understanding that the more which is withheld, the less inherent trust will be placed in the product.

Another critical component of Sourcery should be the linking of materials and companies to related data. For example, I should be able to see clinical studies related to a material, or a report on human rights conditions at a company. This is where the true usefulness of Sourcery would really reside. Without it, I may know a product contains a certain material, but without the context that this is something I may want to avoid the system loses its meaning. With it, it creates a climate where through disclosure, companies can be petitioned to make their products safer/better/more sustainable. Companies that would fight against such a change would inherently be at a disadvantage when competing against companies with less qualms about being honest with their customers. A feature that would certainly be a technical challenge to create, but a boon to utility would be ability to extract high level summaries. The feature would take a request for a summary on a product based on search parameters and dig through the web of sourcing data and return a summary based on anything matching the parameters. For example, lets say I want to know if anything in my mouse was made by a certain company, or made in a certain country. Doing this search by hand would take some time, but could be easily discovered by the feature and returned quickly. This functionality could lead to a whole new dimension of comparison shopping, allowing consumers to quickly get a summary on several similar products and make a decision accordingly.

Undoubtedly, if Sourcery was ever created, there would be those who would decry it as unfair, but to my mind it is the essence of fairness. When we buy a product, we are in essence voting for a supply chain and a method of production which we may or may not actually desire or approve of. By being informed, we can make better choices, what ever those choices may be.

Continue Reading