Second Life

Will Burns (SL username: Aeonix Aeon)

Will Burns (SL username: Aeonix Aeon)

Both in SL and in RL, I’m quite lucky in being honoured with the friendship of knowledgeable people who rise above the typical level of discourse and speak in a down-to-earth, matter-of-fact, manner, with arguments based on facts, logic, and knowledge, rather than fear and “common wisdom” – which, more often than not, is actually common myth. One of these people who have bestowed on me the honour of their friendship is William G. Burns III (SL username: Aeonix Aeon, SL display name: Will Burns), a published academic, and former Vice Chair of the IEEE’s Virtual World Standards Group. A published and respected researcher and professional in the field of virtual reality and virtual worlds in his own right, Will understands the potential – creative, cultural, and commercial – of virtual worlds that very few commentators in Second Life can rival, and he is not one to mince his words. His criticism of Linden Lab CEOs past has always been very severe and, although back then it might have seemed too harsh, with the benefit of 20/20 hindsight I can now see he was just calling things the way they were.

Now, Second Life is, as we all know, in slow decline. Many of its old users are gone, either because they no longer care, or because the ongoing global financial woes have priced them out of what is essentially a costly pastime for people with disposable income and time (two things few members of what was once known as the middle class still have), or because they died away. New user retention is, as has always been the case, disappointing, and more and more private regions sink into oblivion like the lost continents of myth and legend. However, SL still has a vibrant economy, which is based on the creation and sale of various virtual goods – from hairdos to cars and from clothing to furniture. And this economy supports a rather expansive ecosystem of merchants, regardless of whether their products are entirely their creation, or based on resources purchased from other markets like CGtrader.

SL’s merchants apply all sorts of different business models, but there is a common denominator: They are extraordinarily precious about their creations, even if they are nothing but very crude retextures of full-perm templates – sometimes even less than that. One look at most content creators’ dire, straight outta Bible, “fire and brimstone”, DMCA warnings is more than enough. In the past, many in-world shops had employed CS- and ToS-violating devices that promised (without delivering, but that’s another story) to “detect” potential copybotters. In other cases, store owners ejected and / or banned store visitors for idling, because they genuinely believed that, if you’re AFK in a store, then you are by definition a copybotter. Almost four years ago, a rather botched amendment to LL’s ToS got numerous content creators up in arms, claiming – of all things – that LL itself was “trying to steal their content”; much hilarity ensued, with several creators even ragequitting SL. It is, thus, an unfortunate fact of Second Life that it is very hard to have a calm, reasonable, and rational discussion on merchants’ intellectual property, on the implied and express licences they need to provide to LL so that the virtual goods can be displayed and sold to the customers, and – eventually – consumer rights. Unfortunately, much of the blame must be put on Philip Rosedale, who, regardless of whatever innovative ideas he may have had, has always been a bit of a demagogue. The promises given in 2003 have essentially been haunting SL ever since, often putting customers and merchants on a collision course, with very little – if any – room being given to the rights of the consumer. Naturally, things were further exacerbated, with the stance of many merchants going to full-on prokanoia with the Great Copybot Scare of 2006, which has never quite gone away.

In more recent times, the suspicion with which SL merchants have traditionally viewed customers has taken new forms: Mesh body creators demand that apparel, jewellery, shoes, etc. created for their bodies be non-modifiable, “to prevent copybotting”, even though permissions have exactly zero impact on a Copybot viewer’s ability to intercept and extract an object. We have the infamous “anti-rez” scripts, which are another form of “anti-copybot” snake oil. And so on, and so on. So, to have an honest, open, no-nonsense discussion on this risky topic, I needed to talk to someone who actually knows what he’s talking about and doesn’t mouth off based on false assumptions and blatant misunderstandings of web-based platforms like Second Life. Inspired by the licensing suggestions he made in this post on his blog, I invited him over to my always work-in-progress café, and we had a lengthy, but most enjoyable and productive, discussion.

Read Full Article

Advertisements

I had written about the issue of lag before, and before me, Penny Patton had done the same, and I think very little has changed for the better since then. Most of the “lag” we experience in Second Life is blamed on Linden Lab, whose engineers are always accused of basically not knowing what they’re doing. Rarely does it cross our mind that we, the users – from consumers to content creators – are doing something wrong.

Read Full Article

What am I to do with all this junk?

What am I to do with all this junk? – Click on any clickable image for the full-size version (they open in a new tab).

Every now and then, on Plurk and other platforms used by SL users, some dismayed user will ask for help with managing their inventory, because it has become bloated, terribly disorganised, and, as a direct consequence, it’s become terribly hard for them to find the things they need when they need them. Bloated and disorganised inventories are also linked to a serious drop in the viewer’s performance. Having gone through similar situations myself, I’ve devised several methods that can be of help, and I’ll offer them below.

Read Full Article

mona-profile-pic-by-liara-1-512Regular readers of this blog might have noticed I’ve put all my analytical and opinion posts on virtual reality, virtual worlds, and Second Life in particular on hold, opting instead to dedicate my time and efforts to my story titled Arianna, of which I’ve already written three chapters. As I’ve explained in a recent post, events in my SL during the past few weeks have been extremely painful to me.

I wrote my heart was broken recently. That was an understatement. These events destroyed my faith, trust, admiration and love for someone I adored and looked up to. They also opened my eyes to how little regard that someone had for me; you certainly don’t let your new lover hurt, humiliate and insult a “valued and trusted friend and confidante” in front of you. At the very least, you’ll be alarmed by such behaviour and you’ll defend your “valued and trusted friend and confidante” – after all, lovers come and go and friends are forever, right? This didn’t happen in my case.

What happened before that fateful Saturday and afterwards, as I discovered more and more of what has been going on, only served to bring back painful memories from my real life. SL for me is, to a great extent, a form of escapism. I have my own RL problems and stresses; I have my whims, fantasies and desires that can’t be satisfied in RL, and SL largely serves as an outlet, creative, social or otherwise. Because of things that had happened in my RL, I’ve been dealing with depression for many years. I tried to deal with it through sporadic cognitive-behavioural therapy (when my finances allowed it) and by keeping myself as busy as possible. RL circumstances beyond my control during the past few years have not been exactly helpful. What happened recently in SL was the final straw. It was the trigger that brought back all the memories I’ve been pushing away, and the catalyst for the fire to burn more intensely inside me, to burn me more intensely and make the pain even worse.

I’ve been trying to take my suffering in silence. It was one little thing after the other that added and added to the burden on my back. I kept trying to adapt. To fit in. To be and do what would not offend, what would be liked and appreciated. It didn’t work. I was shutting myself up and down, emotionally, verbally… In every possible way. Just to hear a good word; a word of truly heartfelt praise or appreciation. To receive a hug, a smile, or a kiss. I kept trying and trying, but to no avail. And then, whatever little I had, or thought I had, was taken away from me and shattered before my eyes.

I decided I’ve remained silent for too long. If it’s OK for others to hurt me, it’s OK for me to speak of what I’ve been through. In my own voice. I decided to tell my story – my first ever organised and concerted attempt to write a story. Thus, Arianna was “born”. The title was taken from the first name of the first SL account I created, way back in 2006. You could say I am Arianna, and it would be true in so many ways. The story itself is a blend of fictional and real events. It is set in a fictional version of the UK. Obviously, neither Ashworth, nor Dagenhull or Sunford exist. And, unlike Arianna, I haven’t committed suicide. That’s not to say I haven’t contemplated it, though, or that I haven’t been tortured – especially recently – by thoughts of whether people would be better off without me. So, while the suicide that kicks off the story and the exploration of what led the protagonist to jump off the bridge is fictional, the events of Arianna’s life are not. They are adaptations of RL and SL events and dialogues that have really happened. By “adaptations”, I mean I’ve adapted the events to fit in with the environments I describe in the story. Perhaps you could say it’s a mixed reality novel. Well, at the very least, it’s inspired and informed by my existence in both the physical and virtual realm.

Fallen

I mentioned that this story has very real elements. For instance, in the second page of the second chapter, the reader is presented with Arianna’s suicide note. It’s a real suicide note, from my RL. One I had written ten years ago, but never acted on it. As said earlier, the actions, events, and words that led Arianna to jump off the fictional Ashworth bridge are real. They’re words that were really said; they’re events that really happened; in both worlds: the physical and the virtual. Of course, I have changed the names of the people involved, although some might be recognisable – easily or with difficulty.

The – real or perceived – recognisability of the novel’s characters is something that concerned me as I was beginning to write my story. Would it cause upset? Would it cause gossip? Would it… (add whatever worry or concern you want – legitimate or not)? Would rumours start to circulate? Would it cause drama? Shouldn’t I protect those involved? I thought long and hard about it, considering the past, the present… And what could come in whatever future there can be. In the end, I decided to proceed. After all, it’s my story. It’s my pain, and I need to let it all out. I can no longer suffer in silence. I can no longer keep it all inside me. With every word I write, I bleed, for I relive each instant, each moment.

I know people may get upset with what I have to say, but I need to do it. People around me do what they want, and, as far I’ve seen, without asking if and how I’m affected; this time, I’ll do what I need to do. It must also be said here that, just like my post on the “drop” in D/s relationships (which, ironically, is my blog’s most popular post by far), Arianna is something I wished I would never have to write… But there you have it. And you can interpret it in any way you want, depending on your perspective.

As to my “other” blog work… It will continue. I’ll keep my other articles coming, if perhaps at a slower rate. But Arianna is something I need to do. And if anyone gets upset by it… I’m sorry they feel this way.

.

Chapters already published:

.

Shortlink: http://wp.me/p2pUmX-L1

build-floater

The Build Tools floater – Firestorm’s version; the official viewer’s doesn’t really differ significantly. Please click on the picture for a larger version.

Whether you live your virtual existence in Second Life or OpenSim, the viewer’s build floater (right) is, in all likelihood, an integral part of your experience. From simply adjusting your worn attachments to putting together intricate and complex builds, using the build floater is practically inescapable.

As I’m pretty sure everyone in SL and OpenSim knows, to put several (or many) prims, sculpts and / or meshes together, you need to link them. Now, imagine the following scenario: You’ve been working on a complex build for weeks, and you’re near its completion – you’ve even made scripts to control parameters of its various parts. And you accidentally click the “Unlink” button, which is “conveniently” placed right next to the “Link” button. And you’ve just unlinked everything. Yes, I know. You can re-select everything and link the items again. But everything will be out of whack; different root prim, different link order, and don’t get me started on the extra work you’ll have to do on the scripts. Or the LI discrepancies under the new accounting system.

I was discussing the matter with Inara Pey recently, and she said we should be asked to confirm we really want to unlink the selected object(s) – just like we’re asked to confirm that we want to log out.

It actually makes sense. Quitting and logging in again doesn’t really cause much inconvenience. It’s usually just a matter of minutes before we’re back in-world, usually where we were when we logged out. But unlinking a complex, scripted object can be a royal pain. So, I have decided to file a feature request JIRA on SL’s official bug tracker system, and (after being prompted by Whirly Fizzle) another one on Firestorm’s.

The proposed functionality is as follows:

When you click on the “Unlink” button, a pop-up window (accompanied by the typical sound alert) will appear, with the prompt “Are you sure you want to unlink the selected object(s)?”. Underneath, there will be the option for you to never be shown this message again (“Do not show me this again”). It’s quite simple, really, and would help us avoid frustrating and time-consuming mistakes.

notice

We’re asked to confirm we want to log out of SL or OpenSim, so why not get a notification of this kind when we’re about to unlink a linkset?

If you think such a new feature would be useful to you and you’d like to help bring attention to these two JIRAs, watch them on their respective bug tracker systems (at least in LL’s case, voting doesn’t really do much). Of course, there can be more ways to further improve things: Different colours for the two buttons, for instance, and / or a confirmation for when you click the “Link” button.

UPDATE: The Firestorm team responded quickly to my feature request; Ansariel Hiller added this notification facility, and it will be available in version 4.7.0 of the popular viewer.

.

With thanks to Inara Pey and Whirly Fizzle

.

See also:

.

Shortlink: http://wp.me/p2pUmX-J9