Today is: Thursday, 11th March 2010
Log in

Technology, Web Development and Saltwater Fly Fishing, not in that order.

The Blogs as Aggregator

Over the past two years, we’ve seen the genie come out of the bag on blogging.  In the good old days if you wanted our content, you came to our blog.  Now, our content is being automatically posted in a bunch of spots, perhaps on Facebook, Google Buzz, Google Reader, and even the headline shows up on Twitter.

Then we throw our participation on those other sites in, and now we’re all over the place.  It’s hard for us to keep up with everything we’re doing, but our readers are at best getting an incomplete picture.

So I pose this question: should not our blog be the place where all of our participation is aggregated? Maybe this site indeed should be “All Things Cahill” as the name implies.

There are several problems:

  • We need to filter for unique content.  The recent Google Buzz launch has shown that cross posting between services can lead to some truly weird looping problems.  Multiple copies of the same post start to show up as Buzz posts to Twitter and Twitter sends to Buzz.  Honestly, I’m surprised some of you haven’t unraveled the fabric of the universe…
  • What about the unique flavor of those services?  Personally, I like the distinct difference between my Twitter posse, the Facebook crowd and my audience here.  They’re all different communities and the idea of tying them all together here might be somehow denigrate that.  For the record, Facebook tends to be my long time friends, the folks I have physically met, whereas Twitter is a more general distribution.
  • Does removing the message from the service remove it from it’s context?  Quite probably, esp. in the situation that my comment is part of the ongoing discussion.

So I ask the question: does it make sense attempt to pull in as much as possible from around the web?  Obviously twitter is here, how about Google Buzz, Foursquare, Yelp, etc.?

Deep down suspect we’d find overall the non-blog content is generally of much lower value.  Share your thoughts…

It’s Time to Rethink the Permalink

The permalink – nothing could be more core to the concept of blogging, and indeed, content management.  In it’s early inception, it was the one link to rule all others.  The problem is that with the advent of microblogging systems like Twitter, the permalink has been devalued and now faces possible extinction.

From Wikipedia:

permalink, or permanent link, is a URL that points to a specific blog or forum entry after it has passed from the front page to the archives. Because a permalink remains unchanged indefinitely, it is less susceptible to link rot. Most modern weblogging and content-syndication software systems support such links. Other types of websites use the term permanent links, but the term permalink is most common within the blogospherePermalink is a portmanteau word made from permanent link. Permalinks are often simply stated so as to be human-readable.

Here’s the problem: while the permalink once was the one true way to identify our content, it’s now going more or less unused, as people instead link to shortened urls, using services like Bit.ly or others which provide character economy in the links that are used around the web.  Hence, with shortened urls in use, it becomes much harder, if not impossible to find mentions and, in fact, discussions, surrounding our content.

I’ve decried over the past year the ongoing diaspora of blog comments.  The discussion continues, but for many bloggers, its moving out of the confines of their blog, into the realm of Twitter, Google Sidewiki, and in the semi-walled garden of Facebook.

It was one thing when there were reliable Trackbacks, but the spammers have all but killed that for us.  Hence the discussion continues, but it often continues without us, the folks that wrote the content in the first place.

So here’s the thought: perhaps it’s time we rethought permalinks.  Instead of existing as a single link, there probably ought to be both a long form (the old permalink) and a short form (shortened url) with the shortened url using the service of the bloggers choice.  Hence the blog software would have knowledge of both the long form (which would be used mostly internally) and the short form, that which would allow us to actually track where our content goes online.  This would further enable us to pull the discussions surrounding our content back into our pages where it ought to be…

Hence a blog which currently might have comments and trackbacks separately identified, might actually list the origin of a comment, such as “Via Twitter” or “Via Facebook” and actually thread the follow ups, and potentially direct replies from our blog to those comments back to the platform they came from as well.

The key concept here is that the blogger must control the initial shortened url, because the url shortening service becomes utterly key to our solution.  That service, like so many today, could provide us with an aggregated comment feed via rss, analytics data about where our shortened url was used, by who and also combine the data with the usage of our long form permalink.

What are your thoughts?

Wordpress 2.8.6 Released and a 2.9 Preview

I got the notice last night that Wordpress 2.8.6 was released to fix a pair of security holes.  So I hopped right into the admin console from my Iphone and in 2 minutes, it was updated.  If you have a Wordpress installation, I urge you to update right away as well.

This will almost certainly be the last release prior to the much anticipated release of 2.9 which is our next major (feature related) release.  Aaron Brazell had a great preview on his site yesterday, and since I’m not currently running the beta, I’ll leave the full on feature review to him.  Here are the major bits to expect:

  • Enhanced image handling – scaling, cropping, and thumbnail sizing on a per picture basis.
  • Trash Can – this really goes back to the old notion we saw in newspaper editorial systems, delete doesn’t really delete, it just hides.  This will come in handy.
  • The_post_image – if you’ve ever tried to add an image to an excerpt of a post you will know why this is important.
  • oEmbed – video support, which I’ve had for years using Vipers Video Tag Plugin.
  • Custom Post Type – this is one of those CMS type functions.  It’ll make my life easier, although honestly in the past I’ve been able to make categories do my bidding with little trouble in Wordpress CMS settings.
  • Comment Meta – I have no idea what to think about this one.
  • Metadata API – Another feature I’m sure I’ll use, but currently I can’t think of anything I’d use it for.  I guess this is like custom fields for everything, not just limited to posts.
  • Theme System Modification – this will allow developers to work on one theme, while real users look at another.  This has been needed for some time.
  • Rel=Canonical Optimization – seems like a little thing, but it will help a lot with SEO.

Check out the preview at Technosailor.com for the full scoop.

Tags: ,

Wordpress 2.8.5 Released

A new Wordpress release came out last night. Unlike the previous, this is what they are calling “a hardening release”, i.e. it is generally designed to make the code base more secure, but doesn’t fix any known vulnerabilities.  As with all minor level releases, I suggest you update as soon as possible, if for no other reason than to stay current.

From their blog:

  • A fix for the Trackback Denial-of-Service attack that is currently being seen.
  • Removal of areas within the code where php code in variables was evaluated.
  • Switched the file upload functionality to be whitelisted for all users including Admins.
  • Retiring of the two importers of Tag data from old plugins.

We can expect to see 2.9, the next major level release within around the end of the month, certainly before mid-November.  That release will supposedly center on enhancements to image handling features.

(For those casual readers, I should probably explain that I develop sites daily with Wordpress, and have for many years…hence I think my opinion on matters Wordpress should have some level of importance to you…)

Tags: , ,

The Death Knell of Paid Posts

Yesterday the Federal Trade Commission issued it’s first change the policy on endorsements in over 30 years.  From this point forward, if you accept any form of payment for a post, you need to disclose it.  PCWorld.com sums it up:

Bottom Line: If you receive gifts, money or any other type of compensation from a product manufacturer or service provider you have to disclose it.

For the record, it’s always been my policy that if there’s any possibility of conflict of interest, I disclose, as do others.  Obviously, I work for Namemedia Inc. and when I write about our sites or services, I am going to be slightly biased, but here, the voice is mine and I write about what I want.

A month or so ago, my wife asked me to write a post about a company she had a good service experience with, honestly I forget who it was.  I turned her down…much to my later chagrin.  I did offer to give her a login so that she might faun over them under her own byline.  The truth is that I couldn’t recommend a business I had no experience with, even if my own wife told me to.  Yes, the view from the dog house is quite lovely this time of year.

The timing for this ruling could not have been better, coming right after the Izeafest show in Orlando, which is a celebration of the sponsored tweet.  I’ll make the statement right here and now, sponsored tweets will be one of the things that will kill Twitter.  That and the inevitable move to niche real-time web services.  The minute you begin to appear as not genuine in social media, you’re on a down hill slide.

It’s just sad that the FTC had to actually put into regulations that which we, as bloggers, marketers, etc. should have known all along.

What is the next Wave?

Google Wave - a chance for us to rethink Social Media?

Google Wave - a chance for us to rethink Social Media?

For some time, I’ve been looking for the next compelling thing in social media sites. For that next development that transforms the way we interact, that re-envisions forums, chat, photo galleries, articles, etc; in fact a redefinition of the way in which we communicate online altogether.

For the past couple years, I’ve watch as vBulletin, my favorite forum software, basically did minor incremental releases, remaining essentially the way it was in 2001.  Wordpress has done better, yet still, the fundamental blog/cmslite experience remains pretty much as it was 4 years ago.  Photo gallery software, chat, etc. all remain pretty much as they were when they burst on the scene.

The user experience on most sites now is very segmented.  Comments are in one spot, while forum posts over here.  Most sites  don’t integrate chat, as it tends to remove us from the page view model on which our revenue streams are so often based.

We’ve patched together separate systems, and in virtually all cases, the seams are showing.  Clear lines of demarcation block logical points of information transfer.  Most of what happens isn’t real time, or anything close to it.  It’s a post then wait and click refresh experience for most of what we do.

That’s the point of entry for Google Wave, the new open source project that launched in private beta today.  It has real time communications, chat has both private/public components, that can take on the threaded view of a forum with real time updates, that can be presented as a forum, or a blog, or whatever you imagine.

You see the important thing here for a developer is that they’ve built the basic tools, but we can add whatever we want via their api.  To demonstrate this, they added Google maps integration.  Yet that bit could be a video, or even better a live video stream or a recorded application view (think Webex presentation), live photo gallery, or all of them.  All of which can be manipulated and edited real time by multiple users.

So what is this Google Wave, really?  It’s opportunity for us to FINALLY break out of the box, to really do something new and different, to for once rethink the way we do our sites.

I can’t wait…

Check out the abridged version of the video from the I/O conference to get a taste of what I’m talking about.

YouTube Preview Image

Wordpress 2.8.4 – Update Now

wordpress-logoThe folks at Automattic released a security update for Wordpress today due to a very specific bug:

…a specially crafted URL could be requested that would allow an attacker to bypass a security check to verify a user requested a password reset. As a result, the first account without a key in the database (usually the admin account) would have its password reset and a new password would be emailed to the account owner.

While this isn’t an incredibly nasty bug, it does affect the admin user, which many folks use as their only point of access to the system, which is poor practice.  On my customer sites, the admin user is never actually used by anyone (except for me, and only in an emergency).  Everyone gets a user specific account and that account has the right privelidges for that user.

Click the upgrade button now, or have your web guy/gal/poodle take care of it for you.

Tags: , ,

A Grand Diaspora – The “Conversation” Disappears in the Ether

One of the things that is most missed in the Social Media rush to “join the conversation” is that in many cases, by offering a plethora of places to get our content, we’ve turned the tables.  Our readers who used to find us now expect us to find them.  Even though I write on my blog, I’ll often get the comments for that post on my Facebook page, or via FriendFeed or Twitter, or on some other blog somewhere that quoted from my post.  So instead of my comments coming to me, right alongside my post, I need to schlep out into the great wide web and find them.

Think about where your content appears.  It may start on your blog, then it shows up on a myriad of social media platforms in which you participate, each with their own means of commenting or discussion and even, in some cases, yet another email function.  Let’s face it, in many cases, those commenting functions are ratholes.  You may not even see them for days or weeks, at which point, why would you even bother responding?

Look at the previous post here.  I had a great comment that came in via my Facebook account, but I had to do a cut and paste to pull it into my blog.  How 1998 that functionality is.

How about:

  • If social apps offered a “redirect comments to original publishing platform” option?
  • What if we had a function like a ping back that used xml-rpc to import a comment when it was made on your Facebook, or on another blog.
  • How about if readers thought to try to comment on the original article, instead of the summary?

I love comments, I love forum discussions.  The problem I have is that when you start to spread them out acrross many separate and distinct platforms, their value decreases.  The “conversation” is affectively split and disjointed, and we end up with a grand, yet failed, experiment.

Wordpress 2.8.1 Released

I really used to look forward to Wordpress updates, probably because there were so many things that needed to be fixed.  Now we’re at a point where it’s in very good shape, and, frankly, the interim releases are kind of boring.

Still, it’s good to see that I can finally click on automatic update, for either plugins, or the main software itself, and it actually does the update.

In other Wordpress news, they have a new developers survey out for 2.9 image handling feature prioritization.  My general sense as I filled it out was that there wasn’t anything earth shattering on the list.  Again, a function of a fairly well featured system.

The only area I can think of that I think really needs further development right now is the workflow, but honestly, it’s not as though its not working for me.  Simple workflow is good enough for my needs…but I know there are others for whom that simply doesn’t work.

So tell me, what do you think Wordpress needs in the future?

Wordpress Revision History to the Rescue

(Uh, Jeff, Kelly, move on, nothing to read here.  Nothing of interest to you at all…really…)

I had one of those moments today.  Mistakes were made.  Bad mistakes.  The “oh crap, I’m editing on the production site, not the qa or dev server” type of mistakes that immediately have you picturing your career dissipation light suddenly burning bright.  

So I noticed after working on this highly important site that I’d accidently overwritten something on the live site.  Yech.  

Luckily, as of version 2.6, Wordpress now has Revision History.  I’ve only used the feature a few times before, and then, only when I’d gotten to an unrecoverable point on a qa server.  So in I went, and there it was…the content I’d overwritten, waiting for me, like a girlfriend I’d done wrong…

Saved.  Career dissipation light dims to nothing.  

Thank you Wordpress…without that my next stop was going to be the Internet Archive…

Tags: , ,