Avatars disunited

A semi-interesting e-mail pinged up this evening, thus:

Dear Avatars United Member,

In January of this year, Linden Lab purchased Avatars United for its underlying social technology and to integrate powerful social networking capabilities into the Second Life experience.

Today, we have made the difficult decision to discontinue Avatars United and will be taking down the site on September 29, 2010. Over the next week, we encourage you to save any pieces of content (such as pictures, friend’s names, etc.) that you want to keep. We will also soon update you on your AU Coin refund, if you have an account balance.

Over the two and a half years since launching Avatars United, we have welcomed avatars from many virtual worlds and MMOs to connect on our platform as the only social network catering to the needs of virtual identities. We are proud to have served those needs and honoured to have shared this journey with you all.

Going forward, pieces of the Avatars United technology will be integrated into the Second Life platform to support a richer, and more dynamic, community experience. Read more about these efforts on theSecond Life blog.

Thank you for being a member of the Avatars United community, and part of the Second Life family.
Sincerely,

The Avatars United/Second Life Team

Am I surprised? No. Even at the height of the Mark Kingdon “inspired” (if wrongly attributed) push that “SL = Facebook = SL”, the purchase of Avatars United seemed a little odd, even for Linden Lab, despite the latter suffering an identity crisis of its own at the time.

While there was some potential for Avatars United to enhance Second Life, the fact remains that it always was the square-peg-meets-round-hole situation for Linden Lab in terms of offering those of us already engaged in Second Life with anything truly beneficial. Similarly, as a marketing tool to draw others involved in on-line games into Second Life, its value was perhaps less than useful.

That LL had no idea as to what they should do with their new shiny once they had it was perhaps most clearly indicated by the massive flurry of Linden activity over on AU that dropped off faster than a rock disappearing over the cliff as the novelty of the new toy wore off to be replaced by the taxing question, “OK, so we’ve got it, not what do we actually do with it?” In fairness LL were not alone; the number of us who probably did the same is likely to be legion.

I’m actually surprised that AU has lasted this long; to be honest, I can’t even bid it a fond farewell.

The Green goes

Linden Lab have sounded the death knell for Emerald.

Well done, Phox (I wonder if that was an infantile play on “pox”). I sincerely hope a real lifetime ban follows for you, and Fractured Crystal. Not that I begrudge you anything, you understand, its just that – well, SL will be a lot more savoury without you.

For those panicking about their favourite Emerald features – fear not and look here. The future is bright. The future is winged….

Phoenix has now cleared self-certification (and do I ever wish some people would understand that term does not mean “approved by Linden Lab” or even “approved”!), and is now listed on the entirely voluntary TPV Directory.

So – onwards and forwards!

Addendum

Within 12 hours of appearing on the TPV Directory listing, Phoenix had achieved some 50,000 unique logins to Second Life. While a portion of these are going to be people running alts and potentially “bots”, the vast majority are going to have been unique users. As such, this is an extraordinary figure to hit in a so short a period. And without wishing to stir the Viewer 1.23.5 vs Viewer 2.x debated, one has to admit that it does show how loyal established users (who are the most likely to be aware of the entire Emerald debacle) remain to the older Viewer, despite LL’s best efforts at enticement, cajoling and denial.

Re-Emergence

Following all the shenanigans with Emerald, including the complete break in any credibility the Modular System’s group had, it is good to see that LordGregGreg Back has not given up entirely.

He’s now offering Emergence – a Viewer based solely on the last “safe” (as in not wee-wee’d all over by others in the Emerald camp) code for Emerald. I’ve downloaded it, and so far I’ve found it to be a more than acceptable replacement for Emerald, and one that – on the machine I’m currently using while away on vacation – is at least as fast as Emerald .1636,the last version of Emerald I ever installed.

I’ll probably take time to write-up more when I’m back home – there are some nice levels of transparency in things like the installer (at least to my uneducated eyes), and LGG has, I think, tweaked a couple of other functions.

For now, if you want to continued running SL in an Emerald form, but don’t want to have to face the trust issues – why not give LGG’s Emergence a try…?

Out with the globe, in with the storm

Note: Following this post being published, Esbee Linden made a formal blog on the subject on August 17th

In his address at SLCC 2010, Philip made mention of “standardising” the viewer platform. At the time I was curious as to what this might mean and asked a speculative question or two. Later, during SLCC 2010, Q Linden (whom I hope makes a full recovery from his stroke) and others gave more insight into what is going to be happening, and Oz Linden posted an announcement on the opensource dev list (thanks to Argent Stonecutter for the link).

Q’s opening of the SLCC presentation was somewhat enlightening, in that it confirmed many people’s views that Viewer 2.x proceeded along a development path that was simply far too rapid. In fact he candidly admits that it was developed and rolled out to meet a given schedule, rather than when it was “ready” (in November, for example, a meeting was held in which the “to do” list of outstanding work on the Viewer was cut down to a list of things that could be done in the remaining time frame prior to the release of the Viewer.

He also admits that Linden Lab erred when preparing the ground for Viewer 2, in that they didn’t create sufficient use cases to reflect how the Viewer is actually used in-world (that LL needed to “invent” user types in order to build the use cases in the first place also surprised me. After all, what are we out here, if not users?). The upshot of this is an admission that the overall capabilities of Viewer 2 are too narrowly focused.

This may sound like a “well, duh!” statement – but I think it fair to say that such an admission from the development team is somewhat refreshing. It’s not often the Lab or its employees own up to mistakes, and Q’s comments do add up to a strong admission of  having erred, and a hint that the lesson has been learned internally, “For marketing reasons we felt we wanted to keep it secret and we wanted to release it in a kind-of ‘ta-da!’…I think you won’t be seeing any more of that sort of behaviour from us any more! Yes, I hear the applause, thank you!”

Following this, Esbee went over the new methodology for Viewer development – Project Snowstorm, which has the core aim of rapid, effective deployment of new features and functionality. Essentially, and as hinted at by Philip, this will be achieved through meeting three goals:

  • Weekly, visible progress on the Viewer – which not so much is focused on weekly releases per se (although that is something Philip indicated he’d like to see), but more a case of making the development process more visible too all, including users being able to attend development meetings
  • Improving the user experience – hitting Philip’s requirements of Fast, Easy, Fun (a slogan I *still* loathe, but there you go)
  • Revitalising the open-source community

It is this last point that is the most interesting and – if carried through  – marks a radical change in Viewer development; one that would seem to have many potential benefits – and not just for Linden Lab.

The core of this new approach is that Viewer development will be somewhat streamlined, with LL themselves working on specific elements of the Viewer while leaving things open so that third-party developers can engage directly with the LL team and take on development of a given aspect or function within the Viewer, and developers with existing fixes or functions that could benefit the Viewer can deposit their work with the team for potential integration into the Viewer.

This effectively means the end of Snowglobe, the open source “version” of the Viewer code.  To quote Oz Linden, “The main Linden Viewer is now completely open source…the source code is available on a public repository…NOW!” What is more is that this repository is to be the central “integration repository” where all code from Linden Labs will go prior to integration into the Viewer.

Alongside of this is the re-licensing of the code from GPL to LGPL – which, if I am understanding things correctly, means that it will be both easier to incorporate the Viewer code into other Viewers (I assume those that can be used on OSGrids and the like) and – particularly from LL’s point of view – will make the licensing of the code for use in “closed” third-party Viewers significantly easier, potentially attracting other professional organisations towards developing their own Viewer systems without the “stigma” of being associated with open source code. Again, given LL’s stated desire to drive SL onto more mobile platforms – tools such as the iPhone, Droid, the iPad, etc. – this would seem to be a good move, as it will allow third-party organisations with the expertise LL lacks to develop the kind of functionality such tools will require if people are to use to them to access SL and use it for more than just chat and IM.

It’s not just developers who have the chance to be more directly engaged with Viewer development either. AS Esbee said, users will be able to get involved as well: iterative releases will be available bi-weekly or us to use and feed back upon, and even daily releases, or “project releases” covering specific features under development will be made available and user feedback encouraged.

From a non-technical perspective, this does seem to be a logical approach, and in some respects, it is a shame that, when they opened the Viewer code to the community, LL didn’t show foresight and put these measures in place then. Of course, the devil will be in the details – and there is much that will serve as either proof of the pudding or still needs to be addressed  / clarified. In listening to the presentation, a number of points occurred to me, some of which were echoed by others in the Q&A session.

One issue that springs to mind is who will, in the final analysis, determine what is “right” for integration into the Viewer, and will other agendas overrule the core goals – such as making SL Fast, Easy, Fun? “Linden knows best” has been very much a part of the Lab’s culture and has been seen time and again, particularly with the arbitrary closure of JIRAs or the turning of a deaf ear to valid user requests.  With the best will in the world, cultural behaviour is the hardest thing to fix in an organisation.

An extension of this concern comes down to user input actually being heard and acted upon. Q openly admitted at the start of the presentation that LL erred with Viewer 2 in not creating enough user cases on which to model the viewer. Now they seem to be swinging to the opposition end of the pendulum swing: seeking too much user input. There are – as Q and Esbee acknowledge – many diverse uses for SL, and as such diverse sets of users have diverse needs. Some are going to apposite in their aims, others opposite. How are filters going to be applied to stop all these calls simply swamping Snowstorm with the result that the individual internal dev teams beyond them simply cherry-pick or (again) turn a deaf ear?

So where does this leave the current crop of TPVs? Oz was pretty unequivocal on the matter: the Viewer 1 code base will not be developed any further by Linden Lab (Q also touched on the need to depreciate 1.23 in the future, simply due to security issues). Therefore, with the Viewer 2 code base becoming publicly accessible, the view seems to be that TPVs will be encouraged to continue – as well as give input to the new project – but will be expected to migrate to the Viewer 2 code base.  Certainly, there doesn’t seem a move on hand to proactively “shut down”  TPV development, but it is going to be interesting to see how this moves forward and who engages through Snowstorm as is intended, and who simply continue to work on their own Viewers utilising the now-available Viewer 2 code.

Overall, this move strikes me as positive. *IF* LL can carry through on this with the necessary internal cultural changes and if we all, developers and interested residents alike, engage with Snowstorm and LL constructively, positively and openly on our own part, then there is no reason why this project should give birth to something very worthwhile and which benefits us all.

SLCC: Pip’s vision – good, bad, possibly ugly?

Note: Updated Sunday 15th August, after re-watching the  recorded video stream without rl interruptions!

Philip Rosedale has just given a presentation at SLCC, and its is causing a very mixed reaction.  The following represents snippets – I missed portions of the stream due to RL issues, and will potentially expand once the whole thing is reposted somewhere for more relaxed viewing.

Highlights of the take were:

  • Script limits are still very much on the books, along with other methods of helping improve the overall in-world experience for users
  • General latency issues (failures in group chat; rough region crossings, teleport latency, etc.), are going to be improved substantially be the year-end
  • The start-up process (Viewer loading, downloading information from the servers, etc.) is going to be improved (speeded up) possibly by a factor of 2
  • The new user experience is going to be radically overhauled (as outlined in his meeting with BK)
  • General tasks are going to be made a lot easier – such as simply walking / sitting or even opening a box and wearing / using the content
  • Looking towards “standardising” the Viewer code base and also towards shorter, more iterative release cycles & automatic updates for the Viewer
  • A confirmation that Mesh *is* going to ship, although the process of introduction will be slowed down – which potentially a public beta by year-end
  • The ability for users to pick their first name and their last name and the ability to edit the display name (e.g. rather than using a group title)
  • The closure / merging of the teen grid with the Main grid.

These are all valid points, and addressing many of them will clearly be welcome to the vast majority of SL users. However, there are a couple there do require a closer examination.

The first of these is the commentary on the Teen grid. This has already caused considerable feedback on the official forum and elsewhere, and many have expressed surprise at the move. Why this should be, I’m not sure; Philip has made no secret of his desire to have the Teen and Main grids “merged” – even going so far as to state in a Metanomics broadcast back in January 2009 that he could see it happening “down the road”.  Back then, he said:

Generally, I think that the future of Second Life needs to be one where people of all ages can use Second Life together, and that’s the direction that we’re taking in our planning and our work. I think that the educational opportunities for Second Life are so great for all ages that we need to make it as available as we possibly can to people….But, if you look at the problems with having a teenage area, which is itself so isolated from the rest of the World, they’re substantial. There’s an inability for educators to easily interact with people in there because we’ve made it an exclusively teen only area. Parents can’t join their kids in Second Life so problems like that are ones that we think are pretty fundamental and need to be fixed. We need to stop creating isolated areas that are age specific and, instead, look at how we can make the overall experience appropriately safe and controlled for everybody. So that’s the general direction that we’re taking there.”

Furthermore, the changes are pretty much in keeping with the idea of “bringing down the walls” of Second Life, if not exactly in the manner Philip initially indicated when introducing the concept.

What will happen here is that ten grid will effectively close for anyone under 16, while 16 and 17 year-olds will be “moved” to the Main grid.

Philip hints at the reasons for doing this are educational and economic – both increasing the user-base and providing a means for younger users to enjoy the full capabilities of Second Life, while offering improved educational capabilities in line with removing the “isolation” elements. While these are not views necessarily shared by educators at present – as indicated by comments made during the Q&A session – Philip’s sincerity on the matter seems genuine; even if – and I have to be brutally honest – it carried the traditional Linden Lab edge of, “We hear you, but we’re doing it anyway, our way.”

On a personal level, I have mixed feelings about this; despite the more noble aim of  Philip’s statements around this move, it is not without risk.

Leaving aside the entire shift in legal onus and potential repercussions of an adult actually being unwittingly caught in flagrante delicto with a minor,  there are a number of other concerns that spring to mind.

Firstly, and despite his assertions that minors can be safely ring-fenced within Second Life through mechanisms such as Age Verification, the matter becomes one of perception more than fact. There are more than enough people outside of SL who are ever-eager to throw sticks, stones and whatever else they can find at SL / LL (step forward, Mark Kirk, salacious tabloid hacks, et al). Perceptions go a long way in the media. So even if the above-mentioned scenario never comes to pass, and no matter how robust age verification and ring fencing may appear to be (and are the verification systems LL employ really that robust?) – there is a strong risk here that innuendo, suspicion, inaccurate tales of under-age sex and other salacious reporting could do both LL and SL a lot of harm as things get mixed.

A second area of concern with the “move” of 16 and 17 year-olds into the main grid is what happens to the content they hold in their inventory. As Teen Grid users such as Ishy Wingtips have posted about in the forums, the Teen Grid, due to the lack of full-scale commerce, is rife with ripped content – including content from the Main grid. Is this content also to be transferred? Will filters be applied? In fairness, Philip does comment indirectly on this point and indicates it needs addressing – but the concern remains, particularly given LL’s track record of addressing “issues” in the past.

While not wishing to portray all young people as content rippers, there is a further concern here: ripping, as Ishy and others have indicated, appears to not only be endemic in the Teen Grid, but pretty much a modus operandi for many; it’s an accepted norm. Obviously, this is in part due to the “lack” of specific content on the Teen Grid. But, given it is something of an accepted norm, there is a risk that the arrival of younger players into the Main grid might lead to a renewed round of content ripping; that those entering the Main grid (assuming they are not already doing so “illegally”) will be the proverbial kids in a candy store.

Equally worrying, even if the above doesn’t happen, is the perception among content creators that it is – leading to another rise in the paranoia that surrounds the issue of content ripping which in turn leads to a rise in the use of the more edge-case “anti content theft” tools within Second Life. The net result being the Grid becomes somewhat more unpleasant for people of all ages as suspicion becomes the norm and people find themselves getting kicked from stores, etc., simply because their avatar looks like a teen.

In fairness, this latter point goes beyond content creators: while teen player will allegedly be ring-fenced to PG / G sims, one can still, sadly, still picture those *resembling* teens (i.e. with “below the SL average” height) being subjected to suspicion and questioning in clubs and elsewhere.

The other point of Philip’s presentation especially worthy of comment (given I skipped it following his in-world Roadshow last month) is the idea of making SL more fun by having new users being able to sign-up and effectively teleport directly to the things they want to experience. In this case he highlighted someone with an interest in live music being able to sign-up, click and link and go to a music venue.

Again, this is both a laudable aim and a potential minefield – as Philip acknowledged. It is also not something that is precisely new – Mark Kingdon alluded to the same idea back in 2009; the major difference being, he seemed to hint that the process would be far more siloed in effect than Philip is proposing.

The worry is of course, the process by which destinations / venues are selected for inclusion in this process; if it is not handled very carefully and with a lot of forethought, it could be seen as damaging to smaller venues / destinations / businesses if the larger (/louder) players are seen to be benefiting unilaterally as a result. Certainly, it runs the risk of further FICs forming / benefiting (or being perceived to have formed / benefited).

It was very good to hear Philip’s commentary on Mesh; with all that is going on around Second life in terms of emerging “competition” and rich, deep content, Mesh is something that SL will need if it is to maintain its position. But in that, it is pretty much a double-edged sword in terms of its impact  – it can simultaneously make Second Life a richer environment, have a beneficial impact on elements such as lag and latency, etc., and Philip points out – but it also runs the risk of revolutionising the content creation process so much  that many creators find themselves pushed to one side or out of business. Thus, to hear that the impact of Mesh is being considered carefully, and that the rush to introduce it has been somewhat slowed (public beta now slated for “around” year-end), is very welcome.

The comments around shorter, more iterative release cycles for both Viewer and server code were interesting. I’m not a technologist, but it has always seemed to me that making smaller, more contained changes to something like the server code, then building progressively on such changes is more logical than developing a release for a specific purpose – and then throwing as much as possible into it as well. Certainly, to my own way of thinking, the recent spate of server releases that have rolled out and back more frequently than Brighton sees a changing tide tends to support this.

It is going to be around the Viewer that there could well be further howling down the road. Philip raises a very valid point: one of the issues we all face in SL is that there are several flavours of Viewer out there, all handling things differently, and all operating from different code bases. If the Second Life experience is to be one that people can readily identify with one to another, there is a case to suggest things need to be unified in some way so that Viewers grow from a single code base.

The issues here are going to be precisely *what* constitutes this code base and how controls are going to be applied to it to ensure it remains manageable, controlled and verified as being “right” for the Grid; how Linden Lab continues to engage with TPV developers; and how much freedom they will have in terms of developing their own Viewers. Could this actually mean the end of all support for 1.23.5, internal and TPV? Again, while the sentiments appear logical, the potential for upset appears vast.

During the Q&A Prokofy Neva raised the issue of Search – something that is the cause of much angst within Second Life and which was absent from the presentation. Philip was quick to point out the reason for the latter is that he is still trying himself to understand all of the issues, before admitting that the matter is complicated – especially given various factors such as LL currently using two search tools, issues around establishing reliable measures that will help them more properly manipulate things like relevance in a search for the benefit of all. This again caused a mixed reaction on a personal level.

On the one hand, Philip’s openness and honesty was good to hear – the frank admission that there isn’t an answer to all the issues at present. While his comments around the number of people working on search compared to “six months or a year ago” were a tad disingenuous – while there were issues with search 6-12 months ago, they are nothing like the chaos people are experiencing now, so this measure of headcount isn’t entirely relevant in that respect – it was nevertheless good to hear that LL appreciate this is a major issue for residents and businesses alike and are trying to get things under control.

Overall, there was much that appears good in Philip’s presentation, and it is good to hear him couch matters in terms of issues that do massively hit people rather than in matters that could be said to be somewhat more “trivial”.  The assurances given around certain activities – providing they are followed-through – are equally good to hear. As to the more controversial elements, such as the teen issue, there are concerns that, on paper, make this appear to be potentially a “bad” move and may need to some ugliness. But that said, as we’ve seen time and time again, Second Life users and both resilient and adaptive – frequently in spite of LL’s efforts / activities.

Evans et al: file and counter-file

On July 10th, lawyers representing Linden Research and Philip Rosedale filed a Motion to Dismiss in the ongoing case filed on behalf of Carl Evans et al. Rather than deal with the specific claims made by the plaintiffs relating to the “sale” of virtual land, the Motion focuses on why the case should not be heard in the forum of the District Court of Eastern Pennsylvania. In doing so, the lay observer cannot help but wonder if Linden Research haven’t managed to play somewhat into Archinaco’s hands on the matter.

The Linden Research Motion to Dismiss hinges on four points:

  • Of the four named plantiffs, only one – Evans himself – has any connection to the District  in which the papers have been filed, and it is therefore an inappropriate venue
  • The plaintiffs have accused Linden Research of breaking a number of Californian state laws, therefore the more appropriate venue to hear the case is in California, wherein the Defendants reside
  • Evans has, on many, many, occasions not only fully accepted Linden Research’s Terms of Service (which includes matters of arbitrary and legal recourse), he has done so on many occasions using multiple accounts
  • The the plaintiffs have wrongly asserted prior point of law, vis Judge Robreno’s holdings in the matter of Bragg versus Linden Research.

Of these, the first claim has some merit in part: with two of the plaintiffs residing in Florida, why not file there? Obviously, there is a degree of  game play in force here: in 2007, during the Bragg vs. Linden Lab case, Robreno issued holdings that are broadly sympathetic towards the Plaintiffs. As such, Jason Archinaco, the Plaintiffs Counsel, has played towards getting the case heard in the same Court where Robreno resides – if not before Robreno himself.

Archinaco’s rebuttal of this point (which can be found here, as a ZIP file containing an amended original filing), would appear somewhat weak, suggesting that while Evans is *currently* the only plaintiff residing in the Court’s jurisdiction, discovery *may* reveal “hundreds or even thousands” of other Plaintiffs within the same District. However, this would appear to be the only weakness in his overall rebuttal.

LL’s argument for Dismissal on the basis of the Plaintiffs citing LL to have broken a number of Californian State laws would appear to be very shaky.  While the Motion reflects a similar – and successful – argument put forth by the Linden Research legal Counsel during the Bragg case in 2007, the situation today is somewhat different:

  • In the Bragg case, papers for the Plaintiff were initially filed at State level (West Chester, Penn). However, as they referenced Californian laws, LL  successfully argued that the case should be removed to Federal jurisdiction. The case was duly moved to the United States District Court for Eastern Pennsylvania – a Federal Court, where it came before Judge Eduardo Robreno.
  • In this case, the papers have been filed directly at Federal level, with the same Court Linden Research found acceptable when hearing the Bragg case in 2007. As such, there could be an argument to say that if the Court was good enough for them in 2007, it should be good enough for them now.

The last two reasons in LL’s Motion are altogether more boggling to the lay mind because both sides use almost the same arguments, with the logic reversed, as to why the case should / should not be dismissed.

LL point out, Evans et al not only signed up to the ToS Robreno originally cited as unconscionable, they signed-up to later versions of the ToS that were substantially revised after the Bragg episode, once their original accounts had been suspended. Therefore, it might be argued that a) the changes made to the ToS invalidate the Plaintiff’s reliance on the Bragg holdings b) the Plaintiffs knew full well what they were signing-up to in setting up new accounts to access Second Life.

However, as Jason Archinaco, on behalf of the Plaintiffs responds, while the ToS has changed over the years since Bragg, much of the language which Robreno found unconscionable at the time, remains very much in evidence in the ToS. He further implies that the ToS remains a Contract of Adhesion because one simply has no choice by to agree to its unilateral nature in order to use Second Life.

Things get even more confusing to the lay eye as both sides also use the fact that Carl Evans (who is individually singled-out in the LL team’s Motion in what appears to be – as Archinaco points out – nothing less than an attempt to undermine his personal credibility), has, over time, created no fewer than 72 accounts for use in Second Life. LL use this as evidence that Evans (and the others) willingly accepted the ToS over an extended period of time; Archinaco arguing that by their own admission, Linden Lab were forcing the Plaintiffs to adhere to a ToS previously found to be unconscionable and void…

Beyond this, both sides also produce impressive evidence relating to Forum Selection Clauses in contracts (the clause that gives LL the “right” to declare that those entering into dispute with LL must travel to California) which muddy the water even further.

At the end of the day, the filing of a Motion to Dismiss and the counter-filing of papers in rebuttal is generally an accepted step in legal cases. As such, there is little in the overall proceedings per se that is unusual here. What is of interest, however, is that in turning the matter away from the issues of virtual land ownership and towards the question of jurisprudence, Linden Lab have trod the same path as they did in Bragg. The difference here is that this is possibly that they have done precisely what Archinaco had hoped they would.

In their own Motion, the Lab’s legal team has brought the entire subject of the fairness or otherwise of the ToS and matters relating to Forum Selection Criteria, arbitration, and the unilateral nature of both of the latter, very much into sharper focus; this alone may yet come back and bite them rather rudely down the road.  Assuming things aren’t yet settled elsewhere, in another echo of Bragg.