Imprudence returns

Following the recent discussions on the TPVP which led to some needed rewording, Imprudence have announced they will continue to support Second Life.

While SL may no longer be the primary “market” for Imprudence (and Lord knows the OS environment needs a viewer with Imprudence’s strengths), that they have reversed their earlier, and somewhat irrational action is to be strongly commended. So to is their willingness to engage in the issue of clarifying concerns around the TPVP’s ill-considered wording.

Kudos, Imprudence!

I’m sorry, I’ve had a couple of blonde moments

Some may have noticed a couple of recent posts showing up, vanishing and then reappearing or going through multiple edits after publication. It’s not me changing my mind or anything….I’ve developed an idiotic habit of starting a long post, hitting the “save draft” button the first two or three times, and then hitting the “publish” button in error, while still actually drafting.

I have now given myself a stiff talking-to and swapped my in-world hair from blonde back to it’s usual auburn, so hopefully this won’t happen again!

TPV: a further re-wording

Following last week’s meeting between Joe (Miller) Linden and some third-party viewer devs, it appear that concerns have now been addressed.

At the heart of last week’s meeting were concerns over the wording of Clauses 7a and 7d, both of which related to liability, and which have now been re-worded, vis:

Clause 7a:

Original: You are responsible for all uses you make of Third-Party Viewers. If you are a Developer, you are responsible for all features, functionality, code, and content of Third-Party Viewers that you develop or distribute.

Update: You are responsible for all uses you make of Third-Party Viewers.

Clause 7d:

Original: You assume all risks, expenses, and defects of any Third-Party Viewers that you use, develop, or distribute. Linden Lab shall not be responsible or liable for any Third-Party Viewers.

Update: You assume all risks, expenses, and defects of any Third-Party Viewers that you use. Linden Lab shall not be responsible or liable for any Third-Party Viewers

Both re-wordings seem fair and concise and do not rob the TPVP of any teeth.

Elsewhere, LL has further reinforced their position that that are not in any way attempting to infringe upon the GPL (possibly for those who missed the various statements at the top of TPVP), by adding a new Clause 8f: Nothing in this Policy is intended to modify the terms of the GPL.

All of this should go a long way to reassuring TPV devs that Linden Lab isn’t out to “shut them down” as well as alleviating tensions. Doubtless, some still won’t be satisfied – but that is their choice rather than anything to do with LL trying to hound them out of the playground. The full TPVP can still be read here.

Moving towards script limits

Well, it took longer than originally planned, but server 1.38(.1) has rolled out onto the grid. With it comes new LSL extensions and (for those using Viewer 2.0 and its derivatives) the initial script management tools.

The latter take two forms: a breakdown of scripts running on a region (sim), and an Avatar’s personal script load; the former will only be visible to those “owning” land, or who are members of a group with land “ownership” (and then only on the land they “own”), while the latter should be available to anyone wherever they are in the grid.

Currently, both are limited in their meaning, because a) we don’t actually know what the overall limits are going to be for either in-world scripts or for the “pool” of resources to be allocated per server / sim to avatars; and b) the tools don’t accurately reflect Mono script usage – Mono scripts can utilise any amount of memory up to 64Kb (with the average apparently being around 9Kb), but only the 64Kb reserved for a Mono script (whether or not it is using less) is reported. Thus, Mono scripts currently appear to be hogging resources, when this may not be the case.

A further problem with the current tools is that, when looking at in-world script usage, they are simply too broad-based. Details can only be displayed for the entire region rather than for individual parcels. Hopefully, this will become more granular in the future, but for now it does possibly invite the kind of knee-jerk reaction the promotion of Avatar Rendering Costs created (albeit on a far smaller scale, given the limited access to script information), with people with access to the information screaming blue murder at the sim owner because a) the sim is laggy, and b) their neighbour is running XX “gigantic” scripts, and so must be responsible for the lag.

Access to the in-world script list is obtained by going to ABOUT LAND and then clicking on the SCRIPT INFO button in the GENERAL tab of the About Land pop-up.

Script Info - Land (note avatar names purposefully hidden to preserve individuals' privacy)

The list can be sorted in a number of ways – by script size or via avatars names (alphabetically ordered by first name, etc).

There are three buttons on the list – REFRESH – self-explanatory; HIGHLIGHT – which allows an object to be “red beamed”  after selecting it on the list, thus allowing its physical location to be confirmed) and RETURN – which allows an object highlighted in the list to be returned to the named owner’s inventory. In the case of this last item, I sincerely hope the functionality is restricted to SIM owners / Estate Managers, for obvious reasons.

At the top of the list is a small information area entitled “Parcel Script Memory” – possibly indicative that the display will be further refined to parcel level, rather than listing the contents of an entire sim. This section also gives a practical indication that script limits have not been set, as it will report that the sim is using XXXXXXXKb out of 0Kb.

For those who are not land “owners”, their personal script info can still be accessed through one of two ways: either via the SCRIPT INFO button in the GENERAL tab of ABOUT LAND, or via the SCRIPT INFO button that is displayed in the APPEARANCE editing window. Clicking on the MY AVATAR tab at the top of the script listing pop-up will then display the relevant information in both cases.

Avatar Script Info Display

At the moment, both displays are purely informational, and will have no real meaning until final limits for scripts are set by Linden Lab.  But the process has now started, and it is going to be interesting to see how things develop and whether LL stick to their promise of being open and communicative as further elements of this new policy are rolled out.

Echoes of Bragg: Evans et al vs. Linden Lab

Tateru Nino reports over at Massively that Linden Lab is facing a couple of new lawsuits.

The latest, Evans et al vs. Linden Lab, has some echoes of the infamous Bragg vs. Linden Lab case. As with Bragg, Evans and his fellow plaintiffs are proceeding against Linden Lab on the basis of having their accounts terminated and their assets (land, content, Linden dollars) seized. Further, they are being represented by Jason Archinaco, who represented Bragg in 2007. And in a final twist, the case is set to be heard by Judge Eduardo Robreno, who heard the Bragg case.

Evans et al have commenced a class action against Linden Lab and have put up their own website. The crux of the filing calls into issue statements made by Linden Lab representatives – Philip Rosedale being primarily named – relating to the concept of land  / goods ownership which are at odds with core clauses of the current Terms of Service, which effectively deny users’ ownership of anything but IP rights. The action also relates to the manner in which the ToS has been altered over the years – up to an including the forthcoming new ToS due to come into force on the 30th April, alleging that it is akin to altering users’ title without consideration of the consumer’s knowledge or consent.

As Tateru notes, Archinaco is well versed in the minutiae of legal actions against LL, having trod the road very thoroughly in 2007; therefore it is unsurprising that parts of this action strongly echo claims made during that case.  At the time, while there was a confidential settlement, it was viewed that Robreno was broadly sympathetic to Bragg’s position and ironically, it was his holdings on the matter that lead to LL re-wording the ToS (and thus possibly contributing to the current situation) – so having both involved in the Evans et al case makes it an eyebrow-raiser.

During the Bragg case, Robreno agreed with the plantiff’s position that that ToS was a “contract of adhesion”. He further noted that the mandatory arbitration process within the ToS was also unbalanced and unilaterally favoured Linden Lab. As such, many pointed to the Bragg case as being a seminal case in matters relating to virtual worlds and virtual property rights. However, Robreno added a significant caveat to his holding on the case: that the ToS could be regarded as a “contract of adhesion” inasmuch as Second Life was effectively a monopoly service: in 2007, there were no competitors to which users of Second Life could turn.

It could be argued, with some OS Grids starting to offer their own currency systems and having offered land “purchase” schemes for some while, together with the establishment of OpenLifeGrid and the the growth of Blue Mars, et al, that the monopoly situation no longer applies regardless of the technical state of such environments.

That said, the papers filed on behalf of the plantiffs present a curate’s egg of a case.

On the one hand, Archinaco clearly outlines the dichotomy between the ToS and the manner in which Second Life was repeatedly promoted (particularly by Philip Rosedale himself) through prejudicial terms / concepts such as “buying land” and “ownership”. While linden Lab has clumsily retreated from the idea of virtual ownership in the years following the Bragg case – and have finally openly moved away from the concept within the forthcoming ToS through the redefinition of both virtual land and the Linden dollar as effectively being licenses. I use the term “clumsily” quite deliberately; while terms like “buy” and “own” have been expunged from the new ToS, Linden Lab are still using them elsewhere:

As such, the action is being filed under (among others) the Californian False Advertising Act and the Violation of Legal Remedies Act, and Archinaco does build a pretty solid case to be answered in the former, although he seems to rely heavily on Bragg vs Linden Lab in the latter – and as noted, times have moved on since 2007. While I acknowledge I’m not a lawyer, the inclusion of the Californian Unfair Competition Law might not be as effective as it might have been had this action followed directly on the heels of the Bragg case (at least for Evans’ fellow plaintiffs).

Elsewhere, the papers make some rather contentious claims, possibly to support the charge of fraud and/or fraud in the inducement. Notably, the papers contest that Second Life as a whole has been “open sourced” so that (quote): any individual can simply hook up their own server to the Linden “platform” and create their own land, which has resulted in the long-term devaluation of all the land purchased by consumers to zero. This is hardly an accurate statement: as a platform, Second Life remains closed, only allowing third-party clients to connect to it – not privately owned servers. As such, this is a shaky foundation upon which to build a case for Linden Lab fraudulently manipulating the land market for the benefit of their shareholders.

The papers also seek to make a case that buying virtual land is the equivalent to “investing” in LL as a company, and that moves were made to devalue land in order to maximise shareholder profits at the expense of said “investors”. This would again appear to be somewhat contentious: by no stretch of the imagination can the “purchase” of virtual land been seen as an open “investment” in Linden Lab as a company; this is akin to claiming that by using server space to host a website, you are “investing” in the ISP providing the server space with an eye to sharing their profits….

But these wider accusations towards Linden Lab aside, the central thrust of the lawsuit would seem to carry significant weight, and the well-documented references to statements from the likes of Philip Rosedale and others would seem to put Linden Lab in a corner – one which, as Tateru notes, may not leave them in an adequate position to settle.

That said, one cannot help but wonder if settlement might not be on the minds of the plaintiffs. That some of them have waited some 4 years to file against LL, having had their accounts terminated in 2006, and have now done so on the eve of what is a major re-alignment of policy within the ToS does leave a question mark hovering over their motives.

It is going to be interesting to see how this unfolds.

TPV: brown bag and changes?

On the 13th, Joe (Miller) Linden held the first of his brown bag meetings with TPV developers to discuss the Third Party Viewer Policy. The various transcripts and audio recordings make interesting (if headache inducing) reading / listening.

While it was unfortunate that LL decreed the meeting would be in Voice – thereby potentially limiting input and participation (specifics raised in chat seemed to be somewhat ignored) – the meeting wasn’t as fractious as might have been the case, given the amount of ire the TPVP has created. Certainly, despite the efforts of some to try an disrupt proceedings by crashing sims, etc., progress seemed to be made in the key areas of contention – notably Section 7 of the policy.

This section has caused contention largely due to the wording. If taken 100% literally, it would appear to be shifting all responsibility for TPV code onto the shoulders of TPV developers. While this was not LL’s intent – as I’ve said elsewhere, they are not malicious – the wording did leave a lot to be desired. And while some may disagree, part of the problem does stem from the fact Section 7 mixes the development of a viewer with its use by others. Beyond this, there is the problem that a literal reading of some of the clauses – 7a, for example, appears to give the impression TPVs take responsibility for LL’s code when LL absolve themselves of all blame.

Whether one agrees with this standpoint or not (I personally don’t – and I sincerely doubt the law would interpret the language in the manner some TPV devs fear) – the the wording does cause angst and could be reworded without compromising the TPVP rather suggests that there would be no damage done were minor adjustments to be made to the phrasing of the clause – and this was indeed suggested.

A similar discussion was had around clause 7d, where again, it was apparent that much angst could be resolved by simply striking the first sentence in the clause; what was more, doing so could clarify LL’s position on matters of liability.

Elsewhere, people were more receptive to the fact that the TPVP is concerned with connecting to a service, and therefore stands aside from GPL requirements – something that seemed clear to many “outside” observers on the matter, including myself. Most interestingly, Lance Corrimal indicated that the Free Software Foundation’d licensing expert did not find the TPV to be in conflict with the GPL. That it would be is something I’ve had a hard time getting my head around; again, LL are not stupid. They did blunder with the original draft of the TPV – but they also stated the re-draft would be passed in front of experts in licensing and the GPL. I doubt that they  would subsequently go ahead and release the re-draft without following through on their intent to do so; ergo, it was hard to see how the experts they potentially used to review the TPVP got it so badly “wrong”, while those (with the greatest of respect) not versed in licensing and law were so adamant it is “wrong”.

What remains to be seen for the moment is how much fruit this first discussion bears between now and the next (set, I believe, for next week). When one puts aside all the angst and subjectivity surrounding clauses 7a and 7d, both could be more clearly worded without, as I’ve stated, impinging on the TPVP’s overall intent. As such, I would hope LL will take the suggested re-wording of both to heart and update the clauses.

It would still be nice to see the TPVP more clearly focused on the development of such viewers, with anything relating to the use of the same moved to the ToS. This would not only make the TPVP more focused for both LL and TPV developers – it would ensure the limitations on the use of such viewers are placed where they have a chance of being read by the majority.