Wednesday, December 8, 2010

Ubuntu Unity Desktop Review: The disasterous aftermath

Yesterday, I blogged about the current shortcomings of the Unity desktop environment. What happened afterwards, however, is a horror story with a valuable lesson learned, and also something of a testament as to why the *nix command-line still rocks hard.

The problem started when I noticed that Totem and MPlayer started acting weird. When playing a video, the colors were screwed up. But it was kinda funny how people in videos looked as blue as the Smurfs(I now regret not taking a screenshot when I had the chance). So I thought "Maybe I'll check the repositories to see if there's any updates that could fix this".

So I fired up update-manager, and sure enough there were a lot of updates. I proceeded to install them all, thinking it would fix the movie problems and maybe pull in some improvements to Unity too. After the slightly lengthy download and install process, I was instructed to reboot the machine.

On reboot, instead of seeing the familiar GDM login screen, I get greeted with a black screen with only a "ubuntu login:" text prompt. Apparently the X server failed to start up properly. So I logged in and tried to start it manually with "startx". No dice, and it mentioned something about the Nvidia modules. It was then I knew what had happened: the kernel image and/or the nvidia modules didn't jive together. I then tried installing the nvidia-current package and then rebooted. Still didn't work. So I was left with one option: back up my data and re-install the stable Ubuntu release.

But I didn't have a CD/DVD with Ubuntu already on it. I had to first go to the Ubuntu website, download the ISO, and then burn it to disc all from the command-line.

Luckily, I still had access to the Web, could install packages via apt-get, and I knew my way around getting help in a gui-less situation. First, I installed elinks(a text-mode web browser) and rtorrent(a command-line bittorrent client). I launched elinks and navigated to the torrent download link. I saved the torrent file to my home directory, then launched rtorrent to quickly download the ISO.

The real tricky part for me was figuring out how to burn the ISO image via the command-line. After doing a little Googling, I found that the command "growisofs -dvd-compat -Z /dev/dvd=image.iso" fit the job perfectly. After the disc burn was complete, I rebooted and the live session started up without a hitch.

During the live session, I attempted to copy as much of my user data onto a pen drive as I could. Unfortunately, many of the files were somehow uncopiable(undoubtedly a permissions glitch). But whatever I couldn't backup wasn't anything irreplaceable, so it wasn't all too bad.

Then I launched the Ubuntu installer. The installer pretty much took me by surprise, as I recalled I never actually installed Maverick Meerkat fresh before(previously I had upgraded to it from the previous release, Lucid Lynx). The installer is now so polished I can confidently say it's idiot-proof.

Once the install was done, I rebooted and was greeted with an uber-fast bootup from manufacturer splash image to GDM in less than 15 seconds. I'm now still in the process of rebuilding all my lost user data, but I'm back in the game with a couple of golden nuggets of wisdom:
  1. Always regularly backup your stuff, because shit really does happen when you least expect it.
  2. When you're using early alpha software, shit happening is almost guaranteed. Be prepared for it.

However, this experience has compelled me to try a little experiment in the near future. I plan to dedicate at least 2 days of computer use solely within a command-line environment. No desktop environments, no window managers, and no GUI applications at all. Of course this means no SL or YouTube, but I'd like to see how far the command-line can be used to perform tasks usually reserved for a GUI environment. Look out for a future blog post on it.

Tuesday, December 7, 2010

Ubuntu Unity Desktop Review

A few days ago I decided to upgrade my desktop Ubuntu OS from 10.10(Maverick Meerkat) to 11.04(Natty Narwal) Alpha 1. Previous experience upgrading to such an early alpha release told me that this would be very risky and likely I would have to re-install back to the stable release. But after the lengthy upgrade process was completed(took a few hours because I had Gnome, KDE, and LXDE desktop environments previously installed), I successfully rebooted and was greeted with the familiar GDM login screen.

I clicked on my username, entered my password and chose "Ubuntu Desktop Edition" for the desktop session. But instead of Gnome or Unity popping up, it appeared that what I got was a very unfinished and incomplete desktop session. There was no launcher, no panel or even an easy logout mechanism. I was ready to dismiss Alpha 1 as a starting point only for the developers. FAIL.

But it turned out the Unity launcher and panel was present, but required desktop effects to be turned on to use them. So I did just that and this is what appeared:

Ubuntu Unity "Desktop"

Looks like a cross between Gnome Shell and Ubuntu's Netbook UI. What initially annoyed me was that all the entries I created in my Desktop directory were being shown twice: in the launcher and on the desktop screen. And notice the launcher entries displaying a question mark as the icon? That's because it seems the launcher can't display icons that are not stored on the system icon directories. I'd have to hover my mouse over the icons to tell what they really are. FAIL.

But the worst current feature of this release is finding all the applications. You have to click on the Ubuntu logo on the top left of the screen, and Nautilus will appear showing you the /usr/share/applications directory. Ugh. No application menu grouping or sorting by task at all here, just a single directory being spit out in front of you. FAIL.

As far as I can see, the current incarnation of the Unity desktop isn't even a true desktop environment yet. It's still a major work-in-progress, much like when KDE 4 first appeared. No doubt we'll see much improvement in future alpha releases, but for now I'll be sticking with Gnome/KDE/LXDE for my real desktop needs. Unity still needs a lot of work to be easy enough for casual use.

Monday, September 20, 2010

Linden Lab to TPV developers: No KDU for you!(Updated)

During the final months of the now-banned Emerald viewer, one of the major scandals that hastened its' demise was the emkdu library that Emerald used was hacked to send user info to Modular Systems without the knowledge or consent of the user. As a result of the discovery, Emerald was forced to remove emkdu.

In the aftermath of Emerald's demise, Linden Lab has made a few drastic changes. First and most important, they have changed the license of the official 2.x viewer from GPL to LGPL. Second, they are no longer going to release llkdu as a DLL. They will statically link llkdu into the viewer binaries. Third, they are playing copyright cops by threatening to delist, ban or block TPVs that use KDU code without obtaining a proper license(claiming it is a GPL violation).

Why is KDU important? Well, it's the code used to render textures in-world. The advantage KDU has is that it renders textures faster than the open source equivalent, openjpeg. However, KDU's speed advantage seems to be negligible on machines with modern graphics capabilities. So it makes a difference only on lower-end machines.

My personal opinion on it is this: There's only two proper solutions for TPV developers: either switch to a 2.x codebase and obtain a KDU license(not cheap, by the way), or obsolete KDU by modifying openjpeg to match or outperform KDU.

The former solution is apparently what LL is betting TPV developers will not do. They must think that they will simply fall back on stock openjpeg, and as a result virtually all TPVs will be "inferior" to their own viewer. It's clearly a power play by the Lab, once you look at the bigger picture.

However, Kakadu does not have a monopoly on JPEG decoding and rendering. TPV developers can either enhance openjpeg, or switch to another open source library such as JasPer(Google "open source jpeg2000 library" for more possibilities) and work with that. And as a form of protest against LL's power play, TPV developers should temporarily not contribute JPEG library changes back to LL. If LL wants the improvements, they'll have to go out and download them, just like TPV developers do to incorporate LL changes.

Update:  It seems that KDU, if by what folks on SLU are saying is true about KDU vs. openjpeg speed, then ultimately KDU is merely a crutch for older and low-end machines. So ultimately, the KDU problem may solve itself when SL users upgrade their lower-end machines.

Sunday, August 22, 2010

Fractured... OUT!!!(Updated 2x)

It seems Fractured Crystal has finally bitten off more than he can chew, and the entire Emerald gang may soon fork their viewer or call it quits.

What happened? Well, as of a few days ago, Emerald users were unknowingly being co-opted into becoming a part of a botnet designed to perform a DDoS(distributed denial of service) attack on the website of Hazim Gazov, a known distributor of a copybot client who has taken it upon himself to expose the "shenanigans" of the Emerald gang. Hazim quickly discovered what was going on and wasted no time bringing the crime into the public light. The news caught on like wildfire, and given the recent departure of LordGregGreg Back(he quit on ethical principles, believe it or not), the backlash is finally making Linden Lab consider outright banning Emerald.

What happens next is anybody's guess. If LL decides to ban Emerald, it's game over for all of them, including the devs who aren't total douchebags. If Emerald isn't banned, then most likely Emerald will fracture(pun intended) in two.

Either way, it's natural justice against Fractured and Phox. Good riddance to bad rubbish.

"I've got shit to do. I'm TP'ing out." - Fractured Crystal

Update:  Fractured has issued a mea culpa on the Modular Systems blog(jokingly titled "Off with his head"), where he announced he will be "voluntarily" leaving Emerald and hand over control of the project to Arabella Steadham. That still leaves Phox, Fractured's BFF in crime still hanging around, and who's to say Fractured won't simply rejoin the project under a new alt account? Even LordGregGreg has come out completely against using Emerald regardless of Fractured's departure, and started his own fork. Who do you trust?

Update 2:  The Lindens' first official action on the matter... Emerald is no longer listed in the TPV directory.

Sunday, August 8, 2010

MetaGridNet Revamp in progress

As I've previously announced here, I have created a small public OpenSim sandbox called MetaGridNet. It was originally created alongside an Elgg social networking installation. Unfortunately due to persistent spam on the site, I decided to nuke the server and start anew. The MetaGridNet sandbox is still operational, although I did do a fresh install using the latest OpenSim "Diva" distribution(I may set up a basic web site later on). The Diva install has brought with it a couple of new features and one in particular that was sorely needed: a built-in web-based user account creation and management framework(called "Wifi").

The benefit of this is immediate: Metaverse travelers can now easily set up a MetaGridNet account by going to the account registration page and login any third-party viewer(except Emerald because it's not optimized for OpenSim use) with the login URI "http://metagridnet.com:9000/". Or if you're already on a grid that uses Hypergrid protocol 1.5, you can perform a Hypergrid jump.

Stay tuned for further updates.

Victoriana triumphantly returns!

I had previously blogged about Victoriana and Tinytoriana, a Victorian-themed Second Life estate that had been forced to leave SL due to gigantic permissions screwups caused by Linden maintenance routines. The decision to leave and the resulting close-down caused a lot of sadness in SL residents.

However, I'm very happy to report that Victoriana is rising from the digital ashes over at InWorldz! I had found out about it this afternoon while in a group chat with fellow Raglanite tinies. After checking the map, I had teleported to Victoriana Square to take a brief look. Later on in the day after I got home from work, I had checked out Tinytoriana, a place made specifically for Victorian tinies. If there were any differences from when the estate was in SL, I couldn't notice them. So there's relatively little readjustments structurally, despite the fact that LittleBlackDuck Lindsay is still in the process of reconstructing the Victoriana estate.

Nevertheless, it's heartening to see this wonderful estate get a "second life" again, thanks to InWorldz and OpenSim.

P.S. - For a future post, I may try to get in touch with Mr. Lindsay to ask him some questions like why he decided to pick InWorldz, how he reconstructed his estate, what the future holds for his newly resurrected estate and more.

Monday, July 5, 2010

Guide to the Metaverse, Part 3: H-Town, A showcase grid

Continuing my trips to OpenSim grids, this morning I heard that the residential architecture company Hometta has opened their OpenSim interactive showcase grid, H-Town, to the general public. I had heard a lot of buzz about it recently and felt it was worth a visit, so I promptly registered. After registration I hit upon a stumbling block as the viewer offered for H-Town(a slightly customized Hippo viewer) was only for Windows and Macintosh. However, after a failed attempt to use Wine to run the Windows version of Hippo, I had found the instructions necessary to login with the regular Hippo viewer(on Linux).

Upon login, I landed at the Welcome Area, where there were several display signs that would take you to the house shown on the display. The grid itself, while technically small(only 3 regions), is well designed and certainly looks like a modern suburban neighbourhood in development. The houses already up are wonderfully built and are scripted to give visitors an interactive, hands-on experience. My personal favourite was the Draft House, and given that there's more houses coming soon, I'll be sure to make subsequent visits.

The Hometta folks have put a lot of effort into developing H-Town, and it shows. In my opinion, H-Town is a great example of utilizing OpenSim to showcase RL architecture to potential customers, and as a tool for architecture protoyping.

If you're into architecture or are looking to find a dream house to build, checking out H-Town is definitely worth a shot.

If you want to check out the other places where I've been, all of my "Guide to the Metaverse" posts are now tagged "metaverseguide".

Thursday, June 24, 2010

The Google vs. Viacom decision: How Virtual Worlds benefit from it

The big news just came out: Google has beaten Viacom on summary judgement. The case was about Viacom claiming that Google/YouTube knew that copyright infringement was happening on their site and was therefore exempt from the DMCA "Safe Harbor" provisions.

These two snippets from the decision sum up the reasons for the judgement perfectly:
General knowledge that infringement is 'ubiquitous' does not impose a duty on the service provider to monitor or search its service for infringements ... the burden is on the owner to identify the infringement

What Viacom was trying to do, in layman's terms, was attempt to force Google/YouTube into taking the burden of enforcing copyright beyond traditional copyright law and the DMCA. If Viacom prevailed, it would mean YouTube would have to review each and every video uploaded to their site and determine if the video infringes someone's copyright.

This decision is good news, not only for website operators, but also for virtual worlds. As an example of how virtual worlds could have been negatively affected if Google lost, one only needs to look at the long dead virtual world There.com.

There.com residents were split into two classes: consumers and content developers. To become a developer, you had to enroll in the developer program. When you create content, you can't simply start selling it on the spot(like with SL/OpenSim). You must submit the content to There.com's review staff. If the content doesn't pass the review for reasons such as inappropriate content or perceived copyright infringement, you can't sell or use the content inworld.

The problem with this approach is that the review staff weren't copyright owners or authorized agents of copyright owners. Yet they actively played "copyright cops" even in the absence of proper DMCA procedure. This, despite the approach successfully enticing RL companies into creating presences in There, actually endangered their ability to invoke the DMCA Safe Harbor provisions in court.

It's not hard to see that this sort of "copyright police state" scenario is very possible in SL and OpenSim grids, because SL/OpenSim's situation is practically identical to YouTube. Copyright infringements happen quite often in virtual worlds, but it's practically impossible for the grid operators to police the entire grid for copyright infringements. They would wind up dedicating all of their time taking down content they think is infringing someone's copyright instead of properly operating, running and improving the grid. It's an undue legal burden.

That's why the decision states that the burden is(rightfully) on the copyright owner, not the service provider, to identify(via DMCA notices) infringements. The service provider isn't liable to legal action unless they do not follow DMCA procedures. That's Safe Harbor in a nutshell, folks. Be thankful for it.

Update: Via one of my favourite YouTubers, Thunderf00t, I have found a jaw-dropping 18 minute video of Mike Mozart of JeepersMedia catching Viacom doing the exact same thing they accused Google/YouTube of doing. Using Viacom's logic, the YouTubers whose videos got uploaded to Spike.com without their permission could sue Viacom(not the "uploaders"). And since Spike.com(formerly iFilm.com) claimed to "screen all videos uploaded", they may lose Safe Harbor protections under the DMCA. So Viacom, maybe you should rethink filing an appeal, and be happy the judge ruled in Google's favor. You actually benefit from it, believe it or not.

Friday, June 4, 2010

Emerald vs Other 3rd-Party Viewers: Who Can You Trust?

Most of us know that the Emerald viewer is the most popular third-party viewer in Second Life today. Many of it's users will quickly tell you of its' dozens of features that put the official viewer to shame. But ask them this question and you will get some surprising answers: "Do you trust the Emerald developers?"

Those who quickly answer "Yes!" either haven't gotten enough information about them or are willfully ignorant of their shady histories. Those who answer "No" do know about the gang's griefing power plays, but think that there aren't any decent alternatives or "I can't live without Emerald feature X".

Whenever a person decides to switch away from the official viewer, trust in the developer(s) is a crucial factor. In this blog post, let's take a look at the Emerald developers and the Imprudence developers(the viewer that I use) and see how we can compare them in the context of trust.

Let's start off with the Imprudence developers(Jacek Antonelli, McCabe Maxsted and Armin Weatherwax). Okay, so they have a blog, a wiki, a forum, a source code repository, an issue tracker and a mailing list, for starters. So on the surface it's fairly professional. But wait, what do we see in the "Imprudence Links"? Ah, a privacy policy! Very nice. And also in the wiki we find out that the developers hold weekly public meetings(called ImpDev meetups) and publish full transcripts of the meetings. Bonus points on transparency. Another crucial factor is that all of the developers appear to have clean records in SL.

So it seems the Imprudence folks are on the up-and-up.

Now let's see how Emerald stacks up. Well, they seem to have the same basics as Imprudence(blog, wiki, source code repository, etc) and a privacy policy also, but let's dig deeper. Well, looks like the blog has completely disabled comments on all posts. They hold "office hours" but it appears the last thing even remotely resembling an office hour was posted Feb. 6th, 2010. Also, their latest "project" to be outed, Onyx, has gone from a public list of known malicious viewers to a page requiring a username and password to view. So that means they have chosen not to be transparent in the face of public scrutiny.

Then there's the illicit pasts of Fractured Crystal, and Phox/Lonely Bluebird. Fractured's history is that of a typical serial copybotter/griefer. Phox has been caught bragging about stealing stuff, loves to smoke weed, and claims to be able to have the ability to estate manage the entire SL grid. While the other Emerald members' pasts aren't entirely clear one way or the other, it's apparent they are complicit with Fractured and Phox's grid shenanigans.

So now I ask you folks: are all those blingy Emerald features really worth trusting a known copybotter, a kleptomaniac stoner, and a group who has the entire SL grid by the shorthairs(via Onyx)? Who can you really trust? how will you "weigh the scales"?

Update 6/20/2010: The Emerald gang has radically overhauled their ModularSystems site, restoring the comments feature. But all the old comments(and blog posts from April and earlier) are long since nuked, and now there is absolutely no mention of Onyx on the site(navigating to onyx.modularsystems.sl now yields a 404 error page). Oh, and the personal blogs of the gang on the site are gone as well.

Monday, May 31, 2010

Linden Prize Countdown: The Prokofy Factor

In about 24 hours from now(give or take), the winner of the Linden Prize will be announced. I await the announcement with not a sense of excitement, but actually with a sense of fear because there is a very real possibility that the Lindens will choose a finalist that frankly shouldn't have even made it past the gate.

Another reason why I'm dreading the announcement is that as of this point, the biggest chicken booster of them all, Prokofy Neva, has been pretty silent on the matter since the Linden blog post on the sionChickens where she vowed to "fight with every fiber of my being against those worldviews that seek to obliterate the normal, the ordinary, the simple, even the tacky, the mass-taste, the quick buck". Ugh.  I took this to mean that she'd come out swinging hard on her blog, doing everything she can to fight the good chicken fight and badmouth the actual deserving finalists more than she already has.


Her lack of commentary since the Linden blog post is unusual. It's just not like her to leave it alone when there's so much legitimate criticism of her beloved virtual fowl going even stronger now than before(over on SLUniverse, the Linden blog post on sionChickens got the most discussion of all the finalists).


So why the silence? Did she decide she's said all she needed to, and let things come as they may? Or has she somehow gotten the inside track on who will win the Prize? More likely the latter, but I suspect we won't find out until after the winner is announced tomorrow and Prok will inevitably make her own blog post either decrying or gushing over it.

Update: The winner has been announced, and it's not the chickens, thankfully. However as of yet there has been no reaction from Prok. Still, congrats to the Tech Virtual Museum Workshop. You guys deserved it.

Sunday, May 30, 2010

More on why Sion Chickens should not win the Linden Prize

As I had stated in my previous post on the fowlness surrounding the Linden Prize(pun intended), sion Chickens do not deserve to win the Linden Prize, much less be on the finalist shortlist simply because they do not meet the stated criteria.

But there's two more reasons why the inclusion of virtual fowl isn't kosher.

First, there's the humanitarian/charitable nature of the Prize itself. Over on Massively, Tateru Nino hits all the regular beats on the subject. In the comments, Maggie Darwin postulates that the Lab may claim the Prize as a charitable donation in their tax filings, and awarding the Prize to such an overtly successful for-profit, commercial operation may endanger that claim. However nobody beyond the Lab itself, its' partners and investors are privy to that sort of information and the Lab is under no obligation as a private company to divulge it to the public.

Then there's the very vicious actions of Sion himself. When one chicken farmer threatened legal action after Sion released a botched update that harmed many farmers' businesses, Sion actually made the thuggish threat of cutting off the food supply to all chicken farmers unless the criticising farmer backed off. Under pressure from fellow farmers, the critic sheepishly did so. Then to make sure no farmer would ever dare again speak out against the Fowl Empire, Sion crafted a new EULA which allowed him to cut off a farmer's chicken-use rights "for any reason or no reason at all" and even blacklist those who were seen as against Sion "for any reason or no reason at all".

Doesn't sound much like a humanitarian, charitable, or at least benevolent person, does it? Sounds more like the actions of a dictator, really.

So let me ask the folks at Linden Lab, if they happen to read this before June 1st: Why are you considering an entry that not only does not meet the criteria, but also whose proprietor has engaged in behaviour that is completely against the spirit of the Prize? Or do you simply not care about the legitimacy of what you publicly outline as a humanitarian prize?

Tuesday, May 25, 2010

Why Sion Chickens DO NOT deserve to win the Linden Prize

I wasn't going to blog about this, as so many other bloggers have roundly covered it. But then Prokofy Neva wrote this bogus piece on her opinion on why SionChickens should win the Linden Prize and all other finalists are unworthy.

She believes that SionChickens make RL better because it's a "socializing, fun, and a money-making opportunity on line". If this is her reasoning why SionChickens deserve to be on the same list as Virtual Helping Hands, then I propose that every in-world creator/merchant should be eligible, from Stroker Serpentine down to the prankster selling a plain 0.5m plywood cube on XStreet.

This flies right in the face of the what the Linden Prize is supposed to recognize: "an innovative inworld project that improves the way people work, learn and communicate in their daily lives outside of the virtual world". SionChickens have as much positive impact on the real world as Tamagotchi babies do on parenting: none. Just because Prok believes they have an impact doesn't prove anything.

Chicken fans, ask yourselves these questions: 1) Has buying, raising and selling virtual chickens improved the way you work in RL? 2) Has it improved how you learn in RL? and 3) Has it improved how you communicate in RL? If you answered "No, it hasn't" to all three questions then kindly explain in the comments why it should still be considered worthy of the Linden Prize, because I just don't get it.

Note: As of this writing, Sion Chickens is due up next to be profiled on the Linden Blog. Perhaps then we'll find out exactly what the f*** the Lindens were thinking including such an inappropriate entry as a finalist.

Update: The Linden blog post has been made, and it utterly and completely fails to convince why sionChickens are Linden Prize-worthy. Here's my comment to that blog post, if the Lindens decide to censor it:
I'm sorry, but this blog post does not explain in any form how sionChickens can be representative of an inworld project that has improved the way people work, learn, or communicate outside of the virtual world, as the Linden Prize page so clearly tells us.

In fact, it actually confirms the objections of many who believe sionChickens are not worthy of the Linden Prize.

The technologies used in sionChickens and sionCorn are no doubt innovative, but the purpose of the chickens isn't to teach how to use these technologies(If it were then breeders would be able to scientifically figure out how to optimize breeding and such). "Virtual World Tamagotchis" would be fairly descriptive of the purpose of sionChickens.

Monday, May 24, 2010

Guide to the Metaverse, Part 2

Continuing my travels to OpenSim-based virtual worlds, we come to two worlds that aren't for general use, but are very important nonetheless: Meta7 and ScienceSim.

Meta7 is a world showcasing an innovative technology called LightShare. LightShare allows region owners to share their WindLight environment settings with users via LSL script. Aside from LightShare, Meta 7 sadly doesn't offer much beyond most other OpenSim worlds. However LightShare alone makes it at least worth a look, especially if you're an OpenSim admin or a viewer developer looking to spice up your grid/viewer.

ScienceSim is for those who wish to use OpenSim for scientific and bleeding-edge research, simulation and education. The uber-geek's virtual world, if you will. If "Fern Lifecycle and Population Genetics Simulations" are your cup of tea, then ScienceSim is right up your alley. Just be sure to change your starter avatar's chin if you choose the male starter avatar(unless you're Jay Leno).

There may be a part 3 soon, but in the meantime I highly recommend taking a look at the grid list at Hyperica, as there's a heck of a lot more grids out there than I could realistically travel to.

Friday, April 23, 2010

The Axe Falls on Woodbury, thanks to... Emerald?!

The news about the massive banfest against Woodbury members has been getting major discussion over at SLUniverse and on Prok's blog, and it turns out what did them in was that they decided to grief the wrong griefers. Allegedly, Tizzy Teardrop put a bounty on taking down Emerald's beloved CDS, which got the ball rolling. But what most likely pushed the Emerald devs into throwing WU under the bus was the recent video made by Cam Scientist, a Woodbury member who publicly outed the fact that Fractured Crystal should not be anywhere near SL according to the TOS, starting from the first time he got an account banned and also that Onyx is a griefer/copybot viewer.

This, of course, embarrassed the Emerald devs and even put a few holes in their perceived reputation. So they obviously decided to offer up Woodbury as a condition(or leverage) to get on the third-party viewer directory. It's definitely no coincidence both events happened nearly on the same day.

My personal opinion on this is, "I don't really care". I have no sympathy whatsoever for the banned Woodbury griefers, and this doesn't change my opinion of the Emerald devs one bit. It's just a classic case of no honor amongst thieves.

Tuesday, April 20, 2010

The Second TPV developer brown-bag meeting: Wow, what a difference!

As noted in the previous blog post, the second brown-bag meeting between third-party viewer developers and Linden Lab has happened earlier today and from reading the transcripts, this time around it went way better. No griefing, sim crashing or voice problems, and the consensus is pretty much that the policy is much more agreeable as a whole.

What was discussed this time around is more "small stuff", like issues with the policy and content import and export. While Section 2(b) hasn't really changed at all, Joe Linden did recognize that there is a genuine need for extended metadata to help address legal uses of non-creator export, but the policy won't change until that happens. Fair enough, in my opinion. There are ways for creators of permissive content to get around it(host it outside of SL, collaborative builders can export their parts of builds and share it with their collaborators until the build is completed).

Also, Joe specifically wanted to address the Imprudence team about their plans to drop support for SL. This is a very positive sign for me personally, as I do prefer Imprudence not just for the viewer itself, but because I find the developer team to be very professional and upfront. It's also a positive sign for SL in general as well, as it shows the Lindens do not want to see a mass exodus of development support to OpenSim-based grids(although they have inadvertently strengthened OpenSim viewer support).

The only thing about the meeting that didn't change, sadly, was that again it seems no developers who are already listed in the TPV directory were in attendance. Maybe some of them didn't want to attend out of fear they would get the third degree, although it seems that given the policy changes it's just water under the bridge now and their input would be welcomed.

All in all, though, it's a 180% turnaround from last week's debacle and the first positive change I've seen from the Lab in a long while. I feel like doing a headbob:

The New Third-Party Viewer Policy: A Thing of Beauty and A Joy Forever

As noted in the previous blog post, the Lindens have quietly changed their third-party viewer policy. The changes, unlike the previous revision which amounted to nothing, address the majority of the issues raised by TPV developers and results in a more clear and simpler read for those who it's intended for.

The single biggest change is in Section 7(d), which now reads: "You assume all risks, expenses, and defects of any Third-Party Viewers that you use. Linden Lab shall not be responsible or liable for any Third-Party Viewers" Previously, the first sentence had ", develop or distribute" tacked on at the end, which put the sort of legal liability that LL themselves disclaim onto third-party developers. The new wording now makes it clear that was not the actual intent of the clause.

So with this change, for most legit TPV developers, there's nothing to fear from this policy anymore and it may even be totally okay to go for self-certification into the viewer directory(IANAL, of course, but that's my personal opinion).

There may be a few nagging issues left, such as Section 2(b) which restricts content export capability to creator-only. However, that merely applies to when on the SL grid. So it's possible to either simply have creators host permissive content outside of SL, or just have full-perm content export disabled only when on the SL grid. However for non-SL content exporting, I'd strongly recommend some sort of mechanism to convey usage beyond SL's crude C/M/T checkboxes.

Of course, certain folks who are against third-party viewers as a whole will be decrying the changes as "LL caving in to TPV developers" and "they're giving the store away to the copybotters". Reading through the policy, it's clear that's not what happened. The policy now more clearly delineates the difference between a compliant viewer and a malicious viewer(see Sections 2 and 7) and the enforcement terms(Section 8) have not changed(not counting the addition of 8(f), which merely makes clear the policy isn't intended to screw with the GPL).

Given these changes, I may not have to close down my store in SL after all. But I will continue with my current plan of opening up on other grids. It's a happy day for me :)

Update: BTW, the second brown-bag meeting has happened today. The transcript of the meeting can be found here(big thanks to Latha Serevi for the transcripts!).

Sunday, April 18, 2010

Updates on the Third-Party Viewer Policy debacle

Joe Linden recently hosted a brown-bag meeting for third-party developers to discuss the TPV policy. Unfortunately the meeting accomplished very little in terms of reconciliation or possible policy revision. This was due to griefers at the meeting teleporting around and crashing the sim(those griefers sadly being some of the people attending the meeting), and expected major problems with voice.

What was interesting about this meeting is that as far as I can tell there were absolutely no third-party developers in attendance who were listed in the Lindens' third-party viewer directory. That left Joe with virtually no solid support on his side. Also there were a few people there who weren't developers at all: Wut Moorlord of Woodbury/w-hat(a known griefer) and Angela Talamasca, who basically represents anti-open source folks like Prok. Then there's the shady trio of "ex-griefer" Emerald developers Discrete Dreamscape, Fractured Crystal and Lonely Bluebird. So with that unique blend of folks there, it's no wonder it came out a disaster for both sides.

What I took away from the meeting transcripts, however, is that the Emerald devs are going to do exactly what I theorized to several friends: that the Emerald developers are going to secretly negotiate a deal with the Lindens to become the only allowed general use third-party viewer on the directory(KirstenLee's viewer doesn't count as it's meant as a specialist viewer for photographers and machinima creators), with a side deal that Onyx(the copybot/griefer client the Emerald devs use amongst themselves) will be exempt from the policy, making it a Linden-blessed copybot/griefer client under the veil of "penetration testing for the Lab". Meanwhile all of the honest devs of general use third-party viewers will get bullied out of SL to appease the Lindens and their Emerald buddies. I have very little hope that the next meeting will be anything different or produce anything positive.

So in a nutshell, for general SL use it's either the still-craptacular Viewer 2.0, Snowglobe or risk your data and privacy with the Emerald devs in exchange for jiggle boobs, fancy selection beams and lag-inducing extra attachment points. Ugh.

Update: Regarding Emerald, Prok has a new blog post up which connects almost all of the dots about these folks who, in all honesty, should have been perma-banned from the first TOS/CS violation they committed(feel free to skip her usual open source=evil BS, of course). What Prok misses, however, is the connection between Onyx and Gemini CDS. Yes, CDS will ban all copybot viewers detected, except Onyx since it's an Emerald "project". Combined with the TPV policy going into effect, the Emerald devs can run roughshod over SL with no one the wiser, with only the above choices left for SL residents.

Update 2: Surprisingly, the Lindens have quietly amended the TPV policy. From what I'm reading of it, the changes are precisely what the TPV developer community asked for. I guess that blows apart the piece of my theory of Emerald colluding with Lindens to run all the other legit TPVs out of town. However that doesn't change the likelihood of CDS and Onyx collusion.

Saturday, April 10, 2010

Update on MetaGridNet

Just a quick update on the status of the MetaGridNet OpenSim grid. First off, a few days ago I had begun subdividing a part of the megaregion into 1024 meter parcels. These parcels will become the start of a rental program that I will be launching soon to help lessen the costs of hosting the grid and website. Once I figure out how rent payments will be done(most likely via PayPal) and create a decent covenant, I'll officially launch the rental program.

To get a MetaGridNet OpenSim account, you must contact me as per the instructions of this blog post.

Also, I will soon set up some freebies to help new users get started with building and scripting. So stay tuned, more good stuff is yet to come!

Saturday, April 3, 2010

Leaving Second Life and embracing OpenSim

Today I announced that my shop, NixTech, will be closing down on April 30th, 2010. The reasons behind it are related to the Third-Party Viewer Policy that will take effect on that day.

It's no secret that I prefer certain third-party viewers(Imprudence and Hippo, specifically) over the official LL viewer for many reasons(OpenSim support, content backup and restore, better performance, etc). Since many of the developers of third-party viewers have rejected the policy for several good reasons, after April 30th if I use any third-party viewer I run the risk of being banned.

Now, I could simply use the official Viewer 2.0, but to be honest it is a disaster of a viewer in comparison. It suffers from major slowdown, rezzes everything at a snail's pace and still consistently sucks up over 100% CPU use. It is absolutely not good enough for normal use, unless the Lab fixes these problems by April 30th(highly unlikely).

So as it stands, that means I won't be able to stay in Second Life for a long session(greater than a 1/2 hour) without suffering severe performance problems. This in turn affects my ability to run a shop in SL and offer support to my customers. Even my ability to merely socialize in-world will be adversely affected. So I decided to close it down on the 30th and convert the plot into my own residential spot(as I had it before I opened up NixTech). I will continue to have a presence in SL, but due to Viewer 2.0's volatility it will be a greatly diminished one.

However, this doesn't mean NixTech will be dead. I will continue to offer support to customers who have bought my items in-world or via META-life. I have already exported a good selection of my creations to my hard drive, and I plan to re-open NixTech in an OpenSim-based grid(most likely InWorldz) where legitimate third-party viewers are welcomed.

This was a decision not taken lightly. I've been a Second Life resident since 2006 and I've hung on through many events that have sent other people packing: the Linux client's sub-par quality before Tofu Linden fixed it up(no sound, no media, no shiny, not even copy/paste back then!), the gambling ban, the Lab pushing voice chat against the community's input, the OpenSpaces fiasco, and the XStreetSL freebies tax. This third-party viewer policy was simply the last straw and I can't just lie down and take it anymore.

See you all on the other side of the metaverse :)

Monday, March 29, 2010

How to access MetaGridNet sandbox via Hypergrid

As I noted in my previous announcement of the MetaGridNet social networking site and OpenSim sandbox, I had noted that it's possible to access the sandbox via Hypergrid teleporting. Here's how you can do it:


1. Download and install the Hippo OpenSim viewer. It's the only viewer that currently fully supports the Hypergrid technology(I did test with Imprudence, and it technically worked but it rendered the sandbox all botched up).

2. Log into OSGrid and teleport to a Hypergrid-enabled region such as Aesthetica.

3. When you get there, open up the map screen and enter this into the region box: "metagridnet.com:9000", then click Teleport.

Please note that for ReactionGrid users, to get to MetaGridNet you must first make a Hypergrid jump to a grid whose position coordinates are closer to MetaGridNet's(due to Hypergrid not being able to reach regions further than 4096 regions in a single jump on the map; thanks Maria!).

I do have a few rules for Hypergrid visits, though:

1. No griefing, harrassment or drama.

2. When you are done, please save your works, otherwise they may get deleted.

Otherwise, have fun!

Project Proposal: gnome-container-session

Technical Proposal: The gnome-container-session Project This document presents a formal proposal to the maintainers and developers of non-s...