Category: Second Life

Posted in Phoenix / Firestorm, Programming, Second Life, Viewers

The pain of compiling your own Viewer

Posted on by beccapet

This post has been superseded. Click here for the updated post. 

I’m sadly well aware that very few people read my blog and that even fewer have the technical ability or desire to build their own Viewer from the source code, but I know there are a handful and this is for them.

Firstly there is a LOT of pain. Lots of getting all the right libraries, support tools, resources and the like before you even begin to struggle with compilation errors.

Mariana Latynina is blogging about compiling under Linux64, and has tried several code bases including Phoenix
See http://marianalatynina.blogspot.com

And Forestaurora is blogging about Phoenix under Windows
See http://forestaurora.wordpress.com

You can see from there quite how much work is involved in getting a compile done. Surely it has to be easier than that?

(Oh, and a ‘hi’ to Tonya as she’s probably the only person who will read this post and even then only because I’ll point her at it. LOL)

—

Update: The guys at Radegast have the right idea. Ok, it’s not a full Viewer, but even so it’s the kind of thing we’d like to see:
http://radegastclient.org/wiki/Building_From_Source

Posted in General, Second Life, tips

Top Tip: Disable scripts on items that don’t need them

Posted on by beccapet

Lots of clothes are now coming with standard resizer scripts, which include the ability to delete the scripts when you have fitted them right. This reduces lag and is a really good idea, although you should always make sure that you have a backup copy first. Never do this on your only copy if you ever plan to change your shape!

But what if you have a no-copy outfit like the amazing full-prim outfits from Feral Spirit by Melanie Jaehun? You have a problem, because you can’t make a backup and you don’t want to delete the scripts in your only copy of the outfit.

Melanie made the excellent suggestion that, for objects that are no-copy but are mod, you can disable the scripts instead. With 1.x Viewers (eg. Phonenix, Imprudence, etc.) you go to the Tools menu and select “Set Scripts to Not Running in Selection” for each object. This will have the same lag-reducing benefits as removing the script, but without losing the ability to re-enable it and run it again in the future.

Thanks for the tip, Melanie!

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

Viewer usage in Second Life, post-Emerald

Posted on by beccapet

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

Posted on by beccapet

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?

Posted on by beccapet

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 Emerald, Imprudence, Second Life, Viewers

Emerald, Emergence, Phoenix – confused? You’re not alone!

Posted on by beccapet

I was talking to a friend in Second Life today who was really scratching her head over what viewer was what and what the hell was going on. So this is just a short post for her and anyone else who might benefit.

  • Emerald – well, I think everyone knows about Emerald. And those that are still running it are simply ignorant or don’t care.
  • Emergence – this is a sanitised Emerald (ie. Emerald with the bad stuff taken out) that was done by LordGregGreg. Don’t get too attached to it because he has said he is not going to develop it further. So there will be no updates. This is partly because he is now on the development team of…
  • Phoenix – this is another sanitised Emerald and is being actively developed by some of the ex-Emerald team. They are following good software practises as detailed in this post of mine, so I have very high hopes that this is going to be a goodie.
  • Imprudence – this has nothing to do with Emerald and is a completely different Viewer. It is also following good software practises. I wrote a short review on it here

There are other Viewers out there too – Cool Viewer and Kirsten’s Viewer, for example. However I don’t have enough experience of them to comment.

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

The Phoenix Arises – Emerald by a different name

Posted on by beccapet

Well, it seems Jessica Lyons doesn’t hang around and has assembled a team to take over where Emerald left off. And amongst that team is LordGregGreg.

According to her blog entry [here], Phoenix is starting out as a sanitised Emerald, like LordGregGreg’s Emergence Viewer, and will be developed from there.

In keeping with my recent post [here] on how an Open Source Project should be run, they’re running a publicly-viewable repository and full transparency.

This is very encouraging news indeed.

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

Privacy concerns with Viewer 2.0

Posted on by beccapet

[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 Flickr, Photography, Second Life, tips

Second Life Photography

Posted on by beccapet

[Originally posted 19-Mar-2010 here]

Photography is one of the many things I enjoy in SL. At the time of writing I have over 660 pictures on my Flickr account

Torley Linden has a great wiki page on various tips and tricks here:
wiki.secondlife.com/wiki/Snapshot_Help

One trick I use a lot is to take a snapshot using the dialog and then use the mouse-based camera controls to get the angle just right and then refresh it again. There’s a simple tutorial on it here. If you’re into SL photography then it’s a great technique to master.

Something that has annoyed me for ages is the foot shadow. I’m forever trying to correct it in post-production because the invisiprims on a lot of my boots cause the shadow to come out wrong. This problem will start to go away with the new alpha masking for feet in Viewer 2.0 but it will still be around for a while. So imagine my delight (and annoyance that I only just found this out) when I discovered you can turn off the foot shadow!
It’s Advanced menu > Rendering > Features > Foot Shadows
D’oh!

For my next set of photos I’m planning on making use of the depth and object matte capture modes and introducing depth of field in post production. Should be a new challenge for me and I’m really looking forward to it. Watch this space!

Continue reading “Second Life Photography” →

Posted in Emerald, Opinion, Second Life, Viewers

Emerald – so what went wrong?

Posted on by beccapet

[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.