Many users consider this a further violation of privacy, and choose to delete these posts manually by clicking the "x" on each one, then confirming in the popup dialog. This is cumbersome!

Better Facebook fixes this for you. It adds a single link to each block of "recent activity" posts that will remove all the posts for you in one click.

Ah, much easier!

UPDATE!  (Dec 15): I have improved this even more since the original release, and now it works even more consistently in the BETA version of Better Facebook: http://BetterFacebook.net/beta/4.502/

Also in this version is an option in Options->Advanced to automatically remove recent activity posts. If you enable this, then visit your profile, any recent activity posts found will automatically be removed. You will be informed of any removal in a little message box in the upper right. It couldn’t be an easier than that! Keep your activity private!

Download Better Facebook from http://BetterFacebook.net

Although many like the new layout, one side-effect has been noticed by most: The new profile layout encourages users to update their personal information. And as your friends do this, your stream may become littered with stories about their changes to their home town, likes, sports, etc.

Luckily you can easily filter all those stories out of your feed by using the Better Facebook browser add-on from http://BetterFacebook.net . Using Better Facebook, you can setup a Feed Filter like this:

This will cause all of these stories about information changes to be hidden from your stream, and you can get back to an uncluttered stream of posts from your friends.

Enjoy!

http://BetterFacebook.net

Each displayable character has a numeric representation. ASCII defines the common characters, where A=65 and z=122 for example. Most character sets use values 128-255 to store their own characters such as non-English characters and punctuation. These character sets are still compatible with ASCII because they maintain the same character maps as those defined by ASCII.

Unicode is a standard that defines a huge range of printable characters across many languages. UTF-8 is a variable-length character encoding for Unicode that is backwards-compatible with ASCII. All ASCII characters are stored as their single-byte representation. Other characters are stored in 1-4 bytes. UTF-8 is the preferred character set internationally because it supports all characters and because it is backwards-compatible.

ISO-8859-1 (Latin-1) is a single-byte non-Unicode character set that defines characters 128-159 as undisplayable control characters, and lacks important characters like Euro.

windows-1252 is identical to ISO-8859-1, but it takes the range of control characters (128-159) and replaces it with useful, displayable special characters like Euro (128) and smart quotes (often used in apps like Microsoft Word). A single closing smart quote, for example, is character 146.

When browsers receive a page that says it is encoded in ISO-8859-1, they treat it as windows-1252 because in most cases it really is. This way it can display these extended characters correctly, even when the encoding is incorrectly identified as ISO-8859-1.

This special handling is so useful and common that it is actually required in draft versions of HTML5.

Browsers will submit content with the same encoding as what the page is displayed in. If content is pasted into the browser from an external app, it will convert it to the appropriate character set before submitting. It is important to always send the correct character encoding to the browser so it knows how to display it, as well as convert pasted text and submit.

When sending an AJAX request, IE will always ignore the encoding on the page and send in UTF-8 instead. There is no way to override this. When handling AJAX responses, it will default to treating the content as UTF-8 unless it is explicitly stated otherwise.

Web servers treat URL’s themselves and request bodies as ISO-8859-1 by default if no encoding is specified by the browser.

URL’s are defined to be ASCII only. If non-ASCII characters are to be sent in a URL, they must be encoded using %FF hex syntax. A windows-1252 closing smart quote character with code 146 will be sent in an encoded url as %92 from a normal submit on a page encoded in windows-1252, but will be sent as %E2%80%99 (UTF-8) if the URL is constructed via encodeURIComponent and sent via AJAX. There is no requirement about what encoding this character represents, so it is important for the browser to send the correct encoding type in the request headers.

If a GET request is received via AJAX, the parameter values will actually be encoded as UTF-8 (when encodeURIComponent is used), but the web browser treats the URL as ISO-8859-1, and encoded characters do not get mapped correctly. The web server needs to be told explicitly to treat incoming URL’s as UTF-8. The Content-type header in the request does not apply to the type of characters in the URL itself.
In Tomcat’s server.xml, for example:

<Connector port="8080" URIEncoding="UTF-8"/>

This way, Java will not attempt to incorrectly translate URL parameters from ISO-8859-1 to UTF-8, since they are treated as already being in UTF-8.
You can also make the encoding dynamic by using:

<Connector port=”8080” useBodyEncodingForURI=”true”/>

This will cause Tomcat to use the encoding sent by the browser instead.

It is highly recommend that, when possible, UTF-8 be used in every layer. This avoids any transcoding problems and confusion and it supported correctly in IE whether you’re using AJAX or not.

Character sets have different names in different environments, such as Sybase. Aliases:
ISO-8859-1 = iso_1 = cp850
windows-1252 = cp1252
UTF-8 = utf8
Depending on your environment, you may need to use a specific version of the character set name.

Useful References:

http://en.wikipedia.org/wiki/ISO/IEC_8859-1
http://en.wikipedia.org/wiki/Windows-1252
http://en.wikipedia.org/wiki/UTF-8
http://wiki.apache.org/tomcat/FAQ/CharacterEncoding
http://groups.google.com/group/comp.lang.javascript/browse_frm/thread/fd96823cbcd0c126/ca1d033bf8c8aea2

With the latest version of Better Facebook, you can thankfully undo both of these changes!

First, download Better Facebook for your browser by going to http://BetterFacebook.net

Then, make two changes:

1. In Options->Popular (the first tab), enter "13" as the value for the last option – Force post font size to be __px. This will restore the font size.
   
2. In Options->CSS enter this text into the big box:

.actorName{ display:inline; margin-right:3px; padding-bottom:0px !important; }

Click Save and refresh Facebook. You’ll be back to the layout you had before. Enjoy!

But after the update, the selector was hidden in a dropdown under a checkbox on the left. Very inconvenient!

So, Greasemonkey to the rescue again!  I wrote this Greasemonkey script: Gmail – Restore "Select" line including "Unread" link

This will add the "Select" line in and bring back one-click access to message selection, like this:

Enjoy

On July 28 2010, Apple officially released a new version of Safari, and along with it the Extension Gallery. A few weeks before the release, I received an email from Apple requesting that developers submit their extensions for consideration to be included in the gallery when it was released. I was happy that Better Facebook, my browser/script extension that I have been working on for almost a year, worked great in Safari and that I had previously figured out how to package an official Safari Extension. So I filled out the form and submitted Better Facebook to the gallery.

On the morning of July 28, I got an Google Alert email with a new match for the term "Better Facebook" (I am a self-stalker!). It pointed me to the Safari Extension Gallery, and I knew that I could expect a bump in traffic for the day.

Thankfully, Better Facebook is prominently featured in the gallery, near the top of the listings, and the first extension to be listed in the "Social Networking" category:

Impact On Site Traffic

Previously, my site got around 1,000 hits a day – sometimes more, which I was always pretty happy with. But you can see the history compared to July 28!

Looking closer at just the one day of traffic, I found that I got over 16,000 hits to the site itself!

Looking at the referers, I found that over 10,000 of those hits came directly from the Safari Extension Gallery:

I was happy to see that Better Facebook was mentioned in other stories about the Extension Gallery also, including ZDNet and Lifehacker.

I haven’t totaled up the number of actual downloads yet, but I did exceed my bandwidth limitations yesterday. I might need to increase my hosting capabilities if this continues.

Impact On Facebook Page

Better Facebook also has an official Page on Facebook, and the impact on the number of people who "Like" it was dramatic!

The history of "Likes" of the page looks like this:

A slow, steady growth pattern to what I considered to be a pretty impressive number – 8,500 fans before July 28th. But on the day itself, I saw an impressive growth of almost 2,000 new fans! That put the page over 10,000 fans, which is a number that many companies and pages would envy. As I write this, the page stands at 10,691 fans and it just keeps going up. It will be interesting to see the historical graph once it is updated in Facebook Insights.

Conclusion

I have put many hours of work into Better Facebook, and I’ve been happy to see it grow and its popularity slowly increase. I find it incredibly useful for myself, and most users seem enthusiastic about what it does also. The problem has always been how to get it to "explode" and really take off and find a wider userbase. Being listed in the Extension Gallery has finally been the spark that made this happen, and I’m very happy about it! It’s a fun, interesting experience and I get to learn a lot from it. It helps me create better software and learn new ways to share information and interact with users in the social space. I’m grateful for the exposure, and humbled by the positive reactions of thousands of users.

Now… can I somehow profit a little from this? Heh. We’ll see…

Finally, I found the root cause and solution.

The problem was unicode strings being passed into JSON.stringify(). This sometimes resulted in an invalid JSON structure, which then failed when passed to JSON.parse(). The root cause was not within my code, but within the Greasemonkey User Script Compiler that I used to create the Add-on.

The problem was that the script was not being read in using UTF-8, so when executed it didn’t properly handle UTF-8. In the script-compiler.js file, line 22 (for me) I found this:

var channel=ioService.newChannel(aUrl, null, null);

I simply had to change the line to this instead:

var channel=ioService.newChannel(aUrl, "UTF-8", null);

I re-packaged the add-on and the problem disappeared! Hopefully it anyone else runs into this, a quick Google search will find this page. In all my searching, I hadn’t come across anyone else talking about this specific issue. But solving a very needle-in-a-haystack problem is very rewarding, and I’ll be glad to stop getting error reports!

The script has been updated to work with the new Facebook layout, and also now supports Chrome!

Check out the site and the script. I hope you find it useful!

BetterFacebook.net

This is just a re-packaging of my Better Facebook Greasemonkey Script that does the same thing.

The functionality includes:

• Mark your Live Feed as "read" so old posts are hidden by default. Quickly and easily only see new posts
• If new comments are found on old posts, they will be shown and highlighted for you
• Hide or minimize by story type. For example, stop seeing all notifications about who your friends became friends with!
• Pin the notifications panel to the upper right, so it is always easily visible
• Track your friends, and if someone unfriends you it will automatically tell you who it was!

This script and add-on will continue to improve as I add more features. Enjoy!

Better Facebook Firefox Add-On