I’m please to see Arik Jones keeping the Failbox torch burning – in a post on the need for a smarter email client
And yes, he mentions Cullect as an example of a successful recommendation system. Guaranteed to catch my attention.
About time. And product. And being more deliberate.
I’m please to see Arik Jones keeping the Failbox torch burning – in a post on the need for a smarter email client
And yes, he mentions Cullect as an example of a successful recommendation system. Guaranteed to catch my attention.
As a kid, I watched The Right Stuff more times than I can count.
It’s a fun story about the beginnings of the NASA space program and test pilots. But mostly it’s about egos.
Lately, the opening’s been stuck in my head.
“There was a demon that lived in the thin air; they said anyone who challenged him would die. Their controls would seize up, their planes would buffet wildly, and they would disintegrate. The demon lived at Mach 1 on the meter.” – Tom Wolfe, The Right Stuff.
Over at the First Crack Podcast, I ask Tim Quirk about the forthcoming Wonderlick album ‘Topless at the Arco Arena’, the pay-what-you-want models, and music’s changing landscape. [mp3]
I’ve been a fan of Tim Quirk’s music for 20 years – easy. The playful melancholy in throughout his songwriting continually resonates with me. When he announced the new Wonderlick album was in the works and available for ‘name-your-price’ pre-order – I jumped on the opportunity.
When I started hearing about how successful the campaign was – I asked Tim if he’d talk about the album and the campaign for the podcast.
As he mentions in our conversation, the common theme through the 16 tracks is the exploration of an experience he first wrote about in 2002:
In the 16 Topless at the Arco Arena tracks, Tim, with Jay Blumenfield, ask everyone involved what they got out of the experience.
My top 5 Wonderlick – Topless at the Arco Arena tracks:
Download: Listen to Wonderlick’s Tim Quirk on Truth Through Music [36 minutes]
5 Stars
4 Stars
3 Stars
My Kindle‘s been dead since yesterday. My initial thought was that maybe it no longer liked being charged from the USB hub. I plugged it into the wall and the charge light didn’t come on.
Hmmm.
Thankfully, it’s USB so I’ve got plenty of cables lying around to test.
I grabbed the USB cable from my Nokia e71, and the Kindle’s charge light is orange.
UPDATE May 06, 2009
I’m on the phone with Amazon’s Kindle Customer support right now. It’s not as immediately friendly and helpful as the “It would be easier to help you if you called us.” email made it sound.
Even before I described the issue, I had to justify who I was (irrelevant to starting the conversation) – that’s always off-putting and opposite from how people actually interact face-to-face.
Now I’ve been transferred to a Kindle Specialist (I thought that’s who I called originally). Once she picked up – it was resolved very smoothly in less than a minute.
Nice work Amazon.
There’s lots of silly URL shorteners.
Some of my favorites – not just because of their silliness, but because they offer some interesting potential;
Tonight the Wege added another non-URL shortener to the list.
DickinsURL
DickinsURL takes your url and applies a sentence from one of Charles Dickins’ works as the key.
“Enter an ugly URL above and hit convert button. Soon you will be faced with beautiful words of Charles Dickens.”
Unfortunately – if you take a close look at the URLs it generates – the Dickin’s lines are optional!
@highwind – if you drop the numeric key, I’ll give you the #2 slot. 🙂
There’s lots of push lately in the tech community to chase the dragon of real-time.
I do see real-time it most valuable during events that I’m not able to attend in person (the recent IgniteMpls event comes to mind immediately).
Even then, there’s always delay.
Each second delay brings an opportunity to filter for relevance. That’s the biggest win of our increasing use of online services for social interaction. We trust and filter each other [1] [2] [3] [4][5]. While these processes take time, they magically transform a firehose of information into an energizing conversation over a couple of beers.
A friend of mine has opted for a 48-hour delay on his incoming stream. Two days is about how long it takes for daily drama to dissipate. And if it doesn’t – it’s significant, if not relevant.
I was reminded of this earlier today when I received a forwarded email. The email was terribly partisan, terribly incendiary, terribly xenophobic, terribly incoherent, terribly panicked about the economy and the changing face of their community. They even invoked Godwin’s Law2 completely out of the blue.
I received it today.
So I assumed it was written recently – say within the past couple days.
Not at all.
August 2008 it says.
Really?
On second read: apart from a sentence or two, it could have been written in August 2001. Or August 1981. Anytime when significant changes in the American zeitgeist were afoot.
Quite a bit has happened since last August. I can only assume a significant percentage of the people this diatribe was directed at are no longer in positions of power. Do these issues reflect anything 9+ months later?
If this were realtime – no.
Yet, I received it today, and the author’s name has 18,200 Google results2 – all pointing to this identical rant.
Whether or not it reflects the current feelings of the author or their community, this rant has continued to inspire a portion of the American populace to share it with each other.
1. I’d much rather people invoked Steiner’s Law instead.
2. As a comparison, my name has between 18,700 and 32,100 results depending on spelling.
URLs are consistently the least usable aspect of our interaction with web-based information services – which is terribly unfortunate considering their prominence in how we access, share, and interact with these services.
With that in mind, let’s take a look at how Twitter’s URLs could be more usable – by either being more logical, more readable, more share-able, or a combination of all 3.
Here’s a standard Twitter URL:
http://twitter.com/garrickvanburen/status/161277022
Let’s break this apart:
/garrickvanburen
The person’s Twitter account we’re interested in – very clear1.
/status
I’m not sure what ‘status’ is – seems like a very system-centric term. For the sake of this conversation, let’s assume it’s a synonym for ‘note’, ‘message’, ‘news’, ‘memo’, or the collection of things I publish at Twitter.
/161277022
This is the individual ‘status’ identifier. Presumably, it’s the primary key ID of this ‘status’ within all the ‘statuses’ in Twitter’s database – making this ‘status’ ID global – not nested within ‘garrickvanburen’. Again, very system-centric and kind of backwards – if we assume URLs should go from largest logical entity to smallest nested entity.
A RESTful URL structure would dictate the following:
/Plural Version of Resource Name
/Individual Resource Identifier
/Plural Version of Sub-Resource Name
/Individual Sub-Resource Identifier
/(et. al.)
If we mapped Twitter’s existing structure against this model we’d have:
http://twitter.com/people/garrickvanburen/statuses/161277022
We can see, Twitter’s URLS aren’t exactly RESTful, and since they’re not – let’s look at some ways to make them more logical.
Proposal 1: Logically Long
http://twitter.com/garrickvanburen/twitter-suggestion-put-the text-of-the-tweet-in-the-tweets-permalink.
This is the most usable and readable for both people and machines. It has the huge benefit of having the entire message in the URL (the mind reels with possibilities). WordPress does a great of making legal URL strings out of a weblog post’s title.
Benefits: Highly-readable, logical nested structure, great for search engines
Detriments: Long (though Twitter’s built-in limits provide a maximum length)
Proposal 2: Globally Short
http://twitter.com/1612770222
This is akin to my WordPress URL Shortening Hack
Benefits: Short
Detriments: Almost no information provided makes this the least usable and equivalent to the shortened URLs you find throughout Twitter.
Proposal 3: Personally Short
http://twitter.com/garrickvanburen/5954
Where 5954
is the number of the individual message in the pool of all my messages.
Benefits: Short, encourages numerically navigating through a person’s messages.
Detriments: Numbers are always less usable than words.
The great thing about these proposals is they’re not mutually exclusive. In fact – different URL structures bias different usages and contexts. In the same way different formats (HTML, RSS, XML, Text-only, etc) providing different presentations of the same webpage to different devices are more usable – different URL strings pointing to the same webpage are as well.
1. Identi.ca’s URL structure doesn’t include the person’s name [example]- making the number less confusing, but the URL itself less usable.