A cell phone with a RSS button. (!)
Congrats to Kevin Marks on his new job at Google.
Here’s a great story…
Dave Jacobs is PKD survivor, a hereditary disease that destroys the kidneys. Both Dave and his sister Cher received kidney transplants in 2004. His younger brother, Brant, died from the disease. Dave has three sons and is raising his nephew — each of these boys have a 50 percent chance of having inherited the disease. So the Jacobs family is very well motivated to solve this problem.
Dave is healthy again, really — you should see the guy, it’s a real miracle. We go out to eat, go to baseball games, take long walks, and kid each other about stuff that doesn’t matter, and cheer each other on as we go forward. And Dave is doing some amazing stuff, which I want to tell you about today.
His new company, Silverstone Solutions, has developed software that automates something that used to be done informally, manually and inefficiently, and the result is new kidneys for people who, without them, would likely die. Here’s how the system works.
Suppose you have a friend or relative who wants to donate a kidney to you, but for some reason that kidney isn’t transplantable in your body (wrong blood type, for example). So you register with your hospital, and they enter your data into the Silverstone software. Another person has a friend with a kidney that’s incompatible for them, but works for you. And suppose your friend’s kidney works for them. Bingo. Two people survive where before none would. The software of course can handle three-way combinations, and so on.
They’ve spent a couple of years getting it to work, and have signed their first customer, California Pacific Medical Center in San Francisco. And today, Valentine’s Day, they performed their first transplant.
There’s no doubt that Big Dave survived his disease to find his purpose in life, to combine technology and knowledge with medicine and love, to save lives. I’m proud to know Dave, and honored to be among the first to tell this story.
A simple new feature, story pages now have a cookie crumb navigation trail at the top of each page, pointing to the day, month, year and entire archive. This way, when the story is indexed in a search engine, you can find your way back to the context in which the story appeared.
PS: I added a second new feature. Each paragraph on each story page now has a purple pound sign linked to a permalink for the paragraph, making it possible to point to individual paragraphs inside stories.
Things have been a bit slower here the last couple of days — I had minor elective eye surgery yesterday under general anesthetic, and it knocked me out pretty well. It seems to have been a success, had some problems with the retina in my left eye, still a bit wiped out from the experience, but overall feeling pretty well. Nothing like the surgery I had in 2002.🙂
Richard MacManus writes about Pipes. It has the chicken and egg problem, the same one every programming language has when its new, there’s not much interesting data to operate on. In this case, the target is the huge, rich base of RSS feeds, which is designed to work with one kind of aggregator, a River of News, and if you structured Pipes around that — a filtration process for a river, it might bear some immediate fruit, but its built on a different model.
It assumes that each feed can be dealt with as a procedure call, which according to the REST philosophers, it can, but in practice, feeds don’t take parameters, so they’re the least interesting kinds of procedures, like clock.now in UserTalk. Sure there are some verbs that build on that verb, date.month, date.year and date.dayOfWeek, but nowhere near as much as verbs that have rich parameter lists, which are like the gateways that Tim O’Reilly and Jon Udell are so excited about.
See XML-RPC for Newbies for background; a Pipes that could do XML-RPC could be interesting, esp because the Metaweblog API is an XML-RPC application, and is widely supported by blogging tools and CMSes.
In the RSS world, and therefore in Pipes, there’s no way to tell if items in two feeds are talking about the same thing. The best you can hope for is keyword serendipity, which all the demos so far do, and those make for unsatisfying demos, because you know you couldn’t deploy a useful app out of the concepts they illustrate. Very much like the early demos for HyperCard, Marimba, and my own Frontier.
Now it’s possible that a company like Yahoo, with its diverse flows of information, and nearly universal support of RSS, could add enough metadata to their feeds to be sure two items in different feeds were talking about the same thing, and then we’d be somewhere interesting. However at that point, I’d like a nice procedural language, something like Python’s treatment of XML-RPC, not the visually appealing but information sparse IDE that so many marketing people fall in love with, but not many programmers actually use.