How to remove Facebook’s new “Highlights” box

Count me among the countless many that have grown to despise the new Facebook layout. But rather than just pile on with a repetition of the same (and valid) complaints, I’m actually here to present a solution.

One of the common complaints I’ve heard—and one that I share—is around the pretty much brain-dead useless new “Highlights” box that now pollutes the sidebar on your Facebook home page. But if you’re not afraid to do just a tiny bit of hacking, you can get rid of this waste of space forever (or at least until Facebook changes their page code again, thus breaking this hack).

Note: This hack assumes you are using the Firefox browser and not, say, Internet Explorer (though why in god’s name are you still using IE?). You may be able to employ a similar hack for IE, but I do not have the first clue how to do this, and I have zero interest in finding out how, so you’re on your own.

1. Install Stylish.

Install the Stylish add-on for Firefox, and restart Firefox.

2. Create your Stylish user style.

In the lower right corner of the browser window (far right side of the status bar), click on the Stylish icon and select Manage Styles… In the resulting dialog box, click on the Write… button.

Now create the actual user style in the resulting dialog box. First, give your new Stylish user script a descriptive name (Hide The Annoying Facebook Highlights Piece Of Crap, perhaps). Then, paste the the following text into the main text area:

@namespace url(;

@-moz-document domain(″″) {
#home_sidebar > .UIHomeBox:first-child {display: none !important;}

Click Save button, and you’re done!

3. Enjoy!

Once you save this custom user style (it should be automatically enabled by default, so you shouldn’t have to do anything extra to enable it), the “Highlights” box should be gone from your sight, and only the “People You May Know” and “Connect With Friends” boxes should remain in the sidebar.

(If you’re so inclined, you can easily banish the entire sidebar—including those two remaining boxes—by editing the text in step 2 above and removing the > .UIHomeBox:first-child bit; save, and the whole sidebar’s now gone.)

This helpful slap upside Facebook’s head brought to you by the letter “P” and the number “4”.

Follow-up (Mar 31): Looks like Facebook has re-ordered the boxes in the sidebar, so the above won’t work as is any longer (the Highlights box is no longer the first box). So I’ve had to resort to the nuclear option—removing the entire sidebar per the last bit above. Sorry, Facebook, nothing personal. Wait, yes it is.

Follow-up (Nov 01): This tip is now obsolete, as the latest of Facebook’s seemingly infinite series of “improvements” has done away with the Highlights section entirely in favor of the equally annoying Live Feed / News Feed dichotomy. Haven’t found a way around that one yet.

Battlestar Galactica (2005–2009)

A very good episode to mark the end of the series. I’d stop just short of calling it great—the first hour was intense, most of the second hour just felt like a disjointed set of stories all duct-taped together, and the very end was fairly predictable—but this was as good a series ending as I’ve seen in awhile.

I’m going to miss the hell out of this show.

So say we all.

Need a podcast? Create your own!

Here’s the situation: At some point in the past, you subscribed to a podcast that’s now long since gone. You’ve already downloaded the podcast’s MP3 files for your enjoyment later on. And now you want to load all of the old MP3s as a podcast (as opposed to a normal playlist) in your iPod—doesn’t matter what the reason is, only that right now you’re determined to do it.

True story: My situation—and my motivation in the first place for what follows below—is slightly different. I had previously subscribed to a plain ol’ RSS feed for a foreign language site that allowed you to download MP3 tutorial files on a weekly basis, so I did. And I did this for a few months before I discovered that I had the option to subscribe to this site’s podcast as well, where the same files would be served up on a weekly basis. Only thing is that by the time I figured out there was a podcast, some of the earliest items had already rolled off the end of the podcast feed (which only serves up the last 10 articles) and were no longer available via the podcast itself, meaning my podcast subscription was now incomplete. However, since I had been faithfully downloading the files manually via the RSS feed, I actually had the raw content I needed—it just wasn’t part of the actual podcast feed any longer. I like to keep non-music podcasts separate from my normal iPod playlists—I’m funny/anal that way—hence my desire to find a hack to get around this, which led to this article. Phew.

What now? If you don’t want to just add the raw MP3 files into a normal playlist, you’re stuck, right? Aaaaaah, not necessarily…

If you can’t subscribe to a podcast that suits your need, why not just make one of your own that has exactly the items you want?

Please note that I don’t claim that what I describe below is the best or the most efficient solution, only that it works the way I want it to. I’m sure there are optimizations galore that you could make; I’m just sharing this here as-is in case it helps someone else.

1. Set up a local webserver.

Assuming you don’t want to put this up on an actual web hosting server, the first thing you’ll need to do is set up a local web server to host your local podcast files. Whether its on your local workstation or on a private web server on your home network makes no difference. For Windows machines, an easy-to-use option is WampServer, which bundles an Apache web server, MySQL, and PHP out of the box and is drop-dead simple to set up. (Another popular option is XAMPP.)

This tutorial assumes you’re using WampServer on your local PC, though it should be straightforward enough to figure out how to tweak this for a different network setup.

Note: Hosting your local podcast on your PC (and not on a separate web server on your home network) has a minor side effect; see Section 4 later on…

2. Locally populate your podcast MP3 files.

Now you need to put your MP3 files somewhere that the web server can find them. Chances are there’s a dedicated directory where your web server looks for files it’s expected to serve up; this location varies by web server (and is usually configurable by you during installation). For WampServer—assuming you installed WampServer to C:\WAMP and didn’t muck with the default config—this default location is C:\WAMP\www, so stick your MP3s there or, more probably, in some subdirectory under it (for this example, let’s make it C:\WAMP\www\podcast).

(optional) It may be that you’re like me and already have the MP3 files stored in some directory that is not part of your web server’s file directory. (For example, my files are tucked away in a subdirectory under my My Documents folder—let’s call it C:\Documents and Settings\xyz\My Documents\podcast for the sake of this discussion.) Instead of moving or copying them into your web server’s path, you can use the Junction utility to create a link to that directory from somewhere in your web server’s path. So, using my example, you can point C:\WAMP\www\podcast to point to C:\Documents and Settings\xyz\My Documents\podcast and never have to move a thing, and Windows will treat the former as being the same as the latter when accessing files—that is, C:\WAMP\www\podcast\foo.mp3 points to the exact same file as if you had used C:\Documents and Settings\xyz\My Documents\podcast\foo.mp3 instead. Quite cool, though this is old hat for those of you familiar with Unix symbolic links.

3. Create your local podcast feed.

This is really the part the makes it all happen—creating your local podcast feed. If you search around on the Googles, I’m sure you can find all manner of freeware, shareware, and/or commercial programs that will help you do this, but as I was starting at the ground floor, I wanted to get a better understanding of how the whole magic worked. So I created mine from scratch. In any case, all you’re doing is creating an XML file that contains all of the local MP3 files that you have and that you want to serve up as part of your local podcast.

No, I’m not going to go into step-by-step detail on how to do this; it’s straightforward and mechanical, but very tedious (if, of course, you do it by hand like I did). Anyway, it’s easy enough to find DIY instructions floating around the Intertubes; the tutorial I found to be the easiest to follow were the instructions found at podCast411 for creating your own XML podcast feed. (You can also read Apple’s technical specification for creating iTunes podcasts, but it’s more a reference than a tutorial.)

In the end, you wind up with an XML file that describes your podcast in all the necessary detail. Name the XML file whatever you want, and put it somewhere logical in your web server directory; continuing with my example, let’s call my file C:\WAMP\www\podcast\foo.xml.

This is the step that will undoubtedly take you the longest time, but once you finish it, you’re almost done…!

4. Subscribe to your local podcast.

Now you can actually (finally!) subscribe to your podcast. Follow whatever steps your player software (e.g., iTunes, Songbird) needs in order to subscribe to a podcast; for iTunes on Windows, this would be Advanced ––> Subscribe to Podcast…, then enter the local URL for your podcast feed. (Continuing my WampServer example, the XML file location I specified above would translate to a URL of http://localhost/podcast/foo.xml; your mileage may vary depending on your choice of web server, but it’ll be something like this in any case.)

And now your local podcast should show up and look like any other “real” podcast you subscribe to! Do a “Get All” (in iTunes, for example) for your new local feed, and voila!—all of the feed’s files are there for your enjoyment, just as if you had subscribed to a “real” podcast.

[Oh, about the gotcha mentioned up in step #1… If your web server is running on your local workstation—that is, the same computer where your player software (e.g., iTunes) resides, you’re likely going to end up with two identical copies of your MP3 files on your hard drive: one copy is the set of original MP3 files, the other copy is the set of files that iTunes (or whatever) pulls down as part of the podcast subscription and is stored in your player’s designated path for podcast files (for iTunes on Windows, this would be somewhere such as C:\Documents and Settings\xxx\My Documents\My Music\iTunes\iTunes Music\Podcasts\, for instance). Maybe a little annoying, but hopefully not that big a deal for you, especially with hard drive space being what it is these days (i.e., cheap). Anyway, just something to note in case it’s a big deal to you.]

5. Maintenance…

Depending on your circumstances, you’re either completely done at this point, or at most you have a little occasional maintenance to perform…

If you know that no more files need to be added to your local podcast from here on out, you’re done.

If, on the other hand, you occasionally need to add new files to your local podcast, all you need to do at each of those times is edit your podcast’s XML file to include your new MP3 file’s information, save it, then update your podcast subscription on your player software (iTunes on Windows: right-click on the podcast, then select Update Podcast). Get the new podcast item (if your player doesn’t do that automatically when you update a podcast subscription), and now you’re done, too. Lather, rinse, repeat each time you need to add a new item to your “subscription”—it’s really that easy.

Aside: In my case, I just pull the latest MP3 file off of the latest RSS feed item every week, then update my local podcast (per above) to account for the new file.

6. So is it worth all this trouble?

I can’t answer that for you. But it works for me, and it was a nice little educational experience as well. And if I ever decide to host a “real” podcast, I already know 99% of what I need to do having gone through this experience, so there’s that, too.

Anyway, as I said at the beginning, maybe this helps someone else out there. If so, glad to be of some service to you. And if not… well, thanks for reading all the way through, at least. :-)

You look familiar…

The Texas A&M men’s basketball team drew a #9 seed in the West region and will face #8-seeded BYU in a first-round game.

Wait, haven’t we done this before? Last year…

…the Texas A&M men’s basketball team drew a #9 seed in the West region and faced #8-seeded BYU in a first-round game.

With all the machinations of the NCAA tourney machine, this is one very strange outcome, but at least we’re in.

(By the way, A&M won last year’s matchup, 67-62, so here’s hoping the parallels continue…)

Putting a prettier face on war[gaming]

(Ed. note: First post in a month and a half, and 99% of you probably couldn’t care less about the new post’s topic. Can’t have everything, I guess.)

Back in the day (’80s, ’90s), I was pretty big into board wargaming. Now it’s 2009, and I’m getting back into wargaming, but this time of the computer variety.

One of my favorite games series right now is the Panzer Campaigns series from HPS Simulations. Some of the greatest situations of World War II, all based on a common game framework, making it very easy to go from one game in the series to another. Good historical detail, decent AI (important since I’m usually playing solo)…

…and some… well, really dated graphics. As in the graphics make it seem like I’m back in the ’80s, sitting at a table with my old SPI games. Still great games, don’t get me wrong, but when you see what others have done (for example, Matrix Games and their historically accurate and nice-to-look-at games), it makes you wonder if it’s necessary for HPS to sacrifice the eye candy completely.

Fortunately, third-party efforts are around that attempt—and quite successfully—to bring some new life to HPS’s games, graphically speaking. The two biggest (from what I can tell) and best (from what I’ve seen) are Volcano Mods and MapMod for Panzer Campaigns. Volcano Mods tackles the foreground—the unit counters and displays. MapMod tackles the background—the game maps themselves. Put them together (and they get along very, very nicely together), and the visual refresh is quite stunning.

Take, for example, the before and after (with both Volcano Mods and MapMod) for Bulge ’44, the HPS entry into the Battle of the Bulge:

HPS Simulations Bulge ’44

HPS Simulations Bulge ’44 (after Volcano Mods and MapMod)

Want to see some more? Let’s look at El Alamein ’42:

HPS Simulations El Alamein ’42

HPS Simulations El Alamein ’42 (after Volcano Mods and MapMod)

One more? OK, here’s Normandy ’44:

HPS Simulations Normandy ’44

HPS Simulations Normandy ’44 (after Volcano Mods and MapMod)

I love the updated unit counters from Volcano Mods. But I love love love how MapMod replaces non-unit counters with unobtrusive (but equally informative) map symbols—so now when you see a counter, it’s a unit counter and not just some map-related “noise” such as a trench or minefield or such. For board wargames, a counter is the only choice, but it’s nice to see MapMod taking advantage of the new medium.

Now if I could only find more time to actually play them…