Tuesday, April 26, 2011

Let your Chatter Profile be Free!

The results are in for our Chatter Profile "Jailbreak" challenge and while we had a large number of submissions, I am only going to outline the top three.

When we originally posted the challenge we weren't even sure it was possible to meet the requirements. However, once again the crowd proves how #superfreakinawesome it is! It was amazing how each person took a different approach to the problem.

kyleisidorey took an interesting approach to the challenge. He wrote a Google Chrome extension that overrode the entire Chatter profile page with a custom Visualforce page and controller which gives you the freedom to display whatever you want on the page.

Kenji776 went an interesting route and implemented a Force.com Sites Visualforce page and controller that injected JSON content into a user's Chatter profile page. It therefore kept the existing Chatter functionality but allows additional markup to be inserted.

But the winner was fractastical with, once again, a very elegant jQuery approach. Here's the video that he submitted with his code:

Unable to display content. Adobe Flash is required.

So the final roundup for the challenge is:
  1. Fractastical
  2. Kenji776
  3. kyleisidorey
Congrats to everyone who participated!


  1. Good competition, fun to see the results of everyone's creativity!

  2. Kenji776 here. Nice job everyone. That was a lot of fun. Looking forward to the next one!

  3. All are tweakers .. really grt job guys

  4. Really like Fractastical's solution - since the code is MIT licensed, I thought the result would be posted for all to use. I have looked all over the place on this site, but I can't find it. Could someone please aim me in the right direction? Thanks.

  5. Here is a link to the github for that contest: https://github.com/cloudspokes/chatter-profile-jailbreak

    Also a link to all of our opensource code:http://blog.cloudspokes.com/search?q=open+source

  6. This no longer works, are salesforce blocking the javascript?

  7. Sorry but we are no longer supporting this challenge's code.