Posted in Fashion, Flickr, Photography, Second Life

Mixing it up

I love my digital art, and sometimes I like to mix things up a bit. The foreground is from Second Life, of course, but the background was taken in Crysis: Warhead.

I spent ages on this pic, what with fitting the hair to the beret, finding the pose, doing the snapshots in both SL and Crysis, and then all the post-processing (not least correcting SL’s various clipping issues) . I’m quite pleased with the result.

For reference, the various parts of the outfit are:

  • Skin: Tess by Laqroki
  • Eyes: Laqroki
  • Hair: Hunter by Magika (customised by me)
  • Beret: British Para beret by SA Quartermaster
  • Top: Jungle Camo Tank Top by Reasonable Desires
  • Trousers: Woodland Camo Pants by Breach
  • Boots: 9″ Combat by Adi Cat Designs
  • Hand gun: Heckler & Koch USP by Breach
  • Rifle: part of the background
  • Background: Crysis Warhead

Dog Tags are from the SL Library

Posted in General, Imprudence, Phoenix / Firestorm, Photography, Second Life, tips, Viewer 2.x, Viewers

Profile pics and profile Picks (a tutorial)

A lot of people who have made their own picture for their Profile find that it appears squashed or stretched. There is a very good reason for this and it is fairly straightforward to work around. The aim of this post is to try to explain how.

Before I go any further though, do bear in mind that this whole tutorial is all to do with 1.x Series Viewers (ie. official Viewer up to 1.23.5 and most Third Party Viewers such as Imprudence, Phoenix, Emergence, and the like) since Linden Lab in their infinite (lack of) wisdom changed it for Viewer 2.

The key thing to remember with textures (which is the name Linden Lab uses to refer to anything that looks like a picture, which includes snapshots) is that they are always square or else rectangles made up of squares. And those squares are always powers of 2. So a texture can be 256×256 pixels, 512×512, 1024×1024, 512×1024, 512×256, etc. – you get the idea. The maximum size allowed in any one direction (in Second Life) is 1024.
If a picture does not fit into one of these combinations then it is stretched or squashed accordingly, and this is where the deformation comes from.

You would think that you should be able to just take a snapshot in-world and use it, however this is not the case because the Profile picture, and the picture used in the Picks section of your profile, have specific aspect ratios which are clearly defined by Linden Lab [link]. For your Profile pic this aspect is 4:3, and for a Profile Pick this is 16:9 (for 1.x Viewers. For 2.x Viewers LL changed it to 1:1 and 8:5/5:3 respectively. Don’t even get me started on why the Picks have two aspect ratios in the 2.x Viewer).
If you’re unsure what I mean by “aspect ratio” then please refer to [this link].
Unless you can somehow capture your in-world snapshot at something close to the correct ratio, then it’s not going to look right.
(I should note at this point that the RL pic in your profile has a 1:1 ratio, which since it is square is so trivially easy to do that I won’t mention it further)

So, how do you get it right? Well, provided you are happy to do a little bit of simple post-production then it is quite easy.
In order to do it you’ll need a photo editing application such as Photoshop, GIMP, Paint.net or even an online service like Picnik. All except Photoshop are free so don’t be worried if you don’t have one of them. I’ll leave it to you to choose what to use. I use GIMP myself, because it is almost as powerful as Photoshop but is free and Photoshop is very expensive. However, if you are a beginner then paint.net is a lot easier and more intuitive.

First you’ll need to take your snapshot in Second Life. Take a snapshot, but instead of saving it in-world, save it to your hard drive.
In v1.x viewers then this can easily be done with the Snapshot dialog, assessed with the “snapshot” button on the bottom toolbar (or the Ctrl-Alt-S keyboard shortcut if you’re using Windows). There is a radio button under ‘Snapshot destination’ at the top of the dialog, one option of which is “Save to your hard drive”.
You can also use “Snapshot to Disk” from the File menu.
Save the snapshot to somewhere that you can find it again shortly.

If you already have a snapshot in-world which you want to use then it is possible to save it locally and use it. Provided it has full permissions, you can open it and then choose “File -> Save Texture As” from the top menu (which is slightly counter-intuitive as you might reasonably expect it to be a menu on the window of the snapshot itself)

Now fire up your photo editing software and open the picture you just saved (regardless of which of the above two methods you used to create it).
Select the crop tool and fix the aspect ratio. In GIMP this is a checkbox on the crop tool and an edit box to specify the ratio. Your mileage my vary.
For a Profile pic you’ll want 4:3 and for a Pick you’ll want 16:9.
Don’t worry at this point what the final image size is because we will be resizing it.

Crop the picture to the correct ratio. It’s up to you how you want this to look, and it depends on your picture, but do remember that when someone looks at your profile the picture can look quite small. So, for your main profile pic at least, I find it is best to close crop and get your face quite dominant in the picture since your Profile picture is meant to be about you. However it’s entirely your call, of course.

Now, this is the important bit; the trick that this whole entry is about is coming up. You want to resize the picture so that it looks squashed, so that when SL uses it and stretches it, it regains its correct Aspect Ratio. Sneaky, huh?
You can do this in one step, but I like to do it in two steps as it makes more sense to me.
Resize your picture, preserving the aspect ratio. You’ll want to set the height of the picture to be either 512 or 1024 and let your software work out the width.
You’ll notice that the picture still looks right. Which is what we want.
Now the sneaky part – size the picture again but this time turn off keeping the correct aspect ratio. In GIMP this is a little icon of a chain between the height and width. Now set the width to be the same as the height. Do not change the height.
Your picture will now look squashed. Don’t worry, this is fine!
Save your picture – I’d recommend to a different filename.

Now, we need to get the picture back into SL as a texture.

Fire up your SL Viewer and, when ready, upload your edited picture (it’s under the File menu). It will cost you L$10 to do this. It’ll probably end up in the Textures folder of your Inventory.

Finally, edit your profile and drag the texture (ie. your uploaded picture) onto the appropriate picture box of the profile. Or, alternatively, double-click on the picture box and browse for it.

Hopefully your picture will look correct again – it will have been stretched out to the correct aspect ratio again. If it has not you’ve probably used the wrong ratio for the wrong box. Remember, for your main picture it should be 4:3 and for a Pick it should be 16:9
Also, bear in mind that it will only look right on 1.x Viewers since Viewer 2 uses different ratios.

That’s it! I hope that this was useful to you.

Posted in General, Opinion, Second Life

Is “take it or leave it” a choice?

Linden Lab published a revised Terms of Service today.

I started reading through it then stopped, because really the only choices open to me were to accept it or to not use Second Life any more. It occurs to me that the “I accept” checkbox should really have been labelled “I accept. Like I have a choice” and been checked by default.

I’m sure other commentators will be along to tell us just how bad it really is. 🙂

Posted in Emerald, Imprudence, Phoenix / Firestorm, Second Life, Viewers

Viewer usage in Second Life, post-Emerald

As I wander around Second Life at the moment, I’m keeping my eyes open for what viewers people seem to be using. Not in a clipboard and notebook way, just getting a feeling.

Before the Emerald scandal, an awful lot of people would have been using Emerald. In fact, up until the point it was blocked there were still a significant number of people using it.

Now that Emerald has been blocked, I was expecting to see a marked increase in the usage of Phoenix and Imprudence, with possibly the odd Emergence from people who don’t realise it is a dead-end choice.

Instead, I’m seeing a handful of Imprudence, the odd Phoenix and a handful of “LGG Proxy” (which I assume is Emergence). And, amazingly, I’m still seeing the odd Emerald (which surely shouldn’t be allowed?)
Everyone else displays no Viewer tag which either means they are using an Official Viewer or else have suppressed transmitting their tag. I know a number of friends who do the latter so this is obviously skewing my results.

I am left with the feeling that public confidence in Third Party Viewers has been severely knocked and people are returning to the Official Viewers in droves. I’d be interested in hearing other peoples’ comments on this.

Posted in Emerald, Phoenix / Firestorm, Privacy & identity, Second Life, Viewers

Emerald Viewer to be Blocked From Second Life

Just posted on the Second Life blog:

As of 10am PT Wednesday, September 8, the Emerald Viewer will be blocked from logging in to Second Life as a result of violations of our Policy on Third Party Viewers. Residents who have been using any version of the Emerald Viewer will need to use a different Viewer to access Second Life. You can download the official Second Life Viewer, developed by Linden Lab, here. Or you can learn more about alternative Viewers, developed by third parties, here. There are several new Viewers listed in the TPV Directory, so there are many alternatives available to you.

We take Residents’ privacy, safety, and security very seriously and will take action to enforce the policies that help protect it. As our CEO, Philip Rosedale, has blogged about, we recently removed the Emerald Viewer from our Third-Party Viewer Directory due to violations of our Policy on Third-Party Viewers.

Since then, we have been in communication with the Emerald development team and have requested several changes in order to remedy violations of our policy, including changes necessary to meet our privacy requirements, and to address GPL license violations. Unfortunately, the team was unable to comply within a stipulated time frame. As a result, we have decided to block logins from the Emerald Viewer in order to protect our Residents. All versions of the Emerald Viewer will be blocked from logging in to Second Life as of tomorrow at 10am. Please be aware that attempting to circumvent our blocking to access Second Life with a banned Viewer is a violation of the Policy on Third-Party Viewers and may result in the loss of one’s account.

[Source: Second Life Blog]

Well, this isn’t a huge surprise. And given the number of people I see still running Emerald, it’s probably for the best. Yes, some will moan but I think LL have little alternative but to do this.
And now that Phoenix (Emerald without the bad stuff) is available then I don’t see what the big issue is.

Posted in General, Opinion, Privacy & identity, Second Life, Viewer 2.x

Display Names – what could go wrong?

There’s a lot of buzz about the new Display Names feature that will allow you to appear to change your avatar’s name.

I’ve heard a lot of people remark that this sounds wonderful, because they’ll be able to call themselves “Sensible Name” rather than  “SomeStupidNameBigBoobies69 Sillyname” (which was funny right up until the point they realised they couldn’t change it).

Well, yes. But unfortunately they’ll also be able to call themselves “Jackie Graves”, “Stiletto Moody” or “Truth Hawks”. But not “Torley Linden”.

Why not “Torley Linden”? Because the Lindens recognise that could lead to confusion. That’s right, they are not going to put any safeguard in to prevent impersonation, Phishing, character assassination, smear campaigns or trashing someone’s reputation unless it’s one of them.

This just seems totally insane to me. If there is no issue with impersonation, as the Lindens want us to believe, then why stop people using the name “Linden” in a Display Name? Or, if is more obviously the case, there *is* an issue then why are they not taking steps to protect *our* identities as well as their own?

The response Linden Lab are making is that these are only Display Names and people can drill down into the profile to see the username. That’s all well and good, but in the Real World we know that email-based Phishing attacks are successful. Do ordinary users look at email headers to see what the actual email account is when the display name is “PayPal” or “Amazon” or <insert the name of your bank here>
Of course they don’t. Nor do they check the actual URL on a link that looks like www.paypal.com but which actually points to www.somedodgyphishingsite.com
So why on earth do the Lindens think users will be any different in Second Life? They’ll just file an Abuse Report against the person that they *think* is griefing them. Or buy dodgy counterfeit or malicious objects from someone they *think* is a legitimate seller.

There are several JIRA entries open on this subject, and as usual a lot of well thought out and well-explained comments and suggestions made by SL residents on them that will almost certainly be ignored by LL and ridden roughshod over.
http://jira.secondlife.com/browse/SVC-6194
http://jira.secondlife.com/browse/VWR-21053
(you may need to log in with your SL username and password to view those. It’s part of the Second Life website so safe to do so)

Likewise, there are a load of intelligent comments, suggestions and concerns in the feedback on the recent Second Life blog announcement on Display Names:
http://blogs.secondlife.com/community/features/blog/2010/08/31/display-names-project-viewer-now-available…

Personally I think the down sides of Display Names in their current form massively outnumber the up sides. However, I am depressively resigned to the fact that all reasonable debate will be ignored by the Lindens and they will press on regardless.

Posted in Opinion, Privacy & identity, Second Life, Viewer 2.x

Privacy concerns with Viewer 2.0

[First posted 09-Mar-2010 here]

If you care about your privacy and identity then be sure to read and vote on this JIRA issue

In short, any Shared Media prim has the potential to get all sorts of information about you – IP Address, Operating System & version, language (gives a good idea of country), Client & version, all sorts.
Possible exploits are linking alts to mains, griefing, stalking, RL harassment, phishing, malware and viruses.

The JIRA entry and the subsequent comments have a lot more information. And this blog is also worth reading.

I’m kind of surprised how few people seem bothered by this.

Update: This blog comment highlights a very scarily plausible scenario for how a phishing attack could successfully compromise your SL account.

Posted in Emerald, Opinion, Second Life, Viewers

Emerald – so what went wrong?

[Disclaimer: This blog entry is personal opinion based on a personal understanding of current events. Should you feel any facts are materially wrong then please contact me, citing sources, and I will be happy to make corrections or retractions as appropriate]

I try to keep my RL separate from my SL, but I guess it’s not giving too much away to say that I work in the IT Industry and have direct experience with software development. So the self-destruction of Emerald has been very interesting for me.

So, where did it all go wrong? I think to answer that you need to look at how a proper Open Source Project is run.

Generally you have a version control system which is able to be read (but not written to) by anyone who cares to do so. Obviously members of the development team can write as well.

This open access ensures transparency, because anyone with the technical ability can examine and review the source code to make sure there is nothing nefarious in it. They are also able to download the entire codebase and compile their own version of the application rather than trusting that the pre-built binaries available for download were actually made from the source code.
Furthermore, the version control system has an audit trail of every check-in, showing what changes were made, by whom, and when. This makes it more difficult to introduce malicious code although there are ways round it, of course. However, even if the developer subverts the process to avoid the audit trail (if they have direct access to the actual files on the server hosting the repository), the code is still available for inspection and anyone can compare a previous snapshot of the code with the current one using an automated difference tool. So there is still transparency.

The trouble with Emerald is that the version control system was not open and there was no transparency. Yes, the source code was published periodically but in a snapshot form. You were expected to trust that this source code was the real deal and not some sanitised version. And that trust was betrayed.

Because there was no transparency, certain members of the Emerald team were able to inject undesirable code (which is well documented elsewhere so I won’t bother going into it here).

Worse still, Emerald also used some Closed Source software which meant that only the developer(s) of that code knew what was in it and the members of the Emerald team were expected to trust that it was non-malicious. Again, that trust was betrayed.

It also appears to me that the team weren’t really following good Software Engineering process. This isn’t too surprising as, as far as I understand, they were all programming for fun and were all fairly young. So there were few controls in place to audit what was going on. I genuinely believe that the more respectable members of the team (and I’ll leave it for you to decide who they are) didn’t know what was being put in by the less respectable members. This is why we have processes, checks and safeguards in professional Software Development and I simply don’t think they were in place for Emerald.

And I’m not even going to comment on the clash of personalities, egos, hidden agenda and motivations of the actual developers of Emerald. That’s not something I want to explore as this piece is really more about the technical side of things.

In many ways, the Emerald project was a nuclear reactor being run without control rods or safety systems, and it went critical and suffered a meltdown.

So, where does this leave Third Party Viewer Development? Are we doomed to use Linden Lab’s awful Viewer 2.0? The short answer is no!
Emerald was not the only Third Party Viewer and some of the others are being run properly. Imprudence, for example, is fully transparent and Open Source. They are by no means the only one, of course, but it’s the one that springs most readily to mind.

Finally, I just want to say that this blog entry may seem very negative about Emerald. However, I don’t mean it to be because I do genuinely believe that Emerald was truly innovative and really moved the Second Life Viewer game onwards. The developers added some very good features (the nefarious ones notwithstanding) and they should be praised for it; they’re clearly very talented. However, as I’ve said, I think the project was very badly run and was very open to abuse. And that abuse was made.

Posted in Emerald, Privacy & identity, Second Life, Viewers

Farewell to Emerald

[Originally posted 01-Sep-2010 here]

As you know, there has been a lot of worry and concern over Emerald with regards to privacy issues, data mining and illegal activities.

Linden Lab have removed Emerald from their Third Party Viewers list and advised everyone to use other Viewers.

As of today the developers of Emerald have folded the project due to mutiny, disagreement, and Linden Lab demanding that certain developers be removed which they were unwilling to do.

I’m sad to see Emerald go as, for all it’s warts and dodginess, it was a very good Viewer and was very innovative.
It’s just a shame that it was ruined by a bunch of immature Script Kiddies who couldn’t resist messing it all up for everyone.

I’m sure the hard work will be back-ported into other Viewers. LordGregGreg has a version of the full source code for Emerald that he has released as “Emergence” although has stated he will not be actively developing it.

Meanwhile Jessica Lyon has resigned from Emerald and has set up a blog to discuss her side of things – jessicalyons.wordpress.com