Personas Interactive 1.2 with TweetTheme

I'm excited about the new version of Personas Interactive that Brand Thunder just released.

If you don't know, Personas Interactive builds on the Personas features in Firefox adding in things like multiple background images, Personas specific toolbars, galleries that can be hosted on any site and more. It removes the limitations of Personas.

This new version gives the user more control, including adding social network buttons to every theme and weather customized to your location.

But the coolest thing in it is support for our new TweetTheme. Combined with PI 1.2, TweetTheme gives you a full Twitter experience in your browser, including Twitter in sidebar, tweeting and searching Twitter from your toolbar, as well as a viewer that shows your last twenty tweets. It really shows off the power of Personas Interactive. I hope you'll try it out.

You can click here to install Personas Interactive with TweetTheme.

And you won't believe what Brand Thunder has coming up next. BT:Engage lets you build your own themes that will work with Personas Interactive. You can try it out now!

Firefox 4 Doesn't Recognize New Thawte Code Signing Cert

We just got a new code signing cert from Thawte and after getting it installed, I discovered that Firefox 4 would still show "Author not verified" when installing the XPI. After doing some research, I found this bug - Turn on the code signing trust bit for the Thawte Primary Root CA. It has some information on a workaround, but it wasn't very detailed so I thought I would post it for everyone.

Here's what I did:

Per the Thawte instructions, I use on IE on Windows to manage my certs. After importing my new cert into IE, the first step was to export it. Important: When you export the PFX file do NOT check the box to include all the certificates in the certification path.

Next, I created a new cert database using: certutil -N -d .

Then I imported my cert using pk12util: pk12util -i {filename}.pfx -d

Thawte has created a new intermediate cert to work around this problem. It can be downloaded here.

You need to download it and import it into your database using this command:

certutil -t "c,c,C" -n "thawte" -A -d .< new_thawte.cer

You should now be able to sign your XPI.

One other thing I ran into was finding a version of NSS that worked properly. I ended up using this one.

Great American Garage Sale

Recently I was reading an article about how the US government was suing an Apollo 14 astronaut to recover a camera that he was trying to auction. Apparently they want it back. I'm guessing what they're going to do with it is simply put it in some warehouse like they do with everything else.

It occurred to me that the government has TONS of stuff that they could probably sell to get us out of debt. Why is the government holding on to tons of crap when they could just sell it?

When families need to get out of debt. They sell stuff. They have garage sales or sell stuff on craigslist and eBay. So why can't the government?

So here are some ideas:

  • The Smithsonian has millions of artifacts that aren't even on display. Sell them!
  • Instead of putting all the Space Shuttles in museums, take one apart. Sell the tiles. People would pay thousands of dollars for Space Shuttle souvenirs.
  • Clean out all the old junk at NASA and sell it.
  • Does the Library of Congress really need all those books? Sell some.

Wouldn't it be great on the next Independence Day for the government to be financially independent?

Can you think of any other junk the government has that it could sell?

Creating a Universal updateURL

In the discussion of the Firefox rapid release process, one of the complaints has been that add-ons that are not hosted on addons.mozilla.org (AMO) don't get automatically bumped to be current with the latest Firefox. I needed to solve this problem for one of my clients, and here's what I came up with.

Why Do Companies Need Time to Deploy Browsers?

To be clear, I mean browsers that have some level of change to them BESIDES JUST SECURITY FIXES. When it comes to security fixes, I've seen companies deploy those changes immediately.

Throughout the discussion on my previous post, the focus has been on web applications and web compatibility. I thought I'd take some time to bring up all the other issues that go around deploying browsers in an organization.

There was a statement in John Walicki's comment that was missed by most:

Education programs, documentation updates, communications all are planned.

While these changes were between Firefox 3.6 and Firefox 4 which contained major visual updates, there is no promise that these "minor updates" won't include these kind of changes as well. And these changes require all of the internal documentation to be updated as well.

IBM has hundreds of support documents, including walk throughs, screen captures, webcasts, etc. that all reference the user interface of the browser. Every single one of these had to be redone for Firefox 4 (and probably done twice because Mac and Windows Firefox are so different now). And with the new release process, changes like these could happen with as little as 7 weeks to remedy the situation.

There's also the issue of training. As I said in my last post, many companies that use these browsers are NOT technology companies. So the assumption that users will figure out how to use the browser when it changes are simply wrong. When people see things they haven't seen before, or things don't work like they did before, they call support.

Repacking for deployment takes time as well. Most companies would not want an outside entity like Mozilla to deploy software to their machines. So they have to package and certify the application. A lot of changes are also staged, so just because the browser was released on a certain date doesn't mean it will make it down to the user's machine immediately.

There are probably lots of other issues that companies run into in trying to deploy software every six weeks. I'll leave that to other folks to talk about in the comments.

CCK Wizard for Firefox 5

I've updated the CCK Wizard for Firefox 5 and placed it here.

The main change is that you can now explicitly specify the Firefox min and maxVersion when you create your XPI. It defaults to * for maxVersion so it will work on all future versions of Firefox.