«
»

Facebook Purity – New Release – v2.3 – Fixes + Improvements



Facebook Purity is a greasemonkey script that cleans the crap off your facebook homepage, leaving behind a more uncluttered viewing experience.

Ive just released a new script update, here are the Facebook Purity v2.3 Release Notes :

  • speeded up script loading time by checking if the DOM is ready, rather than waiting for the whole page to load
  • fixed the “block app” function for google chrome v4 + hopefully fixed the random script loading problems too
  • added “attended event” messages to blocked extras list
  • added a new “Extra” option to allow blocking of “commented on status” and “likes status” messages ( see http://extras.fbpurity.com for info on how to enable this)
  • added the palm facebook application to the default application whitelist

You can get the updated version of the script here: http://www.fbpurity.com

N.B If you have previously made changes to the scripts Extras blacklist or Application Whitelist, you should make sure you keep a copy of the lists, so you can apply the lists to the new version of the script.

Also, before re-installing, you might need to clear your browser cache. Google Chrome v4 users will need to uninstall the old version (via the extensions menu), clear your browser cache, then reinstall.

Related posts:

  1. Fluff Busting Purity removes annoying quiz messages and application spam from your Facebook Homepage
  2. Facebook Purity – New Release : v2.5 – I’ve Added a custom text filter
  3. Facebook Purity – Now even easier to install in Google Chrome v4
  4. FB Purity Script Updated v3.9.2 : the hide sponsored box option now works on user profiles and facebook pages
  5. FB Purity v6.0.0 Released : FireFox extension is now restartless – Adds “read article” filter + more fixes and tweaks

This entry was posted on Sunday, January 31st, 2010 at 2:04 PM and is filed under facebook, facebook purity, firefox, google chrome, google chrome extensions, greasemonkey, programming, technology. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

Comments are closed.