Android Central – Part of The Smartphone Experts network, the same folks who run CrackBerry.com, which was one of my favorite Blackberry blogs, and The iPhone Blog. Like several of these blogs, Android Central also runs a store with accessories.

AndroidSPIN – AndroidSPIN appeals to the slightly more technical user, with more coverage of the latest unofficial Android ROMs.

Android and Me - This blog easily wins the Android blog beauty contest, both for its main site and its mobile site. In addition to news, they seem to have a good proportion of original content, such as app reviews and a great tutorial on making your Wordpress blog more iPhone and Android friendly (something I hope to do soon!)

Droid Life – This is definitely the oddball of my list. It’s much less polished than the rest, and focuses exclusively on the Motorola Droid. Despite it being a little less robust than the larger sites, this one has lots of excellent Droid-specific content like the Android 2.1 apps (with multi-touch) that have been ported to the Droid. It can get a bit technical at times, with information on “rooting” and so on, but still a useful site to have in my RSS reader.

I also keep an eye on Android-related posts at Lifehacker (one of my favorite blogs in general) and occasionally browse the Android-tagged posts on Engadget.

Any other Android users out there have favorite blogs (or other Android sites) you frequent? Any you’ve found completely useless? I’d love to hear about them in the comments.

Last Friday my wife and I received our new Droids, and after using it pretty intensely over the weekend, these are some of my overall impressions. I won’t even attempt at making this post exhaustive – instead I’ll try and post some follow-ups on things like what apps I’ve found useful (or not) and so on.

I must say that I wasn’t initially sold on getting a Droid – the Google Nexus One is supposed to be coming to Verizon sometime this Spring, and knowing that it has more memory, faster processor, a newer version of Android, etc. I was very tempted to just wait. However, just as decision-time was looming reports started to emerge that the Droid would soon be upgraded to the same, newer version of Android (2.1). Also, the Nexus One has definitely had its share of issues for early-adopters, so ultimately I decided to go with the slightly older but seemingly more reliable Droid.

Initial Setup

Setup was relatively painless for me, already having had a Google account. I had sync’d all of my contacts from my old Blackberry to my Google account using Google Sync, and I had already “cleaned up” my address books in anticipation of importing them to the new phone. You may notice I referred to address books. That’s because I’m taking advantage of one of the key features of Android 2.0 or newer, the ability to connect with multiple Google accounts.

I use Gmail for both my personal and work email, calendar, etc. but with separate accounts. Initially, I was worried about how this would go – would I end up with many duplicate contacts because some people appear in both contacts lists? Would I be able to specify where new contacts are saved when I create them on the phone? How would calendars work?

All my fears were laid to rest as I set up the phone, first with my personal account, then adding my work one. Android does a great job of combining duplicate contacts while still allowing you to un-join them if it makes a mistake or if you want them to remain distinct. When you start to add a new contact, it immediately asks which account to create it under.

One slight disappointment is that the calendar only syncs with the primary account on the phone, my personal account in my case. However, since I had already set up calendar sharing between my work and personal accounts I am still able to view, edit, and add to my work calendars. Disaster averted.

Kudos

I’m incredibly impressed with the inherent flexibility of the Android OS. The commercials for the MyTouch 3G (which also uses Android) that tout the system’s myriad personalization options are really spot-on. Within a couple days, I already have a setup that is very usable and customized to my taste. I’ll write more about this when I blog about apps.

The touch screen is great. This is the first touch device I’ve owned and I’ve always been a bit leery, especially of onscreen keyboards. However, the screen is so responsive and the virtual keyboard so good that I find myself rarely using the physical keyboard.

Google Maps and Google Voice integration are awesome. The navigation app is simply game-changing (no wonder Garmin’s stock dropped significantly once Google introduced it!)

Some other highlights:

• Threaded SMS messaging
• Push support for Gmail
• Great call quality
• Very good voice recognition

Gripes

Of course, nothing is perfect, not even shiny new tech-toys. There is always room for improvement, and these are just a few of the things I’ve run into already that leave me wanting more:

Groups support – Gmail itself does a great job of supporting contact groups, allowing you to send messages to groups, arrange contacts, etc. Android’s support of groups is incredibly rudimentary. All you seem to be able to do is filter your contacts by choosing which groups sync from your Gmail accounts and which groups are hidden. Even then, it is a multi-step process that’s more work that it’s worth. I can’t set ringtones based on group membership, I can’t send emails or SMS texts to groups, and I can’t even modify what groups that contacts are members of. This is the biggest FAIL I’ve come across thus far …

Notifications – I’m surprised to say this, but my old Blackberry Curve did a much better job of managing notifications than the Droid. On the Blackberry there was a single menu section for specifying all the many notifications – phone calls, text messages, email accounts, etc. You could set up multiple notification profiles and easily enable them from the home screen. In comparison, the notifications subsystem in Android is much more rudimentary. Within each app, I can control its notifications, and there are some system-wide settings for ringtones and such but no support for multiple profiles. Once notifications are set, all you can do is adjust notification volume, turn off audible alerts (leaving only apps that would normally vibrate), and turn off both audible and vibrating alerts. I’m really disappointed that I can’t set up a more specialized vibration profile, but it seems I may have to find “an app for that” …

Physical Keyboard – One of the bragging rights of this phone is that it has a physical keyboard. However, it sucks. Seriously. I loved the keyboard on my Blackberry. Despite its tiny keys, I could quickly and accurately type what I needed. At first I thought it might just be a learning curve issue, but then I tried the onscreen keyboards (both in portrait and landscape mode) and found them much more usable and accurate. Including a physical keyboard on this device was a significant design decision by Motorola – you would think they would have made it worthwhile! It leaves me wishing they had left it out and saved a couple millimeters in thickness and reduced the mechanical complexity.

Bluetooth Voice Dialing – The last gripe I’ve got (for now) is that Android doesn’t support bluetooth voice dialing. Period. It’s just not there. I’ve done some research and this is simply a feature that isn’t implemented in Android (yet?). This is a huge disappointment for me, because I (did) usemy bluetooth headset for voice dialing all the time. The Droid does have a “Voice Dialing” app, which works very well. You just can’t use it with bluetooth. This seems like such an obvious oversight to me. Even my wife’s old LG enV2 had this feature. My old Motorola e815 that I had 3 years ago had it too. Bluetooth voice dialing pre-dates Android’s existence! Why is it not supported?!?!?! Argh.

Final Thoughts

Don’t take all my gripes to mean I don’t like the Droid – I still love it. It’s just that when a device has so much potential it’s hard not to notice the areas it falls flat on its face. I’m still finding it incredibly useful and overall a much more powerful device than my Blackberry. I still have some things I need to tweak (getting favorite mobile sites bookmarked, etc.) and more apps to play with, but I’m sure that will come with time.

Stay tuned for upcoming posts where I’ll talk more in depth about apps, Google Voice integration, and more!

One of the challenges I faced in configuring my new backup system on my Ubuntu Linux-based server was setting up my two external drives to mount at the same place in the filesystem.

Why? Because the program I use to manage my backups, BackupPC, expects the storage “pool” to always be in the same place. My options were to write a script to change the BackupPC configuration each time a different drive was plugged in, or make the pool mount in the same location regardless of which drive I’m using. Because I was working with LUKS-encrypted volumes I faced additional complexities which made it  difficult to use other methods (like volume labeling) because of how Gnome handles and mounts such encrypted volumes.

While it took a while to make it work, once I figured it out it did exactly what I needed. Now, I’m sharing my results with you to save you the trouble of doing all the research yourself!

I found the easiest solution both for this problem and my next one (making eSATA drives auto mount) was to use HAL configuration files. HAL stands for “Hardware Abstraction Layer” and is one of the ways Linux interfaces with various hardware elements, including hard drives. Using XML it is easy to create custom policies to define how HAL handles particular devices.

(*Note: I have read that Ubuntu will soon be moving away from using HAL, possibly as soon as 9.10, Karmic Koala. I’ve tested this on Ubuntu 8.04, 8.10, and 9.04, but it should work with any distro that (still) uses HAL.)

(** Note 2: Having recently begun the process of rebuilding my server on Ubuntu 9.10/Karmic, I can verify that this method DOES NOT WORK. I am currently in the process of figuring out a solution, likely using udev and scripting, and will post my results as a post here …)

These configuration files are located in /etc/hal/fdi/policy. My installation included one existing file – preferences.fdi – which defines whether non-removable drives are auto-mounted. (We’ll get to eSATA auto mounting soon enough …)

Some quick notes on how .fdi files work: first devices are matched with pre-determined keys, defined through XML. Then, actions are taken by changing (or “merging”) other keys. A very basic .fdi file might consist of the following:

<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">

 <device>
   <match key="some.key" string="some_string">
     <merge key="another.key" type="bool">true</merge>
   </match>
 </device>

So what’s the easiest way to find these keys to match and merge? In my experience, Gnome Device Manager (aka gnome-device-manager).

To see if you have Device Manager installed, check under “Applications -> System Tools” or try to launch gnome-device-manager from the terminal. If it doesn’t work, install it using Synaptic or run:

sudo apt-get install gnome-device-manager

With your drive plugged in and turned on, open up the device manager and begin to look for your drive. You may have to expand some of the trees for “SCSI Host Adapters” and “SCSI Devices”, or possibly USB-related trees,  before you see the drive entries, usually titled “Mass Storage Drive” or something about removable storage.  There may be several of these entries. You will need to look at attributes like the model numbers and capacities to determine which drive it is you’re wanting.

Once you’ve identified the drive you want the information for, type ctrl+p or click on “View -> Device Properties” which should make an additional “Properties” tab appear beside the previous “Summary” tab. Now you will be able to see the various keys, types, and values you can use when creating .fdi files. For our purposes here we will need to look at the properties not for the drive itself, but for the volume we want to create a mount point for.

Note: this is with drive attached via eSATA

Our first order of business is to find a key that will provide a definitive match for each drive / volume. In my situation I was using two identical external enclosures with two identical drives. I could have simply created one rule that would specify the mount point based on any drive that matched some shared property, such as the model number (storage.model) but I wanted to make sure that these two volumes and only these volumes would share this mount point. In addition, I wanted to be able to tell at a glance which one was mounted, so I needed HAL to distinguish between them somehow.

Every volume has a distinctive UUID – kind of like a fingerprint that identifies it to the rest of the system. In the device manager, under the properties tab for the volume you’re working on, look for the volume.UUID key. Once you’ve found it you can begin to write your HAL policy file.

Create a new, blank text file in /etc/hal/fdi/policy. (You will probably need to do all this as root / sudo) Name it something like 30-sharedmounts.fdi. (The “30″ in the file name makes sure this policy is evaluated prior to the general preferences file.) Once you have created your file, open it in your favorite text editor and start with the following:

<?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">

Now we need to specify the device and they keys we want to match and merge:

<device>
 <match key="block.is_volume" bool="true">
 <match key="volume.uuid" string="7feeefbf-416b-4383-9bb3-7fd51cb3e702">
   <merge key="volume.policy.desired_mount_point" type="string">ext_backup</merge>
   <merge key="volume.label" type="string">Ext Backup 1</merge>
 </match>
 </match>
</device>

Here’s a quick explanation of what you see above, and what each does:

• <match key=”block.is_volume” bool=”true”> – A little bit of insurance, to make sure we’re working with a volume and not a drive.
• <match key=”volume.uuid” string=”7feeefbf-416b-4383-9bb3-7fd51cb3e702″> – As described above, identifies the particular volume you want to specify the mount point for.
• <merge key=”volume.policy.desired_mount_point” type=”string”>ext_backup – This is the new mount point, which will appear beneath /media/ , so this example would mount as /media/ext_backup .
• <merge key=”volume.label” type=”string”>Ext Backup 1 – A little extra nicety. This is how we can identify between different volumes, even when they’re mounted at the same point in the filesystem.

Now that you’ve got the mount point specified for your first volume, you’ll want to do the same for your second (and any other subsequent) volumes. For each volume, just find the UUID and create a new <device> section in the .fdi file. Be sure to specify the same mount point and unique volume labels (if you so desire.) Once you’re done, save your file and restart HAL (or just reboot.)

sudo /etc/init.d/hal restart

Now, whenever you plug in your drives and Gnome auto-mounts your volumes, they will mount in the same place every time.

What’s that, you say? You’re using eSATA drives and they don’t auto-mount? My next blog post will take care of that for you, and it shouldn’t take more than about 5 minutes of your time. As an added bonus, this method will mount the volumes in the same place regardless of whether they’re connected by USB or eSATA.

After obtaining (and assembling) my new backup hardware my first order of business was to get the external hard drives formatted and set up with drive encryption. Since I’m swapping out one drive to store off-site I wanted to use drive encryption just in case it somehow ended up in someone else’s posession. In Ubuntu, the easiest way to encrypt a whole drive is using LUKS. I chose LUKS because it is easily readable by most Linux computers and can even be set up on a Windows PC, if absolutely necessary. This post will walk through the (remarkably simple) process of setting up encryption and formatting.

(Note: most of these instructions are condensed adaptations of articles I found here and here. )

FYI: I set up my drives using these instructions on Ubuntu 8.10 – Intrepid Ibex. I was later able to successfully mount and access the drives using Ubuntu 8.04 – Hardy Heron on my server and 9.04 – Jaunty Jackalope on my laptop.

When setting up my drives I was using USB 2.0, therefore these directions reflect that. The process may have been faster using eSATA, but at the time I did not yet have a controller card. The directions should be applicable to eSATA as well (unless otherwise noted), but your mileage may vary. These instructions can also be easily adapted for creating a handy, encrypted USB “thumb” drive.

Necessary Software

In order to proceed you must have the cryptsetup package installed:

sudo apt-get install cryptsetup

Finding the drive

After powering on the drive and hooking it up to the computer you need to identify the device:

dmesg | tail -20

[33884.688746] usb 4-1: new high speed USB device using ehci_hcd ...
[33884.764079] usb 4-1: configuration #1 chosen from 1 choice
[33884.764868] scsi8 : SCSI emulation for USB Mass Storage devices
[33884.765316] usb-storage: device found at 9
[33884.765321] usb-storage: waiting for device to settle before scan...
[33888.042416] usb-storage: device scan complete
[33888.043707] scsi 8:0:0:0: Direct-Access     HDS72505 0KLA360 ...
[33888.047550] sd 8:0:0:0: [sdb] 976773168 512-byte hardware sectors
[33888.048292] sd 8:0:0:0: [sdb] Write Protect is off
[33888.048300] sd 8:0:0:0: [sdb] Mode Sense: 00 38 00 00
[33888.048305] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[33888.049648] sd 8:0:0:0: [sdb] 976773168 512-byte hardware sectors
[33888.050421] sd 8:0:0:0: [sdb] Write Protect is off
[33888.050428] sd 8:0:0:0: [sdb] Mode Sense: 00 38 00 00
[33888.050432] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[33888.050438]  sdb: unknown partition table
[33888.066470] sd 8:0:0:0: [sdb] Attached SCSI disk
[33888.066545] sd 8:0:0:0: Attached scsi generic sg2 type 0

In the example above (from this article)  you can see that the drive has been recognized as /dev/sdb. Your drives may show up differently (mine appeared as /dev/sdd and /dev/sde.) I’ll continue to use /dev/sdb to refer to the drive we are working with, but you should replace it with whatever your result is.

Create the partition

Before you can actually set up encryption or format the drive, you must create a partition. This is simply a portion of the drive you intend to store data on. A single physical drive may contain multiple partitions (as is usually the case with a linux boot drive) or just one. At this point you could easily choose to set up both an encrypted and a non-encrypted partition on your drive. I didn’t have a need for this, so I’ll be continuing with a single partition.

While it can be accomplished via the command line, I chose to use the graphical GParted program, available under the “System -> Administration -> Partition Editor” menu.

Choose your device via the drop-down menu in the upper right-hand corner. Then, select the unallocated space and create a new partition that encompasses the entire available space. We do not want to format the partition, only create it, so select “unformatted” as the filesystem.

Click “Apply” and your new partition will be created. You should now have a partition named something like /dev/sdb1 (notice there’s now a number added.) Once you have created the partition successfully, close GParted.

Setting up encryption

The next section is copied verbatim from the aforementioned article:

The dm-crypt, sha256 and aes kernel modules will need to be loaded prior to encrypting the partition:

sudo modprobe dm-crypt
sudo modprobe sha256
sudo modprobe aes

If the following error messages appear when loading sha256 and aes:

sudo modprobe sha256
WARNING: Error inserting padlock_sha ... No such device

sudo modprobe aes
WARNING: Error inserting padlock_aes ... No such device

it is an indication that the system does not have a hardware cryptographic device (source: Ubuntu Bug #206129)

The workaround is to add the following lines (using your favorite editor) to the bottom of /etc/modprobe.d/aliases and re-run the modprobe commands for the sha256 and aes kernel modules:

alias sha256 sha256_generic
alias aes aes_generic

Note that this is only necessary when we are setting up the drive. Later we will access them through Gnome and won’t need these modules.

Encrypting the partition

Finally, we can run the command to encrypt the /dev/sdb1 partition.

While there are other ways of securing your encrypted drive (such as key file stored locally or on a USB flash drive) I have chosen to use a strong passphrase. Mine is 23 characters long, but any password 12 characters or longer not consisting of dictionary-findable words should suffice.

The tutorial I used recommended the following command:

sudo cryptsetup --verify-passphrase luksFormat /dev/sdb1 -c aes -s 256 -h sha256

The LUKS-formatting command above has the following options:

• –verify-passphrase – ensures the passphrase is entered twice to avoid an incorrect passphrase being used
• -c aes – specifies the use of AES encryption (c for cipher)
• -s 256 – specifies a 256-bit key size
• -h sha256 – use 256-bit SHA for password hashing

However, after reading this article I decided to go with 128-bit AES encryption instead, along with a strong passphrase, in hopes of reducing some computational overhead. Therefore, my command instead looked something like:

sudo cryptsetup --verify-passphrase luksFormat /dev/sdb1 -c aes -s 128 -h sha256

Creating the filesystem

After setting up the encrypted partition, you must open and map it in order to set up the filesystem and begin using it.

Start with:

sudo cryptsetup luksOpen /dev/sdb1 secureUSB

Which should prompt you for your passphrase and map the drive to /dev/mapper/secureUSB. Now you can format the encrypted partition with a filesystem using whatever method you prefer. I had good luck using GParted to format in ext3.

Like before, select the device you want to create the filesystem on – in this case /dev/mapper/secureUSB. You should again see a block of unallocated space, which you should select and create a new partition within. You may be presented with a big, scary message about setting a disklabel – tell it to create (since you have no data to lose on the drive at this point anyway!)

The create new partition screen will look just the same as before, only this time you will want to specify the filesystem type you want to use. Apply all the pending operations and wait for the formatting process – it can take quite a while, especially for large drives.

Mounting the encrypted drive

Having successfully set up encryption and created a filesystem, we’re almost ready to to mount the drive and begin using it! (Of course, this is still assuming you’re using USB. If you’re using eSATA then this won’t work as easily – that will come in a later post!)

Shut down the computer, disconnect the drive, and reboot. Once you’re back up and logged in, reconnect the drive and Gnome should prompt you for the passphrase and then mount automatically.

If you want the drive to unlock automatically on this computer, select “remember forever.”

After you’re unlocked and mounted, the final step is to take ownership of the drive’s root folder with a user other than your sudo/root user:

sudo chown youruser:youruser /media/disk

where youruser is the user you want to have ownership and /media/disk is where gnome auto-mounted the drive.

Finished!

Whew! I must say it has taken far longer to write this post than it did to actually perform these operations. The longest part of the entire process was creating the ext3 filesystem. If you’re using eSATA to set up the drive it will go much faster, however as I mentioned you will have a few more steps to take before you can easily hot-swap your drive. Stay tuned for the next post in this series for that how-to …

Before I get to what my new backup hardware consists of, it might be helpful to know a bit about my existing (old) setup. My home network consists of a workstation, a laptop, a netbook, a seldom-used garage PC, and a multipurpose server. Among it’s many duties, the server is a centralized backup server, allowing the various computers to back up files each night. It runs on an old AMD Athlon motherboard with 512MB RAM, using a 30 GB drive for the OS and programs and a pair of 200 GB drives for storage and backup.

Prior to this upgrade, the backup drive was regularly at 95% capacity. Even with the intelligent pooling technology used by the BackupPC software it had become necessary to limit the number of nightly backups I was keeping in order to make space for the unique data from the various PCs.  So I decided it was time to upgrade my storage situation.

I had been debating for a while how to best increase my storage space while also ensuring the integrity and protection of my data. Having recently witnessed my parents’ misfortune and recognizing that if a similar tragedy would have happened to me that many priceless digital memories and large amounts of work-related data would have been lost, I knew it was time for a system that incorporated some kind of off-site backup.

One option I contemplated was an online backup service, where your data is stored in the “cloud” and available whenever and wherever you need to access it. The particular provider I considered was SpiderOak. I had one of their free 2 GB accounts already and I was very impressed with their security and privacy policies as well as their interoperability with Linux. However, the problem with such online backup options is their monthly fees. For the price of 100 GB per year at SpiderOak I could buy a hard drive ten times that size!

So that’s what I did – I bought two 1TB hard drives. This will allow for one hard drive to be in service and the other stored at a secure, off-site location in case of disaster. I’ll have tons of storage space and no monthly fees. A win-win situation.

Of course, juggling two different drives means additional complications with set-up and management, but those are later blog posts.

My original plan was to buy two bare drives and two USB enclosures. My server does not support serial ATA (SATA) drives, so USB seemed easiest for both compatibility and swap-ability. I’ll elaborate later, but to make a long story short USB simply was not adequate for my particular needs, so I ended up purchasing a PCI SATA controller as well. Thankfully the enclosures supported both USB and eSATA, so everything else was simply a matter of configuration (also another post.)

So finally, here’s the hardware I ended up using to make my backup plans a reality. All links are to Newegg, my personal favorite purveyor of computer parts. (The prices listed were as of July 2009, and I’m sure will probably become laughable as time passes.)

• 2 Western Digital Caviar Green WD10EADS  1TB SATA drives – $79.99 ea.
• 2 Vantec NST-300SU external USB / eSATA enclosures – $27.98 ea.
• Rosewill RC-210 PCI internal & external SATA controller – $19.99

Total cost – $235.93 (All the items qualified for free shipping at the time I ordered them.) Less than the cost of 100GB for two years through an online backup provider.

Thus far I’ve had no hardware-related problems, and everything has been superbly compatible with Linux (Ubuntu 8.04 LTS / Hardy Heron.) The drives are extraordinarily quiet. Since the server still has 3 internal hard drives and several fans, the new external drives are basically inaudible.

The only nitpick I’ve got is with the Vantec enclosures. There is a bright blue power / activity LED on the front the enclosure, and when you install the drive into the internal tray you have to plug the LED in as you put the enclosure back together. Two small, recessed screws hold the drive tray in place. I found (with both my enclosures) that if I tightened the screws all the way down, completely closing the gap between the tray and the rest of the enclosure, the lights would not work. If I backed the screws out just a few threads everything worked fine. I don’t think the gap is large enough to pose a concern, so it’s basically just a small aesthetic annoyance. Not a deal-breaker, but something worth noting.

That’s it for the hardware specs! Next up, formatting the removable drives and setting them up with LUKS encryption.

Over the next couple days (weeks?) you can expect more on the following topics:

• New backup hardware: drives, enclosures, and controller card
• Setting things up: LUKS encryption on external drives
• Specifying a shared mount point in Ubuntu Linux
• Switching from USB to eSATA, making eSATA automount
• Making external encrypted drives work with BackupPC

As you can tell from this list I faced a lot of hoops to jump through in order to get this up and running. I’ll add links to the individual posts as I write them. Feel free to ask questions if you’ve got any!

I don’t want this to come across as an “I’m just putting something on my blog because ohmygod I haven’t posted in ages!” kind of effort (even if at some level it may be), so here are a couple quick updates. In particular I’ll try to highlight some of the things I’ve posted about “recently.”

• My parents are doing quite well after their house fire last year. I just received word from them today that their construction loan has finally gone through. They are rebuilding on the same piece of land their old house was on, but starting literally from the ground up. They hope to start digging footers for the new construction next week (mid-May) and to be in the house by fall.

• The new Honda Insight has launched, to pretty good reviews I might add, but I’m still not convinced. It is about 4/5 of a Prius at a lower price, both size and mileage-wise. While the $20k price is attractive, I still have significant reservations about the overall environmental impact of all those hybrids’ batteries, even if they do use less fuel.
• I survived my first time through all the major seasons of the church (especially Christmas and Easter) and have emerged unscathed as I prepare to celebrate my 1 year anniversary of being a pastor on June 15th. It’s incredibly hard to believe it’s been almost 11 months, though I guess if you judge by the continually decreasing frequency of my blog posts, it’s not all that surprising.
• Part of the blame for my lack of blogging should also go straight to Facebook and Twitter. The more I seem to get sucked into these social-media oriented sites, the less I create original content for my blog. I do intend to remedy that though …

Rather than inundate you with more semi-interesting updates, I’ll leave you with news about this blog:

No, I am not abandoning it. Yes, I am actively planning new content!

• A review of my recent “road test” of a 2009 Nissan Versa. I’ve had my eye on the Versa as a possible next car for a while now, so you might be interested in my impressions after spending 350 miles with one.
• Some tech updates on “recent” purchases – Lenovo S10 netbook, Nikon D60 Digital SLR camera, and several others.
• Some insight into bicycle commuting – continuing the irony that this gearhead car-blogger often doesn’t even drive a car unless I can’t avoid it!
• A revew of Phyllis Tickle’s The Great Emergence – a wonderful, insightful (and relatively short) book about “how Christianity is changing and why.”
• A semi-regular feature for posting recipes, particularly for the soups and breads I make every Monday night as part of the dinner and conversation group I host.

So, there you go … proof that <montypythonvoice> I’m not dead yet! I’m getting better! </montypythonvoice> Stay tuned for new content coming soon, and feel free to leave your suggestions for interesting posts in the comments section!

This past Sunday after worship, the Richmond Church of the Brethren (CoB) celebrated the launch of its new website! This site has been months in the making, as it was in progress for quite some time before I became pastor in June.  You can check out the site to see all its exciting bells and whistles, including online calendars, a “conversations” blog, and online newsletter distribution. Since I did quite a bit of work getting the site finalized and ready for launch, I’ll talk about some of the more technical details of the site in the rest of this post.

The new site was set up and is hosted by Summersault database driven websites. There are several connections between Summersault and Richmond CoB, so they were a very logical choice. Summersault set up our server space, configured Drupal, an open-source content management system, and set up our preferred theme with some graphic-design tweaks. From that point the site was delivered to us to do any final design tweaks and to create the content.

(Working on getting this new site ready to launch has been another one of the reasons new content has been so sparse on my blog lately. Of course, buying a house may have something to do with my recent busyness as well.)

Calendar Setup

While Drupal has quite a bit of built-in event scheduling and calendaring functionality, both myself and the church’s office manager are committed Google Calendar junkies. While Drupal plays relatively nice with GCal, it isn’t quite as easy to use for recurring events, rescheduling things, and interfacing with other services and devices.

In the end we decided to use a combination of Drupal’s built in calendar and Google Calendar. Special events are scheduled using the Drupal site, while recurring events and more mundane things like when the church office is open, etc. are scheduled via GCal. Since Drupal exports an actively updated .ics file that GCal can subscribe to, I was able to set up a calendar display page that uses an embedded Google Calendar to display both sets of events at the same time. It sounds somewhat cumbersome, but at this point it’s the best compromise we were able to set up. For end users I think the experience will be relatively transparent.

CSS Tweaking

In addition to figuring out the finer details of how we were going to use the calendar, we also ran across several aspects of our chosen template that we wanted to tweak or change. Since a number of people in our community use Linux, I wanted to do what I could to make sure the site looked good on both Windows and Linux browsers. Since many Linux installs don’t include the same fonts as Windows, some aspects of the layout needed to be adjusted to make sure things lined up correctly when non-standard fonts were in use.

As I tweaked the CSS I also found myself banging my head against the wall a few times as I learned some of Drupal’s eccentricities. While Drupal is an amazingly configurable, adaptable, extensible piece of software, that sometimes results in complexity and a steep learning curve once you start to try and fiddle around “under the hood.” I made a few changes to the actual PHP and HTML code that makes up the template we’re using, but most of the changes I made were just in the CSS files.

What now?

Now that the site has officially been launched there will be some additional upkeep needed right from the start. We’re going to try and have an up-to-date list of upcoming worship themes and preachers on the “Worship” page, the calendar will need to be kept a bit more updated, and the Conversations blog will need attention if we really want it to be a place where conversation is taking place.

Because of Drupal’s expandable nature we have a number of options we may look into in the future for expanding the site. One popular possibility is to do some sort of sermon podcast, possibly with sermon texts available too. Another idea would be to have an area that those who help in various kinds of church leadership can use for collaborative planning and resource sharing.

Overall I’m excited about having the new site up and active. It will mean that my online attention will be stretched a little bit thinner with regards to blogging, now that I have 2 different sites vying for my writing attention. However I think that it may also be a generative experience, where I’ll be coming up with ideas that might not work just right for the church blog, but would be appropriate for this site. Only time will tell.

So what are you waiting for? Check out the new site! Let me know what you think, and if you’ve got any suggestions I’d love to hear them.

I realize that there are probably two types of people who might stumble across this site … those who are interested in the content I’m posting, namely articles about computers, cooking, cars, Christianity, and the occasional personal interest piece, and then there are those who are more interested in me as a person and follow this blog to see what I’m up to and what I’m thinking.

This post is mostly directed to this latter portion of my audience. I want to make sure you know that there are other ways that you can stalk me keep up with what I’m doing besides this blog.

For a long time I didn’t jump onto the bandwagon of friendly internet stalking social networking, however over the past 6 months I have decided to give it a go, and I must say that these days that the easiest way to follow along with my life is through these various mediums.

If you’re wondering about the repeated references to stalking, they are because of my inherent distrust and skepticism of the whole social networking scene. I think it’s really far to easy to simply seek out people you know and watch what they’re doing as they post to these networks and never actually take part in the “social” aspect of things.

But despite my skepticism, I figured that there might actually be some folks out there who are genuine in their intent to make this a social endeavor and that I might as well give it a try. So whether you’re just someone who wants to watch over my shoulder as I live out my life, or if you’re genuinely interested in networking with me, here are the places you can find me online:

Facebook

Just look for Matthew E. McKimmy. I’m part of the Virginia Tech and Dayton, OH networks. I tend to frequent Facebook the most out of all these social networking tools, so this would be a logical place to start if you want to connect.

Twitter

My username is mattmckimmy, and my Twitter home page is here. Twitter is notoriously flaky, though they seem to be getting a little bit better. I’ve never really fully understood how you’re supposed to “network” through Twitter, but I do post what I’m up to fairly regularly.

Plurk

Again my username is mattmckimmy and you can find me here. I think I would actually prefer Plurk over Twitter if I ever used either of them regularly. It’s much more user-friendly and easier to understand. I also like the different verbs they encourage you to use, much more so than Facebook’s standard “is.” However, as of yet I don’t know of anyone else who uses Plurk.

LinkedIn

Honestly I’m not sure how you’re supposed to find people on LinkedIn, but some friends invited me to join so I did. I do have a public profile anyone should be able to see. The idea behind LinkedIn is to leverage your social connections for business and career purposes, though I have yet to figure out how that would benefit me at this point.

Flickr

Honestly I don’t really use Flickr, I only have 2 photos uploaded there at the moment. Even so, there is a possibility I might begin to use it more regularly. I have a number of friends who are on Flickr, and when it comes to social networking peer pressure is a powerful thing. If you want to check in and see if I’ve actually uploaded anything, check out my photostream.

And now for a confession … I cheat at social networking. Let me explain. Many of these social networking tools use little blurbs to let people know what you’re up to, how you’re feeling, etc. It seems silly to have to post the same sentiments or to have different, possibly conflicting messages in all these different places. So I use a great web service called Ping.fm to post to nearly all of them simultaneously. What does this mean for you? Well, it means that if you’re following me on Twitter and Plurk and watching my status updates on Facebook and LinkedIn, that you’re going to see the same message 4 times.

I do occasionally post something to one of them that isn’t duplicated elsewhere, however that’s probably not the norm. If you’re interested more in the networking aspect of social networking and not just the stalking, then Facebook is the primary place I tend to do that. That’s not to say I wouldn’t use these other services more regularly if people I knew also used them, however at this point most everyone I want to connect with seems to be on Facebook.

So how do you use social networks? Are you a silent facebook stalker? An avid twitterer? A flickr junkie? Do you have the same skepticism I have when it comes to using these tools to their fullest? Let’s hear your thoughts in the comments …

Back in the early days of Firefox it held many clear advantages over its primary competitor, Microsoft’s Internet Explorer. These days, Internet Explorer, Opera, and Firefox have all come a long way, and each has some very compelling merits. I’ve used all three and in my experience this newest version of Firefox is on top of the heap.

Apparently I’m not the only one who is excited about Firefox. As I am writing this, about 6,287,283 downloads have been registered on Mozilla’s official counter on the Spread Firefox site. Mozilla is hoping to establish a world record for most downloads in a 24 hour period, and on the site said they hoped to reach 5 million. Obviously they’ve easily surpassed this, and they still have another 4 hours to go.

There are tons of articles floating around outlining the many improvements made in this new version of Firefox including faster page loading, less memory usage, a nearly-psychic “smart” address bar, and increased security features. Here are just a couple of the articles I’ve read about it:

• Top 10 Firefox 3 Features (Lifehacker)
• Top 10 reasons you should upgrade to Firefox 3 (TG Daily)
• Igniting an open revolution: Firefox 3 officially released (Ars Technica)
• Technology Today: Firefox 3 Download Day (I Never Promised You an Organic Garden)

So what are you waiting for? Download it and take it for a test drive!