Malicious, lost, or out-of-time?

I‘m going to start this post with a quick statement: What follows here has been cogitating for a while now. It started as a number of posts that never made it beyond the draft stage (including one from way back in 2008, written in response to Mitch Kapor’s SL5B keynote address), combined with such factors as LL’s TPV Policy, the new ToS, Viewer 2.0 – and the (sometimes irrational) responses these have garnered among users of late. However, what with me being somewhat slow to organise thoughts, getting sidetracked by other matters and the arrival of Easter and family, it has taken me a little while to try and pull everything into a (hopefully) cohesive post. In doing so, I’ve pre-empted some of what I’m about to say, and others have come to the same conclusions, potentially with greater grace than I. I’ve also been pointed to other blogs wherein lie comments that echo – again, possibly more succinctly – my own thoughts (a fact that has also weighed on my mind as to whether I should order my ramblings into something comprehensible, or simply move on to other subjects). As such, this post is not an attempt to jump on the bandwagon, or lay claim to anyone else’s thinking; rather it is more an exercise in catharsis: getting everything down and out, right or wrong, so I can at least clear my head somewhat.

Why is it that Linden Lab, throughout the history of Second Life, appear to have such a disconnect between their management team and their users? How come, time after time after time, they consistently piss off so many, so quickly with (generally) so few words (or sometimes even lack of words)?

Over the last few years, we’ve seen a number of events that have upset users to a degree that – I think it fair to say – has actually surprised senior management at Battery Street, notably the OpenSpace / Homestead sim debacle and the Zindra upheaval. More recently, we’ve had the apparent push to align Second Life with Facebook and its ilk and reduce it to a simplistic, 3D social networking site (aka Viewer 2.0) causing consternation; and, bringing us right up to date, we’ve had the arrival of the Third Party Viewer (TPV) Policy and the sudden introduction of a new, and potentially far-reaching Terms of Service.

All of these have lead to predominantly negative reactions from users that have ranged from angry official blog postings right the way through to protests, banner waving, “flag burning” and even the departure of segments of the community (such as Elf Clan). Yet, each and every time, the management has sailed on; apparently unaware of the chaos they are leaving in their wake, only to blunder into the next crisis.

Or perhaps they are aware, and simply do not care. This is the most commonly-held view among those who find LL’s recent decisions so upsetting: that the Linden Lab management team simply don’t care: they are malicious grey suits only interested in the bottom line of the balance sheet.

While I’ve criticised LL a lot in my time, I do not believe that the likes of Mark Kingdon are driven by pure maliciousness. Those who have been around SL long enough know that heavy-handed attitudes and policies pre-date his arrival by a long margin – so if maliciousness is involved, he didn’t start it. As I’ve commented previously, the whole CopyBot issue, and LL’s complicity in its spread occurred a long time before Kingdon arrived on-scene. If you want to go back further than that, then there is the so-called tax rebellion of 2003.

I don’t buy the “simply malicious” argument because, at the end of the day, Linden Lab isn’t likely to profit or grow from it in a sustainable manner. Grabbing the profits today and saying to hell with the customer and to hell with tomorrow is an exceptionally myopic and ultimately stupid way to run a company. In the case of Linden Lab, it would probably have lead to the demise of the company a goodly while ago.

Similarly, the New User Experience makes no sense.  Viewer 2.0 is central to this – and yet, Viewer 2.0 (as many have pointed out over the last several weeks) is not so much flawed as completely broken – hardly an encouraging way to entice new users into SL, retain them and encourage them to part with their money in-world and grow the economy….

Maliciousness makes sense if the company profits. We may not like it, we may howl against it – but if we all see practical benefits from it: a growth in user numbers, more people spending time and money in-world, the economy expanding, etc., – then I think the majority of us will find the maliciousness a bedfellow we can tolerate because a) Second Life survives and we continue to participate in it; b) those in business within SL stand to retain viable income streams, and thus remain in-world and help encourage the rest of us to stay.

But again, this doesn’t seem to be the case with Linden Lab. If we look at the OpenSpace / Homestead fiasco for example – did it lead to an obvious growth within Second Life? Did it make the platform more sustainable? No. When all is said and done, when all the angst and drama around the change is put to one side – the overall status quo of the platform remained unchanged from a fiscal perspective. The economy neither expanded radically, nor contracted. LL themselves may have enjoyed a small upward blip in cash inflow as a result – but longer-term, the move didn’t really help them.

Zindra and the Adult Policy are also held up as an example of the maliciousness of the Lab’s management – that they are “anti sex”, “anti BDSM” and that the Lab wanted both to “go under” by driving people into leaving SL. But again, I simply don’t buy this. Certainly, both the policy and the Zindra move were ill-considered, poorly-executed and almost certainly could have been handled a lot more pragmatically – but none of this happened simply because senior management “don’t care”. Furthermore, simply driving out a segment of the community makes no sense – not when said segment is actually responsible for generating a large amount of in-world spending, which in turn generates an inward flow of cash to the economy as people convert real money into Linden Dollars. Thus, if “driving out” a very profitable segment of the community was the aim, then the Linden Lab management aren’t only malicious, they’re stupid.

So is incompetence within the management hierarchy responsible? A management team that seems to be constantly chasing its tail, or which leaves all its policy making to the lawyers (as seems to be the case with the new ToS and TPVP) would certainly appear to be incompetent. But again, it is hard to reconcile this with the business profiles of those at the top of the management tree. Take Mark Kingdon as an example, and his history prior to joining Linden Research Inc.

He joined Organic in 2001, after the company had been forced to down-size following the Dot.com bubble bursting in 2000, which also forced the company to re-privatise. Then, and contrary to sniping posts in the official forums, he steered the company through seven years of successful growth, which included the launch of an entirely new arm of the business. Before that, he was a senior executive at PWC, closely involved with that organisation’s merger with Lybrand. So he’s hardly a slouch or an idiot when it comes to managing a business.

Thus, the idea of rank incompetence doesn’t entirely fit, either. Yes, the management team have got it wrong. Yes they have at times let lawyers run amok in the playpen (most recently with the poor wording of the TPV Policy) – but people in business do make mistakes; this doesn’t automatically make them totally incompetent.

What is more, Kingdon has demonstrated, through the first of his in-world meetings with residents that he is potentially far more aware of the potential for the technology than his spin-laden blog posts, etc., would imply. As his honest, unscripted answers to questions at this meeting indicated, he does hold a certain vision and hope that goes beyond simplistic bottom-line costs and profits.

Indeed, the fact that Kingdon is taking the time to come in-world and spend time with residents, face their concerns and anger head-on, is another reason to thrown the “malicious” argument out the window. If he were so minded as to simply not care about what we think and feel – if he was simply looking at “new users” to sustain LL, he simply wouldn’t bother participating in such open engagement with us.

So what is it? If it is not incompetence or maliciousness, what is it about LL that causes them to repeatedly underestimate / misinterpret the liable outcome of their broader actions?

For the most part, my own feeling is that when all is said and done, it is this: Linden Lab’s management team have no intuitive understanding of, or identification with, their users. To use Grace McDunnough’s wonderfully-chosen term (and curse her for beating me to the punch and posting first on this subject – as well as for putting it so beautifully succinctly! *smiles*), they simply don’t grok us.

There is a fundamental disconnect between what they see as the marvellous potential of the environment presented by the technology behind Second Life and their ability to connect with the equally marvellous potential of a passionate and engaged user community. And, I believe, it is this failure, more than anything else that has damaged both their ability to approach use, and our ability to see them in a credible light.

This is partially understandable: Second Life is unlike any other platform or business model, having the unique ability to bring together so many facets of life into a single environment. There is no single quantifiable reason as to why we’re here: there is no treasure to hunt, or enemy to kill or war to wage or objective to reach. There is no single demographic within SL that fits traditional marketing and promotional tools that Kingdon and his senior management are going to be familiar with.

What is more, the reasons we stay involved in Second Life are not always constant. We may initially come here because it offers a “gaming” or “role-play” or “lifestyle” outlet – only to find weeks or months down the road, that we’re involved in many other things: scripting, building, “business”, be it simply working in a club or store on behalf of someone else right the way up to full content creation and re-sell. But through it all there is no defined objective.

Thus, rather than being malicious or incompetent, I tend to feel that those running Linden Lab simply do not know how to approach us, deal with us and engage with us. In a word, we’re a pretty overwhelming force, one quite outside the keen of most corporate executives….

….but that is no excuse for sitting in isolation from us, as the current management team have tended to do to far, far greater extent to their predecessors. And even while I do applaud efforts by Mark Kingdon to host in-world meetings and address concerns head-on, the fact remains that the frequency of these meetings leaves much to be desired. The first was held in February, but it doesn’t look like any follow-up will be held for several months. If Kingdon really wants to get to grips with matters, then frankly, he should be putting an hour aside once a month to sit with people.

A lack of involvement, a lack of understanding has lead to those leading LL to regard SL purely in terms of numbers: if the metrics are good, the platform must be good and therefore the users must be happy. But metrics are only one side of the equation. If there is a fundamental lack of understanding as to who we are, and how we are feeling; if there is an inability to link our upset over heavy-handed policy implementation with our love of Second Life  – then LL will continue down the road of losing its most valuable commodity.

In this regard, it doesn’t matter how they change the New User Experience. Nor do the number of man hours put into developing a new Viewer account for much: because at the end of the day, if the management still don’t understand us, if they still see us as standing apart from their platform, as “just users” – then whatever they put out on display to entice people into the store is ultimately going to fail.

In 2006, Facebook launched an applet that enables users to track changes made to, and activity on, their Friend’s pages. The tool caused outrage in the community, with tens of thousands of users viewing the tool as an invasion of privacy and protesting about it. Two days after the tool was launched, Facebook issued a statement that they would put the tool under individuals’ control so they could determine what others could see. At the time, one marketer commented:

The members prevailed. How? And why? Members used this powerful medium to connect, assemble, and make their voice heard. Fortunately, Facebook listened and responded.

The takeaways for marketers:

  • Listen carefully. If you target connected customers, have a mechanism in place to collect feedback before taking major actions (product changes, new product launches, etc.). Don’t act in a vacuum. Use social media to engage customers and solicit their feedback. Then, make their input an important part of your strategy.
  • Be ready to act. Social networks and many Web 2.0 tools make it very easy for people to assemble around a cause. Major brands should have a rapid action plan in place to identify and address these situations before they get out of hand. In the old world, this was called public relations or crisis communications. In a new, networked world, it’s good community relations.
  • Respect the community. What I wrote in an earlier column about five best practices for marketers who venture into social networking still applies: “Respect the Community. It’s a club and you don’t really belong. Most social networks aren’t about advertising or commerce per se… As an advertiser you’re a guest in the club. Understand the environment and respect the unwritten rules: don’t intrude on conversations or connections in a way that irritates members; don’t divert users from the network to other sites; and don’t disguise yourself in a dishonest way.”

If this advice doesn’t resonate with you, close your eyes and imagine this scenario:

You’ve just spent six months developing a new campaign for a major new product launch that’s a line extension in a very popular, somewhat dated product line. You and your management team have high hopes for this product. You need to invigorate the product line and generate a big bump in sales. You’ve carefully researched the product and launch strategy. The focus group results indicate you’d add new customers without alienating your core franchise. You launch.

Within a week of launch, 126 groups have formed, all calling for a boycott because you spoiled the product with this line extension. The revolt started in the U.S. and is now moving to Europe. Angry customers are filling your inbox with hate mail. Your boss calls and asks what the heck’s going on, how significant the damage could be, and what you’re doing to respond. You tell him you’re going to change the campaign messaging and heavy up on PR. Then, you realize that strategy won’t fly. These people want answers and action — now. You have hours. Not weeks.

Sound advice to any company: listen, engage, respect the community and build community relations. The author has the right idea.

So what, exactly, has gone wrong, Mr. Kingdon? Why is it the advice you gave to others just four short years ago has been largely absent in the management philosophy at Linden Lab? Why are you only now making some effort to more properly engage with us?

Think of how different the experience would have been if Linden Lab had approached things like the Adult Policy and even the new ToS through a process of open engagement with the community, rather than playing word games and leaving it all in the hands of the legal staff. Yes, people are frightened by change – but we can deal with it if we’re given the opportunity to participate in the process and understand the underpinning reasons why change is needed. None of us are fools – and many of us understand the environment at least as well as Linden Lab management. Engagement with the community, using – as Grace McDunnough suggests – the process of appreciative inquiry rather than autocratic mandate, could have lead to the Adult Policy and the TPVP being far less traumatic affairs than they have so far been – for both the community and Linden Lab.

The sad thing is that, despite pleas for LL to raise their grok factor, it may now be too late.

Mitch Kapor has made little secret of his desire to see the “pioneers” (aka you and I) of Second Life to get out of the way and let the “pragmatists” (e.g. big business) in. He’s been wanting SL to “do” something for a goodly while. In part, this has likely fuelled some of the errors LL’s senior management have made in pushing through policies with absolutely no finesse whatsoever. He’s also likely fuelled the drive towards the SLE product and the development of the business side of SL. Doesn’t take a genius to work that out.

Even so, despite all the pushing and pulling, the hype and hoped-for, LL itself is still something of a lame duck as far as venture capital companies are concerned. It’s sitting in that 30% zone of VC-funded start-ups that tend to limp along, making just enough to stay in business, but not enough to be a raging success. Sure, the SL economy is continuing to show modest growth and LL continues to make a modest profit from it as a result. But it is not the stunning success all the hype surrounding it these last 8+ years has suggested it could or should be.

One cannot help but wonder if Kapor et al blame the very people they’ve failed to understand – you and I – for the failure of SL to “achieve”. We’re the “pesky kids”, constantly getting in the way. If this is the case, it could explain why we’ve seen the rush to bump Viewer 2 from beta to full release, despite it being badly broken, and why we’ve seen the almost stealthy (and certainly unexpected) shunt of an entirely new Terms of Service & its associated policies.

Some has decided that it is time to break up SL to some degree. I’ve already touched upon this in an earlier post – that the operation to run the Grid might be licensed-off, allowing LL to focus on what might be regarded as the “core” business that is likely to generate a more predictable income stream.

The business enterprise side of Linden Lab is still fledgling – also it is being realigned as a set of three services – but a lot of hopes are pinned on it. Could it be that someone right at the top of the Linden Hierarchy has set a deadline for the management team, something along the lines of “achieve X by the end of Y, or get ready to license-off the platform. Let some other poor sod deal with the user issue…”?

It wouldn’t be easy to go this route, certainly; but it also wouldn’t be impossible. Yes, it would cause some upheaval and no doubt wailing and rending of garments – but again, isn’t that the response (as far as the upper echelons of LL are concerned) to every decision made?

As I’ve previously said, putting all the paperwork in order would be a first step in this process. As of the 30th April, the lines of responsibility, the type of services being supplied, are clearly spelt out (well, as clearly as legalese allows), making it much easier for anyone taking up a licence to run the grid to see where their liabilities start and finish, and how external liabilities (such as third-party viewers connecting to the grid) have been “minimised”.

Of course, exactly how much time the management team have been given to “get things sorted” and realise both the increased influx of users, etc., they’ve been promising as a result of the new viewer, the new ad campaigns and the cosying-up to the Facebook community and the anticipated growth within the SL economy is totally open to question. And that’s assuming this speculation is even right.

But it does potentially mean that it no longer matters whether or not senior figures in Linden Lab empathise with us. Does this in turn make them malicious, as postulated at the start of this post? Not at all; nor does it make them incompetent. Careless, then? Absolutely.

Putting the paperwork in order?

I’ve been going over the ToS in more detail over the past few days (it was either that, or sit with older family members through the likes of Emmerdale Farm, East Enders, Jack Frost and re-runs of Hercules Parrot again).

What has struck me once again is the manner in which everything is being handled by Linden Lab. We have Viewer 2.0 being pushed into prime time before it is really ready. We have high-level Lindens (Amanda, T, etc.), suddenly spending a lot more time in the flogs addressing user concerns; we have the new Third Party Viewer policy coming into effect from the 30th April. We also have the new ToS coming into full effect from the 30th (although we’re all being asked to agree to it now), together with all of the policies associated with it having undergone a top-to-toe re-write.

So much so, that one has to ask why? Why all of this now? Why the paradigm shift evident in the ToS that moves Second Life from a platform to a service? Why the rush to get everything out by April 30th? Why not a phased approach that would, for example, introduce the TPV, filter in other policy updates and culminate in a new ToS and which would allow the more glaring issues with Viewer 2.0 (Search, for example), to be reasonably fixed?

Part of the reason I started chasing Amanda Linden is that I have a deep-down feeling that LL are paving the way for Second Life  – as a service – to be sold?

Many moons ago, “the Grid” (as in the underlying technology of Second Life) was ostensibly hived-off into a “separate” business element. More recently, the Grid itself has been split into three distinct “microsites” which appear to be leveraging the technology in terms of service provisioning to businesses.

Could LL now be seeking the opportunity of divesting themselves of the actual running of Second Life itself?

The reason this thought keeps popping into my head is section 13.2 of the ToS:

13.2 You may not assign your Account; we may assign this Agreement.

You may not assign this Agreement or your Account without the prior written consent of Linden Lab. You may not transfer or sublicense any licenses granted by Linden Lab in this Agreement without the prior written consent of Linden Lab, except solely to the extent this Agreement permits transfer of the Linden Dollar Licenses and Virtual Land Licenses. Linden Lab may assign this Agreement, in whole or in part, and all related rights, licenses, benefits and obligations, without restriction, including the right to sublicense any rights and licenses under this Agreement.

In other words, you cannot “pass” (or sell or whatever) your SL account to anyone else, but Linden Lab, can at any time, pass on or sell this agreement (the ToS) at any time, without any prior warning to users.

When viewed in this light, the new packaging of the ToS and all associated policies appears to make sense: LL are neatly drawing a line over all that went on prior to 30th April 2010, effectively (on paper) freeing anyone coming in to take over SL from any prior obligations and/or issues.

Other elements within the ToS also fall into place when viewed this way – Linden dollars becoming a license system for example; not only does this potentially clarify tax issues around them (it is now spelled out that Linden dollars have no fiscal value until cashed out) – it also further ring fences any potential liabilities surrounding Linden dollar accounts on the part of the “service manager” (be it LL or anyone else).

A sale of SL as a service could be beneficial to LL: they would lose the income from land, etc., certainly: but they would retain the IP on the technology and its development, and they would conceivably generate income through one (or more?) licensing deals with those wishing to run Second Life environment(s). It would be hard to work through all the details to make it work – but potentially not impossible. If nothing else, it’s interesting to speculate on the idea.

Malicious Viewer detection systems

There has been what can only be described as an ongoing war of words enacted over on the official flogs relating to the use of “Viewer detection systems”. This fight has been focused on the Gemini CDS (Copybot Detection System) and it has people hotly divided for the most part: those who are “pro” the system, those who are “anti”, with a lot of name-calling and aspersion-casting going on between the two.

Essentially, Gemini CDS offers people protection from “copybotting Viewers” by detecting them when an avatar using such a Viewer tp’s into range. It can then either alert the land owner to the individual’s presence or it can boot / ban them – and add their details to a blacklist shared among all versions of the system that have been deployed in-world (i.e. there is a back-end database external to SL supporting the system). Further, the ban remains in place, even if the alleged violator subsequently tries to access a protected sim / area using a “legal” Viewer. To support the network ban list, purchasers of the system pay L$700 a month over and above the initial purchase price of the system.

The system apparently works by using the media streaming capability built-in to the Viewer to identify known “copybot” Viewers and thus take action against them (assuming, I gather, the user has media streaming enabled on the Viewer). There has also been a lot of hype surrounding the ability of this system to somehow automatically ban alts of those found to be using “copybotting” Viewers at the same time as the initial ban is handed out – leading to (unfounded) claims that the tool illegally scans the local computer.

Leaving aside these wilder (and pretty much unfounded) claims of data scraping, Gemini CDS would appear to offer a degree of protection against content ripping. However, having toiled through the seemingly endless flog threads on the subject as well as bouncing around other SL-related forums (where the debates surrounding Gemini CDS are as prevalent), I have serious concerns as to the effectiveness of the system, and something of a niggle relating to its validity.

For a start, the system appears to have been largely deployed by store owners, who give it the loudest praise in the flog. BUT – the vast majority of stores use vendor systems (with some notable exceptions in the furniture and housing markets) – and goods contained in vendors cannot be ripped. Ergo, aside from those who are utterly naive when it comes to content ripping, it is highly unlikely “serious” rippers are going to be plonking themselves down in the middle of stores.

Even the effectiveness of the system cannot be examined; while store keepers may point to the “fact” that Gemini CDS has ejected X people from their store / sim in any given week – this does not automatically equate to said individuals being genuine content rippers nor does it mean content ripping is in any way being deterred (again, because it is unlikely serial content ripping is taking place in stores).

Then there is the question as to exactly how endemic content ripping really is. The flog shows the level of fear / paranoia circulating on the subject, with ugly fighting erupting among content creators themselves. Within the flogs themselves, some store owners openly admit to ejecting people who stand around in their stores for more than a couple of minutes without moving, because they “know” these people are ripping their content (again, unless the content is on open display – such as being modelled – it’s hard to see how this can be the case).

As such, it is hard to accurately assess the spread of content ripping through the use of malicious Viewers simply because of all the FUD that surrounds them; and this being the case, it is fair to ask whether tools such as Gemini CDS actually feed into this FUD, simultaneously feeding on people’s fears while creating a veneer of comfort and sense of protection – while all the time generating a revenue stream for the creators of the system.

One might argue that profit or not, the fact that Gemini CDS gives the perception of being protected against thieves, then it is sufficient deterrent – and I am, after all, one who is pretty big on seeing perception as a motivator, as my comments around third-party Viewers will demonstrate.

But really, the answer to this must be “no”. Deterrence only works when it is shown to deter (prevent / discourage). When one strips away all the hype, arguments, hyperbole and misinformation circulating around Gemini CDS one is driven to a single conclusion: it will have absolutely minimal impact on “serious” content ripping. While store keeper may well feel comforted by seeing this system boot 5 or 6 people a week from their sim and even consider that in doing so, it is enabling them to “do their bit” to stamp out content ripping – the very sad fact remains that ripping will continue unabated elsewhere on the grid  – and probably at levels that have remained more-or-less unchanged for the last several years.

The there is the annoying niggle over the validity of the system. Gemini CDS is owned an operated by individuals outside of Linden Lab. They have no “official” position within Second Life and no sanctioned authority. They maintain the Gemini CDS system under a blanket of secrecy that goes far beyond the need to protect (as they put it) “trade secrets”. There is no oversight as to which Viewer is or is not branded a “copybot”, there is no oversight of their ban list and there is no guaranteedmeans of appeal should someone feel they have been wrongly banned. Indeed, as Mitzy Shino has already found out, the owners of the system are predisposed not to accept appeals and lift bans.

I won’t go so far as to claim Gemini CDS is insidious or a waste of time per se. While the system has been developed by individuals with a questionable past, others have managed to test it to the point where it is not doing anything overtly insidious – my only caveat being that we only have the creators’ word that it is only collecting data related to the use of “copybot” Viewers (although as I use Emerald, I’m in a bit of a cleft stick in this regard). Further, that it does give store owner a naive sense of security – which they are entitled to, having paid for the system itself and continue to do so on a monthly basis in order to retain their sense of comfort – then I’ll grant that is has done some good for them.

But I’d draw the line far short of Gemini CDS being the kind of panacea for content ripping many portray it to be believe. In the wider scheme of things, the best one could say about Gemini CDS is that it is a placebo – :quit! (for those familiar with Copybot “destectors”).

A brief history of content-ripping

This “little” post has come about as the result of a suggestion from regular reader, Peter Stindberg, which followed the concerns I raised about the “Bye Bye Copybot” prim being circulated by members of the Emerald team, and lauded by  some content creators and others, despite its potential as a ToS violator.

Before I get to the nitty-gritty, I will point out that while what follows is a genuine attempt to timeline events and interrelations of events as accurately as possible, the degree of paranoia and misinformation surrounding content ripping means that a) there is a possibility I may fail to mention some events ; b) some may view things differently (and may themselves not necessarily be correct); c) I’ve confused issues (although I’ve verified as much as I remember over the years with various sources elsewhere) – in which case polite corrections welcomed!

libsecondlife

Up until 2006, Second Life had largely been a closed universe: the code for both the server and client-side software was developed purely by Linden Lab. There had been issues around copying content – tools like GL Intercept, which enabled the likes of avatars to be copied, and basic tools and scripts that enabled textures to be pulled from the local cache. However, these tended to be somewhat obscure as far as the populace of SL at large were concerned, which somewhat mitigated their impact (but didn’t excuse their use).

Then something happened: libesecondlife was created.

libsecondlife commenced, with Linden Lab’s blessing, as group of Second Life residents attempting to back-engineer an open-source version of the Viewer (client-side software).  Today, to avoid copyright issues in relation to the Second Life name the group is now called lib.openmetaverse.org.

CopyBot

As a part of this work, an automated tool was developed – CopyBot that could be used to replicate avatars – bots, and be used as a debugging tool. The original CopyBot required that that target user actively give permission to be copied, and issued a disclaimer (in the form of a drop-down) prior to the copying taking place, specifying the fact that ownership / permissions pertaining to anything worn by the avatar would be lost in the copying process.

The software itself (written in C#) worked by intercepting the communications between the Viewer and server and replicating the information relating to objects (prims, textures). In doing so, and due the the way in which Viewer / server communications had been coded by LL, the copy process would lose the metadata relating to the original creator of the object and all permissions set against it – there was simply no way of including this information in the raw copy process as written in C#.

The original version of CopyBot was published as a part of the libsecondlife library of tools, where it became relatively easy for someone to remove the code asking for the target’s permission to be copied and the disclaimer drop-down, and thus use the code to copy virtually anything in Second Life – with the exception of scripts, gestures and animation (although later iterations of CopyBot could apparently grab animations and gestures from avatars) – completely surreptitiously, giving birth to CopyBot as we know it today.

What made CopyBot different to earlier attempts to rip content was its relative ease-of-use, it’s availability and – inevitably – the notoriety it quickly gained as a result of being made “public”.

From the start, the libsecondlife group were fairly unconcerned by the risk CopyBot presented to content creators, demonstrating a “so what?” attitude, supported and repeated by other techies posing as “journalists” as the news broke. Indeed, in one such interview, libsecondlife’s Admin, Babba Yamamoto intimated the issue of metadata loss could have been overcome if the CopyBot code had been re-written in XML (this is in fact how tools such as Second Inventory and Viewers such as Meerkat and Emerald “legally” export content)  – but no-one saw the point in doing so, since the “flaw” that lost the metadata lay with the way LL had originally coded Viewer / server communications, so those in the libsecondlife group felt justified in deflecting anger directed at them by pointing the finger at LL.

libsecondlife did eventually pull the CopyBot branch from their open source library as the wave of outrage reached the level of a tsunami – but again (and to mix metaphors) their action was that of not only shutting the stable door after the horse had bolted – but having ensured the horse had an open-ended ticket to any destination of its own choosing as it left the stable.

Protests and Response

The “revised” CopyBot code quickly started showing up as being for sale both in-world and on SL Exchange and immediately generated uproar as a result. Protests were held, the forums were flooded and people were angry: stores were closed; sims locked down, and calls were made to boycott Second Life.

While the libsecondlife group’s reaction remained pretty much, “so what?”, Linden Lab’s initial response to the protests could best be described as lukewarm, with Robin Linden repeating the assertion that content copying is “not necessarily” theft – a meme initially rolled out by Cory Linden – himself an active supporter of libsecondlife. While the meme is technically true (it should be pointed out that Second Inventory, for example, effectively uses CopyBot-style coding with ownership and permission checking in place, to export objects from Second Life, for example), it was also was somewhat disingenuous to raise it in the context of content ripping.

Many were angered by this reaction from Linden Lab, which gave rise to a further round of protests. Some of these made headline news in the likes of Business Week and  News.com – prompting Linden Lab to take something of a more affirmative stance, revising their policy to make it clear the use of CopyBot and similar tools would not be tolerated. While the move was in some ways welcomed, it was also felt that it was the risk of poor publicity, rather than a desire to help reduce the risk of Copybotting that prompted LL into “action”.

Nor was the revised policy that successful. By referring to the use of such tools as CopyBot, the policy implied that the sale of such tools in-world was still OK – and so people kept right on selling it at up to L$1500 a pop, quite prepared to face the wrath of residents while the Lab again kept quietly to the sidelines.

At the same time as calls for tougher action against CopyBot and it users continued, so to did the counter-argument “that nothing can be done” to stop the matter (an argument still heard today) gained strength among techies. People pointed to the code behind web pages being viewable and therefore copyable; people pointed to the existence of tools such as GLIntercept that could copy avatars, people raised the issue of ripping MP3s over the Internet as reasons why CopyBot was not only “inevitable”, but should be more-or-less accepted.

While such statements are broadly true, they in no way justify the theft of Second Life content – or any theft for that matter. Rather, they deflect discussion from the core issue that Second Life is promoted as a platform of commerce, and as such those encouraged to take up business opportunities on the platform should be offered a degree of protection that appeared to be somewhat lacking on LL’s part.

Promises and Tools

Another reason people perceived Linden Lab as having little concern over the matter was the time taken to develop practical tools that could help in the identification of potentially ripped goods. Conversations around such tools commenced in November 2006, with Robin Linden’s above-mentioned post. However, it was not until April 2008 that the first really useful tool –  the Object Inspector – finally made its debut;  18 months after the initial furore.

Now, there could be perfectly legitimate reasons as to why such a tool took so long to develop and deploy. However, during the 18 months it was in development, Linden Lab was largely silent on the matter of content ripping, giving rise to the perception that they “weren’t interested” in dealing with the issue. Right or wrong, this perception was further reinforced by the fact it was not until August 2009 – nigh on three years after the original protests – that the Lab saw fit to outline updates to their IP Complaints Process, as outlined in their Content Management Roadmap. Even then, insult appeared to be added to injury in that elements of the Roadmap appeared less concerned with the worries of current residents as they did in providing the perception of content protection for “upcoming” users of the Second Life Enterprise product.

In the meantime, CopyBot development continued among known hacker groups – such as the Patriotic Nigaras – who worked to make the tool more “user-friendly” and added further capabilities to it. While the sale of the tool was banned from both in-world and on the likes SL Exchange / XStreetSL, CopyBot does continue to be available through various torrent sites – although I understand (but have absolutely no proof) that many of the advertised CopyBot downloads are, in an ironic twist, themselves riddled with viruses / Trojans.

Viewer Threats

Throughout 2007 and 2008, CopyBot remained an issue. Exactly how widespread its use was was difficult to assess: paranoia meant that many reports of copying came via “friends of friends of friends” rather than first-hand exposure, and the storm was further whipped up by merchants selling “anti-Copybot protection” tools that were little more than scripted placebos. While such tools did little or nothing to stop Copybotting, their widespread proliferation  in stores across the grid reinforced the perception that Copybotting was epedemic in proportions.

Then the landscape started to change. In 2007, the first fully-functional third-party Viewers began to appear. Over a period of several months, a crop of Viewers showed up that offered people a genuine alternative to the “official” Viewer, which was regarded as poorly-written and crash-prone. What was more, these Viewers not only offered improved stability, they also tended to offer features that users has been requesting from Linden Lab without any success. As the popularity of these Viewers increased, so did the likelihood that the Viewer code would be maliciously hacked.

This likelihood became a reality in 2009, when the first of the “CopyBot Viewers” appeared in-world. This did raise content theft to a new level: now it was possible for anyone to grab content (with the exception of scripts) simply by using a modified Viewer – no other tools or add-ins required.

As with CopyBot itself, Linden Lab were initially slow to respond, despite the renewed outcry the appearance of these “hacked” Viewers caused. It was not until February 2010 that their Third Party Viewer (TPV) Policy first appeared.

BuilderBot

In mid-2009 the matter almost took another very nasty turn when Jim Himoff of Rezzable suggested an in-house tool created by his company would be made available to the open source community. This tool was Builderbot. Based on the CopyBot code, Builderbot enabled entire sims to be “backed up”: land, buildings, content, textures – all in a single pass.

Like CopyBot, Builderbot was initially developed with a genuine function in mind: Rezzable had invested heavily in Second Life in terms of sim development and commissioning custom builds they have not only paid for, but have purchased the rights to as well. When they opted to make a move from Second Life to their own OS Grid, they obviously wanted to take their investment with them: hence Builderbot.

However, Himoff’s announcement of issuing Builderbot to the open source community as an unrestrained tool was alarming, and his very public claims that it presented “nothing new” as it was based on “CopyBot” and the “CopyBot was already out there” was an utterly disingenuous excuse. Given the history of CopyBot, any release of an unrestrained version of Builderbot would have been worse than mischief making – it would have been as malicious as pulling the pin of a hand grenade and tossing it into a crowded room.

Fortunately, such was the outcry over the announcement that Rezzable quickly backpedalled away from their stated intent (assuming said intent wasn’t a stunt aimed at raising Rezzable’s visibility and that of their new OS Grid offering), opting instead to develop a version of Builderbot that would include ownership and permissions protection. So far as I’m aware, no version of Builderbot has to date been released.

The Present

Most recently, Linden Lab again caused some consternation with the release of Viewer 2.0 – which had the invaluable Object Inspector completely removed. Why this was done is anyone’s guess, but it lead to some consternation on the part of residents using it – so much so that a JIRA was raised and LL reintroduced it with the first Viewer 2.0 update –  although one has to ask why it was removed in the first place.

We’re still awaiting further updates around the Content Management Roadmap – again nothing has been heard of on this subject since the August 2009 blog post, giving the (potentially wrong) impression that it has fallen of LL’s radar in the rush to get Viewer 2.0 and all things “Enterprise”-related out the door.

Currently, the subject of content ripping remains contentious. Not because it isn’t happening – it is – witness the recent XSL sale of ripped dances and Ishy Wingtips’ highly-literate and thought-provoking flog posting on the subject as it affects the Teen Grid –  but rather because the accepted perception is that copy ripping has reached pandemic levels in Second Life. This perception has resulted in a lot of misinformation to enter circulation – some of it through simple misunderstandings, some of it to deliberately derail attempts to halt the further spread of the problem.

The waters have also been muddied by the subject of “copybotting” being used to promote other agendas. Towards the end of 2009, for example, a number of high-profile content creators used the subject of copybotting to float the idea that only a selected “elite” (my term) of content creators should be allowed to operate in Second Life. Among other things, they suggested the criteria by which such creators should be selected should be related to in-world turnover – an idea that found its way into the Content Management Roadmap thus: We are starting the process of planning a content seller program, and we would like your input on possible program criteria. At a minimum, participation in the program will require that the selling Resident…..3. meet a minimum threshold for content transactions.

Quite how limiting the number of content creators to a “selected few” would stop content ripping (given their own content would clearly become the target) has never been fully explained – but the fact that their views, issued under the guise of concern about content ripping, found their way into the draft CM Roadmap is disturbing.

Beyond this, and in part due to the apparent lack of concern from Linden Lab on the matter, in-world tools to “combat” Copybotting have appeared over the years. How effective any one of these tools is, I cannot honestly say. Some appear utterly useless and smack of cynical attempts to cash-in on people’s fears. More recent tools have appeared that seem to offer a degree of protection against the use of “hacked” Viewers, but even these are subject to considerable controversy, inasmuch as a) they have been developed by former content rippers (allowing their potential effectiveness to be undermined using the question of trust), and b) the creators have been so secretive around the tools, entire rumour mills have been created around them- and not always positively.

And so we come bang up-to-date with things, and the post that initiated Peter’s suggestion that I try to summarise (!) things relating to Copybot, etc.

I think I’ve covered all the bases and key events. If I’ve missed anything significant, I apologise, and will attempt to correct any omissions / inaccuracies that are pointed out to me.

Further information on CopyBot and the furore around content ripping can be read at:

Note: Revised Mar 26, 2010 01:45 BST to better reflect the situation prior to the advent of CopyBot. With thanks to Tateru Nino for both prodding me in the right direction and for giving further information.

The road to hell…..?

I use the Emerald Viewer. Over the years I’ve used a wide range of Viewers to experience Second Life, from the official Viewer through Snowglobe to Meerkat, Imprudence, Cool Viewer for Windows, KristenLee’s Viewer  – and even Viewer 2.0 and the Snowglobe iteration of Viewer 2.0.

But it is with Emerald I’ve found my “home”; of all the Viewers, this is the most stable for my PC configuration and provides the fastest fps rate of any (although KristenLee’s Viewer isn’t that far behind. Truth be told, if KLee’s Viewer incorporated RLV functionality, I’d swap over in a heartbeat, as her rendering pipe just blows everything else to pieces on a good graphics card).

It is true that Emerald has features that could be a nuisance if incorrectly used: the ability to locate anyone on a sim and Tp right into their face is one. I’m also aware of the claims of data scraping and the like surrounding Emerald and the claims relating to it ignoring permissions (generally made by those who have not sought to actually use the Emerald export tool). But the fact is, Emerald includes much that has been lacking in the official Viewer for general users, builders and estate managers – and these make it a winner.

As such, I applaud the efforts of the Emerald Dev team in building and maintaining a versatile Viewer.

However, even good intentions can go a step too far. Today, members of the Emerald Viewer group received a Notice and attachment I’d venture to suggest is questionable.  The attachment came in the form of a wearable prim. The Text of the Notice accompanying it reads thus:

This neat little prim has certain magical properties about it that causes viewers that do not respect permissions to crash when selecting it.

We turned it into a sort of “copybot shield” you can wear.
Fractured thought you guys should have these, they won’t hurt any viewer that respects permissions.
Come by Emerald Point to see us if you liked it.

So in essence, it is a prim that can be worn and which contains a script that identifies malicious Viewers and crashes them.

Now *IF* this prim is for real (there are no visible scripts, so exactly how it detects / communicates with “illegal” Viewers is beyond my ken), then on the surface it would appear to be a neat trick in deterring copybotters. However, *IF* it is for real, the tool raises concerns on a number of fronts.

  • At the very least, it would appear to violate the Terms of Service, to whit, Section 4.1, which includes the statement: In addition to abiding at all times by the Community Standards, you  agree that you shall not: (v) take any actions or upload, post, e-mail or otherwise  transmit Content that contains any viruses, Trojan horses, worms,  spyware, time bombs, cancelbots or other computer programming routines  that are intended to damage, detrimentally interfere with,  surreptitiously intercept or expropriate any system, data or personal  information. Given this prim has the ability to crash suspect Viewers, it could be argued that it is a form of Trojan horse  / time bomb intended to detrimentally interfere with other systems
  • While copybotting is a major concern, and it could be argued that Linden Lab should be doing more to control / eliminate the worse cases, this same argument does not entitle users and /or content creators to undertake what amounts to be vigilantism in lieu of firmer action on the part of Linden Lab (and I say this as a creator of content myself). Two wrongs simply do not make a right
  • There is already a degree of controversy surrounding the Gemini CDS system marketed by members of the Emerald team – not in terms of whether or not it hack people’s computers (it doesn’t) – but rather in the number of “false positives” it has been reported as giving. Can we be sure this tool is actually foolproof, even if vetted?
  • What gives a group outside of LL the right to determine  which Viewers should or should not connect to Second Life? LL themselves are already in the process of rolling out their Third Party Viewer (TPV) Policy. While it has a number of flaws within the revised wording, it is nevertheless the official means be which the use of malicious Viewers is to be contained. What gives one or two developers who have no direct accountability to Linden Lab or anyone else the right to take matters into their own hands?
  • The means by which Viewers are added to this tool (assuming it is going to be maintained) is far from transparent. While the best of intentions may have been behind its creation, it is therefore open to potential abuse
  • What happens should a rogue coder decide to retaliate?  If this tool can be developed to target “illegal” Viewers, how hard would it be for someone to target a specific Viewer – the one supported by this tool’s creator(s)? If the tool can be worn, it can be rezzed in-world as a mass griefing tool. Do we then enter a war of escalation?

I’m genuinely curious as to whether anyone in authority at Linden Lab was consulted during the development of this tool or prior to its release. I’m also very interested to see how they respond to its presence on the grid.

Again, I have little doubt the intentions behind the tool were good. The major problem with good intentions is the manner in which they invariably pave all the roads leading to hell….

Coming to a splash screen near you – your own MOTD…sort-of

In June last year, people logging-in to SL and who hung around while the progress bar was displayed caught a rather unusual Message of the Day (MOTD), thus:

(with thanks to Ciaran Laval for this image)

At the time it caused a mix of teeth gnashing and speculation. When pressed, there were mutters from some inside the Lab that the Azure MOTD was a “pilot” (or “beta” or some such), and that others would get the opportunity in “the future”.

Well – it seems the future has arrived.

On the surface, it comes across as a reasonable idea – those running businesses in SL can have the opportunity to reach a wider audience by having their very own Message of the Day displayed on people’s Viewer log-in screens. Of course, there have been the inevitable howls about “more advertising” in response to this post – but lets be honest here; LL have taken something of a shellacking of late for the manner in which they’ve used the MOTD to promote their own in-world content (vis-a-vis Linden Homes, etc.) – so one might argue that this is an attempt to redress the balance and put residents on the same footing.

Well yes. Apart from one small detail. Anyone wanting to use this “service” is going to have to shell out a minimum of $1500 for each 11.5 hour block of advertising space they want to book – with the “peak” rate (07:00-18:30 PST) being hawked by the Lab at a staggering $4500 per 11.5 hour block.

(Technically, each block is 12 hours – but LL “reserve” 30 mins in each block for “administrative purposes” – which suggests your MOTD may not be actually displayed during this period.)

Ciaran Laval has rightly called out Linden Lab over these charges from the perspective of the more modest estate owners in SL – as it is fairly obvious that the rates are only likely to be within the reach of the largest land barons. However, and while acknowledging Ciaran’s call on behalf of the smaller estate owners, I’d say the matter goes further than just the ability of estate owners to use the MOTD as a channel to market – the pricing structure virtually excludes all content creators from any participation.

Given this, one can only assume one of three things; either:

  1. LL is increasingly playing to a minority within SL, or
  2. LL is indeed in financial difficulties, and this is an act of desperation to generate income, or
  3. The offer has been skewed by LL’s continued belief that the future of the platform is inevitably tied to the use of the platform by “big business”, and as such, the rates have been set in a belief that they’ll be seen as a “serious” “opportunity” for “big business”.

Inevitably, most will go with (1.). But the FIC theory is all too often rolled out in response to LL’s actions whether or not they make sense.  (3.) has merit in that those who consider themselves “serious” businesses (aka the GSP group) pushing for the ability to market themselves “professionally”, and LL seem to determined to tie aspects of activities on the large grid into their SLE offering.

(2.) Is also possible – and certainly, if one leaves out (1.) and (3.), the “offer” does have more than a whiff of desperation about it.

As I’ve said elsewhere, I’m going to be very interested to see just who takes up the offer.