First, you need to find your blog’s feed URL – it’s probably a link labeled something like “RSS” or “Atom” or “Feed” in the sidebar or at the bottom of each blog page. You’ll want the one that has just your posts – some blogging entries will have multiple feeds – for example, one that is just comments other people have made. Copy this URL – you’ll need it later.

Next, log into Facebook, and in the left hand navigation click on where it says “Notes” – you may have to click the “more” link to get it to show up:

Once your notes have loaded, in the right column where it says “Notes Settings”, click “Import a Blog >>”:

In the next screen, paste the feed URL into where it says “Web URL:”, click the checkbox (after reading the copyright warning of course) and then press “Start Importing”:

In a little bit, all the blog posts in your RSS feed should show up as Facebook Notes, with a link back to your blog. When you make a new post, it will be automatically added as soon as Facebook scrapes your RSS feed.

Asaph looks pretty cool as a way to quickly reference and quote other pages/images on the web. I’ve been feeling like I should add it or something like it to this blog to replace all these Tradenotes posts, as but most of what I do is links with commentary, similar to what Gruber does on Daring Fireball.

Look into my eyes. Still got your pocketbook?

An elephant paints an elephant. I wonder how long it took to train it to do that.

The Gloggomobil is a music box you can program yourself with little pegs. It’s too bad that it costs $1000+.

Men

• Just themselves: 9
• In a public situation with others: 3
• In formal wedding attire: 2
• With spouse: 2
• With pet: 1
• “Artistic rendition”: 1

Women

• With spouse: 2
• In formal wedding attire: 1
• In formal wedding attire with spouse: 1
• Just themselves: 1
• With pet: 1
• Obviously photoshopped: 1
• Landscape photo with nobody in it: 1

What I can gather from this is that if you’re male, you’re much more likely to put a picture of your manly bod or something that portrays you as being cool or social as your profile picture.

If you’re female, you’re likely to put up a picture that indicates that you’re “taken” (if that’s the case). On the whole the women put up more a more diverse, creative set of pictures.

This analysis is probably skewed by my particular data set, but it’s just interesting nonetheless.

Flash can and will crash your browser at times. Watch your CPU usage spike whenever you load a page with flash – by running someone’s crappy code, there goes your battery life. This is especially bad on some platforms (linux, PPC macs). I can only imagine it would be much worse on the iPhone.

Used sparingly and for certain things where it’s the only option (games, video) it’s fine.

Outside of that, flash breaks a whole lot of what is good about the web. It’s not searchable – text you may want to show up in a search engine dissappears into a black hole if your site is all-flash. This also causes problems with accessibility for the blind.

A few years ago, I bought into one of their buy-once-have-forever (aka VC) account. Eventually, they changed their servers from FreeBSD-based to Solaris-based, and I’ve been migrating a few of my hosts over.

A few little glitches ensued – for example, the hemingway theme I use in modified form on this blog uses short php start tags, and as a result breaks with an error like this:

PHP Parse error: syntax error, unexpected $end in /path/to/functions.php on line XX

To fix, in the PHP Configuration section, under Other Setting, you need to set Allow PHP scripts starting with <? to “yes”.

Additionally, if you want PHP logging to work a bit better, set the error_log variable in the php.ini file, to something like ~/domains/domain.name/logs/php_log .

Now, all I need to do is figure out how to rotate the PHP logs…

So… Charlie invites me to Facebook. Because I used a different email address to sign up, I had to re-invite him. Unfortunately:

…

Can you say defamation of character lawsuit?

Wordpress Patch from version 2.2.1 to 2.2.2

My first thought at looking at this screen was that if you click anything other than the yellow “Accept” button, you may end up being proselytized to.

(Apologies to Christopher, whose name facilitiated this unfortunate truncation)

When you start upgrading multiple blogs, you’ll soon realize that the standard process of updating Wordpress is time consuming, and requires a lot of manual intervention, so here’s a way to automate it using two standard unix tools, diff and patch.
diff finds all the differences between two files and folders, whereas patch takes the output of diff and makes the changes described in the patch file to the files and folders it is run on.

This example goes from Wordpress 2.2 to Wordpress 2.2.1, but should work for any combination of releases. This won’t update any of your themes and plugins, and you should definitely make a backup before doing it – don’t blame me if you completely screw up your installation!

Step 1

Obtain copies of both versions of Wordpress you’re going to be using from the Release Archive, and decompress them into two folders (we’ll call these wordpress22 and wordpress221, in this example)

Step 2

Run diff on the directories to generate a patch file.

diff -Naur -x .DS_Store wordpress22 wordpress221 > wp22_221.patch

(The -x .DS_Store argument is only needed on the Mac, which stores directory information in that file. The other options make the diff unified, recurse through the directories, make it ascii, etc. – read the diff’s man page for more information)

Step 3

Apply the patch you created in step 2 using patch. cd into the directory, and run the patch command:

patch -p 1 < /path/to/wp22_221.patch

You will get a lot of output like this:

...
patching file wp-admin/edit-form-advanced.php
patching file wp-admin/edit-form-comment.php
patching file wp-admin/edit-form.php
patching file wp-admin/edit-page-form.php
patching file wp-admin/export.php
patching file wp-admin/install.php
patching file wp-admin/user-edit.php
patching file wp-admin/users.php
patching file wp-admin/widgets.css
patching file wp-admin/widgets.php
...

If there any errors, you'll see them during the patch process.

At this point, you're done. You can use the patch file you created on any Wordpress weblog that you want to bring from version 2.2 to 2.2.1, but it won't work for other versions.

“This year’s White House greeting card extends ‘best wishes for a holiday season of hope and happiness.’ No mention of ‘Merry Christmas’ from the First Family.”

Oh, and what’s on the commander and chief’s iPod?

Gmail on your cell phone

Here’s a spreasheet of operational satellites currently in orbit around the Earth.

We went to Bianchi’s (Speedway/Silverbell) last Sunday – it’s good, cheap italian food, and they give you a ton, if you’re looking for a place around here to eat.

Chwang Yi – for all the peripherals the now defunct MacMice used to make.

You can now get Rush Limbaugh, on your video iPod – (man, the last time I heard Rush was when I was in middle school and still young and impressionable)

Go grab Mozilla 1.5 if you haven’t already. You’ll be glad you did.

Web Developers Handbook

It’s quite comprehensive.

(Found via the CSS Weblog.)