One of the latest things I've been working on at Mahalo is Mahalo Share. It's a utility that automatically posts links that you want to share to 11 different services: del.icio.us, Facebook, Twitter, Jaiku, your Tumblr blog, Ma.gnolia, Faves, Pownce, Mahalo, StumbleUpon, and/or Google Bookmarks.

All of this cross-posting is done behind the scenes using various APIs, so there aren't additional popup windows to fill out for each service. We'll be adding more services as they're requested.

I've updated Facebook Scavenger (a Firefox extension that saves a backup your Facebook friends' profile data) to add vCard export support. You can download this new version (1.1) from the Facebok Scavenger homepage, and you might want to hurry. A little birdie told me that this handy tool might not be available for too much longer.

Earlier today, I mentioned that it wouldn't be out of the question to write a Firefox extension that would grab profile data about your Facebook friends as you view their profiles so that you could take that data to another service.

Given that, allow me to introduce Facebook Scavenger. It's a Firefox extension that saves data (including e-mail addresses) from Facebook profiles that you view and then allows you to export that data in CSV format.

Note that this extension does not violate Facebook's TOS since it does not automatically load pages to retrieve profile data; rather, it reformats data that you have already seen on pages that you yourself loaded. Robert Scoble could have saved himself a lot of trouble (and avoided a lot of that nasty publicity that I'm sure he hates ;-) had he just used this extension for a few days.

A while back I mentioned that Facebook Image-to-Email (a Firefox extension that converts Facebook's e-mail address images to plain-text) was broken after some unknown change was made by Facebook. I am happy to announce that it is working again, after I re-tooled it with a different method for accessing the image data of those e-mail address images.

You can download this new release from the Facebook Image-to-Email homepage. If you don't care to know more about the technical details, stop reading now.

Technical wrap-up: In previous versions, I was injecting JavaScript into the document and doing all of the processing of the images there. This is a pain, but because webpage JavaScript is not allowed to access the data of images from a different domain (and JavaScript running in the chrome couldn't seem to do it either), there wasn't much choice. At some point, Facebook made a change to their pages or the server that their images come from, and this method of parsing the images broke.

What I've done is this: instead of accessing the images directly, the extension now takes a screenshot of the entire page (allowed under the browser's security policies), locates the portions of the page that contain the e-mail address images, and parses them out entirely from the browser's chrome, a beautiful place with much looser security restrictions than a webpage. (I've also added character maps for "-" (hyphen) and the "r." sequence that wasn't being parsed properly.)

(Sidenote with relevance to current events: this extension is now a hop, skip, and a jump away from being able to be used to parse and download all of your friends' information, including e-mail addresses. If Scoble had only waited, he could have avoided this whole mess.)

I am aware that the Facebook Image-to-Email Firefox extension is (once again) broken, and given that version 1.1 installed on Firefox 2.0.0.8 was working, and now version 1.1 installed on Firefox 2.0.0.8 is not working, it has to be due to a change that Facebook made. The problem is that I can't discern any relevant changes in Facebook's profile pages that would cause a problem.

The crux is this: I'm getting an NS_ERROR_DOM_SECURITY_ERR error when trying to run context.getImageData(). From what I've read, this implies that the JavaScript is not in the same domain as the image that was fed into the canvas and/or does not have permission to know the image's contents, but as far as I can tell, Facebook didn't change where the e-mail images are coming from, so that would seem to be a strange problem to have.

Any insight into this is appreciated.