Here’s my Google+ profile.
See also my initial thoughts about Google+.
A friend invited me about 10 days ago into Google+, Google’s new “social” service. As many others have commented, it’s very well done for a “field trial” as Google calls it. The UI is very nice – with a couple of exceptions like endless comment streams – and Google+’s handling of photographs is beautifully done. You can get to my Google+ posts by clicking on the G+ icon over at the top of the right sidebar on this page.
Of course, Google+ is still new – and it’s attractive partially just for that reason. It’s sort of like the new restaurant in town. Still, I’m finding that Facebook is getting less of my attention as a result of Google+. How about you?
As for Twitter, I typically keep Twitter running – as a separate app – off on the right side of my display and always in view along with my browser. It’s a parallel feed – and I appreciate it’s “information density” with short posts, no integration of comments, etc.
Facebook, on the other hand, I run in a separate browser tab – a tab that I have to decide to click and go to – just like my email (ugh!). In the “attention economy”, seems to me that’s important – at least in the desktop environment.
On a mobile device, it’s clearly a different story. Each app is “all consuming”! We’ll see how the Google+ iPhone app affects our mobile usage – once that app is released.
Going forward, it’ll be very interesting to see where Google+ goes. Might it replace my separate blog here? Or…?
Earlier this afternoon, I implemented Facebook Comments here on my personal blog. It was trivially easy. There’s a WordPress plug-in available called, appropriately enough, Facebook Comments, which was a quick install and a straightforward configuration to enable. Once configured, the comments were active.
I fretted a bit about one configuration option – should I leave the old WordPress comments on – or just enable the new Facebook comments system? I decided to leave the old comments on – the new Facebook comments are positioned above the WP comments on the individual post pages.
I made one tweak to the Facebook Comments php code to add a link to #respond just above the Facebook comments section. By default, that link goes to the WP comments from the home page – and I didn’t want that. If someone wants to add a new comment, I’d prefer they do so using the Facebook commenting scheme. [Update: Scratch that – version 3.0 just became available – we’ll see whether I try to make that change again – or not! Turns out I did make the mod – it’s now in facebook-comments-display.php!]
Time will tell whether this makes sense or not. MG Siegler just wrote a post about the experience with Facebook Comments on TechCrunch. Meanwhile, I must say it’s a trivial implementation for a WordPress blog. Yet another example of Facebook extending its reach!
A colleague asked “So Scott – tell me again what you do about emails you open with 1) PDFs and 2) links – that you want to read later, on the airplane?”
Here’s what I’ve been doing:
How about you? How are you managing your online life?
For my personal sites, it’s interesting that my recipes blog, ScottsKitchen.com, has been running about twice the number of page views daily that this blog receives. While I tend to think of sjl.us as my personal “hub” – the web doesn’t. It likes food (and recipes) much better! 😉
Our hyperlocal blog – InMenlo.com – has yet again twice the number of pages views – it’s become very popular indeed. Fascinating that a significant amount of InMenlo’s traffic comes from Facebook while the traffic to ScottsKitchen and SJL.US comes primarily from the search engines.
Part of that is seasonal – my high heat upside-down roast turkey recipe on ScottsKitchen.com is an annual Thanksgiving favorite! Since I posted it in 2005, it’s consistently been the top page on that site. Our late fall roasted tomato soup recipes were also pretty popular this year.
In my book, the “gold standard” for a superb recipe site is SimplyRecipes.com run by Elise Bauer. She does a wonderful job – combining great recipes with luscious food photography! The iPhone web app version of her site has come in very handy for me many times!
My other go to iPhone app for cooking is Mark Bittman’s How to Cook Everything. The paper edition of this cookbook was my late friend Chris Gulker’s go to bible for cooking! His kitchen copy is delightfully bookmarked, spattered and stained – a real working volume!
I seem to remember recently that Google announced a new image format that offered significant (40+%) reductions in image sizes – part of an effort to make the web more efficient.
I’m an avid podcast listener – I currently have over 6 GB of podcasts sitting in my iTunes library. These podcasts simply take too long to download – they’re typically in the 20-40 MB range in size.
Aren’t there solutions available that would dramatically reduce these file sizes?
Why aren’t we making progress in this area? What am I missing?
When I launched this new WordPress-powered version of my blog over the weekend, I quickly looked through some recent photos to find one that would be suitable for use in the header image. The one I picked, which I’ve loosely titled “Band on the Run!“, was taken on November 19, 2010, in County Wicklow in Ireland. Seems like a near perfect shot for an album cover, doesn’t it?!
We’re standing on a cliff overlooking Luggala – the Guiness estate. We had just jumped out of our tour bus (Wild Wicklow Tours – highly recommended!) and were headed over to capture the views when I snapped this photo with my Canon PowerShot S95. My Glenbrook partner Carol Coye Benson and I were in Ireland teaching our Payments in a Mobile World workshop earlier that week. That’s Carol out in front of the band in the photo!
Here’s a page showing all of the header images that I’ve used over the years on sjl.us.
Since 2003, this blog has been hosted by TypePad. They’ve provided excellent service – I have no complaints in that regard.
So, why did I decide to migrate from TypePad to WordPress?
Basically, the TypePad version of this blog had been put together (by me) using Advanced Templates and a bunch of hacks. It worked – but even I couldn’t figure out how to maintain it going forward.
So, I decided to migrate.
Over the last two years, I’ve launched several other blogs based on WordPress – and have become more familiar with the administrative aspects of WordPress. WordPress has just become more comfortable. That’s not to say it’s simple. WordPress is complicated – especially with respect to themes, plug-ins, etc. Be careful.
That said, while the posts export and import readily, there are many other issues – like image libraries that don’t export/import cleanly, category archives that have different permalink locations, and photo albums that simply don’t migrate. Not a pretty picture – but no surprise given the current state of the blogging art. Cruft. Crap.
I stopped using the TypePad photo albums a few years ago – when I became such a Flickr fan. But, there earlier links are still around, in the search engines, etc. Want to view my photos? Checkout my Flickr site!
Among other things, my migration initially screwed up the images displayed on another of my TypePad blogs. We’ve figured out a clever workaround for that – but it’s dependent on both the old and new sites being available. No way to cut the cord between the two without a lot more work. We’ll deal with that eventually.
Tonight, I spent time adding a bunch of redirects for the TypePad category archives – to their new locations on my new WordPress instance. This was just another giant hassle – but, with only about 30 categories, something I could get done without a lot of pain. Luckily, .htaccess provides a lot of power for redirection of URLs – but it’s still a giant PITA.
Tonight, I think we’ve got most of the conversion issues resolved. I’m watching the logs to see what URLs from searches aren’t resolving correctly – and may need to add a few more tweaks. Such is the life of the aging sysadmin…
So, last night I rolled sjl.us over from TypePad – where we’d been since 2003 – to a hosted WordPress.org site. All in all, took about an hour to do the work – and then another couple waiting for the DNS change to propagate.
All of the old post content is now on this site – although almost all of the URLs have changed as a result of differences between TypePad and WordPress handling of permalinks. Unfortunately, the import/export process doesn’t support all of the images in my historical posts either – so we’ll be manually sorting through those over the holidays and trying make things presentable again. Such is the nature of things.
Hopefully, Google will begin making sense of this new site in relatively short order – although at the moment I’m frustrated with Google Webmaster Tools and an inability to force a refresh of the site’s robots.txt fiie. Apparently this only happens on a 24-hour cycle.
What happened to the “real-time web” anyway?!
[Update: I decided to change the permalink settings in WordPress to mimic the permalink format that TypePad used. So far, so good. Some of the archive and category pages aren’t mapping – but the individual post pages are now working nicely.]
Turns out yesterday was the 9th birthday of this blog – with the earliest posts being made back on November 25, 2001. Next year, we’ll celebrate 10 years of personal blogging!
There actually were earlier posts – a quick look at the Wayback Machine shows an early page on October 19, 1998 – just a placeholder with no content! So the November 2001 date is really just a placeholder for the content I was able to bring across on to whatever platform I was using back then.
A page from August 1999 shows the actual beginnings of the blog – created back in those days using Microsoft FrontPage! So the true birthday was more likely back sometime in 1999 – but the cruft gets the way of actually seeing it!