Lijit

I've spent my Sunday morning mostly online. It's a lovely day, sunny and cool outside, and I've been wanting to get outside and do stuff. But I wanted to catch up online with some blogging and reading and such.

Which means that I've spent a bit of time struggling with the pathetic, slow, DNS-forgetful DSL service from Qwest I have at home. Every page view was taking ages to load. (How does Qwest even stay in business? Oh yeah, I forgot.)

And what's worse, among the slowest sites to load this morning was your humble hostess' own blog. And it wasn't just Qwest making things slow to start with -- it was the widgets. The slooowwwwww widgets. I'd sit there, watching the sun rise higher and higher while I wait for "Read" and "Transferring data from" messages in my status bar cycle through all the different services trying to load their widgets.

The. Widgets. Must. Go.

Into my feed-reader steps a new post from friend and pingVision colleague Greg Knaddison on how he just killed all the widgets on his blog. And rather than just rant about the woes of having page loads slowed down by widgets having to load from different servers in the far reaches of the virtual world, Greg has some useful advice for the widget-makers out there:

As I've pointed out, the problem can't be solved by "get faster" solutions like just speeding up the internet connections of users or making the servers that run the widgets faster. That would certainly help, but the "more files" problem means you are still limited to a few widgets.

The real solution, in my opinion, lies in solutions that are integrated into my site's software. Don't give me a flickr javscript widget - give me a flickrrippr module that pulls my photos into a local cache. Don't give me a comment plugin that takes years to load - create the "intense debate" by reading my comment rss and aggregating that information with some form of universal login so that my comments can be tracked from blog to blog (if I want). Having integrated applications you can take advantage of javascript and css aggregation/compression to reduce those files from 10 to 2. That helps.

Of course the problems with my solution is that 1) it requires lots of things like microformats that are only slowly picking up 2) site users will need powerful website building software that can be more difficult to install 3) some of these widget companies have "collect lots of data and do stuff with it" as a business model and they can do more of that without you knowing about it when they do it in this format.

Greg is dead-on. Maybe we can collectively "scratch our own itch" in the open source world (and in particular, Drupal) to help bring about widget reformation.

Meanwhile I'm going to rip out the widgets and put them into an "about me" post, so they are still there but don't drag down the entire site with every page load. I'm going to do that. Soon. Right after I get out and enjoy some of this gorgeous fall day.

Via my Lijit stats, I see that quite a few people are coming here searching for a solution of syncronizing or backing up Yojimbo without .Mac.

Alas I don't have an answer. I gave up and signed up for the .Mac service, despite their claimed "right" to snoop through or destroy whatever I put there. I'm using much more encryption on my entries now, that's for sure (and probably a best practice anyway).

I wish there were another answer. Alas....

Kudos to Boulder start-up Lijit for winning in the Internet category for showing innovation and creativity in the Boulder Valley.

And they were up against some well-known competition: Me.dium and Collective Intellect.

If you don't know what Lijit is about, scroll down and look at the sidebar here. It's the green search thingie. Don't be fooled! It's not just any search thingie!