Description
 

Welcome to my Blogroll
Important statements
Cool Tools
Our stuff
Current Collaborators
True Nerds to know
Open Technologies
In Rotation
Occasionally
Resources






July 2003
Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31    
Jun   Aug



Click here to visit the Radio UserLand website.

Subscribe to "Marc's Voice" in Radio UserLand.

Click to see the XML version of this web page.

Click here to send an email to the editor of this weblog.

Marc's Voice
Home LANs + Broadband + Devices

Tuesday, July 01, 2003
Bioartificial organs for transplant. Apropos of Xeni's post below regarding Dave Jacobs' quest for a kidney transplant, the new issue of Technology Review features a survey of the state-of-the-art in bioartificial organs, hybdrids of lab-built components and human cells:
"For now at least, they are external devices, and the cells inside them stay healthy for no more than a few weeks. Even such temporary support could be a boon for medicine, sustaining thousands of patients and enabling them to regain the function of their own organs or survive until transplant organs become available. But the real revolution will come with the development of permanent, implantable bioartificial organs. That will require new materials that allow the cells to receive nourishment from the body but still protect them from attacks by the recipients’ immune systems. Such devices are years from fruition..."

With the United Network for Organ Sharing counting more than 80,000 people waiting for transplants in the US alone, time is of the essence. Link Discuss [Boing Boing Blog]

The PKD Foundation is the "only organization, worldwide, devoted to improving clinical treatment and discovering a cure for Polycystic Kidney Disease." [Scripting News]

Whether it bio, cyber, analog or digital - it would be REALLY amazing - if all this causes some good to happen.

RSS, Echo, Wikis, and Personality Wars. The weblog world has taken the 4 elements of organization from mailing lists and usenet -- overall topic, time of post, post title, author -- and rearranged them in order of importance as author, time, and title, dispensing with topics altogether. (Choosing a formal topic, as Many-to-Many does, is both optional and rare.) This "author-first" organization gives the weblog world a huge boost, as the "Who said what" reputation system we all carry around in our head is a fantastic tool for organizing what we read, as well as acting as a kind of latent bozo filter.

"Author-first" has a downside, though, which is that in some areas, personality is a bad proxy for quality. Exhibit A is the standard wars over RSS, which have been driven by personality -- Mark says one thing, Dave a second, Sam a third, and the whole thing takes on the quality of the "Britney dates Justin/Britney dumps Justin" headlines at the checkout counter.

So Sam Ruby, in an effort to rescue the idea of a syndication format from this new danger, the personality-centric standards war, has rounded up The Usual Suspects and is corralling them into the design of a new standard, currently called Echo, that is "100% vendor neutral" (read: unconnected to personality.)

And the Great and the Good of the weblog syndication world are doing this work...in a wiki. There are lots of good reasons for using a wiki, of course, instead of a trackbacked weblog conversation. Though both weblogs and wikis support conversational patterns, weblogs are "conversation as published comments" while wikis are "conversation as shared editing." Weblogs tend towards polarized or divergent views, while wikis tend towards convergent ones, which is just what you want for a conversation around standards.

But there is a second reason, under the surface but possibly more important -- wikis denature personality. Echo exists not because there are things wrong with the RSS markup -- there are, but they could be easily fixed. Echo exists because there are things wrong with the RSS process. RSS is having not a technological crisis but a constitutional one, where who decides what concerning RSS is not clear, and will never be clear, because the people doing the deciding don't even see themselves as being part of a decision making body.

Ruby is attempting to cut that Gordian knot by launching the new standards work in a wiki. When the problem with the process is social, the solution should be social too: Wikis are a much more radical re-arrangement of the usenet/mailing list principles. The two key aspects of wiki organization are Page Name and Now. Page Name is someplace between a subject line and a formal topic -- it lasts longer than a subject line, but isn't permanent as it can always be re-factored. And Now is what time it is on any given wiki page -- the page itself reflects the history of changes to date, so Wiki Now is always the best approximation of consensus view.

Wikis have no strong concept of author -- people can sign their work if they like, and can sometimes register, but additions and edits don't have to be signed, nor does any particular addition enjoy special status or presumption of permanence. There is no overall topic required for a wiki, though one can be declared or emerge. Reverse chronological arrangement is a second order view, either of revisions to a given page or in the Recent Changes list. But the wiki pages themselves are organized by Page Name and Now.

By doing this, Sam seems to be saying "You can hold forth in your blog all you like, but the work is here. Everyone is welcome, no one's words matter more or less, and no one's words are sacred. Rough consensus will be reached by hammering out the ideas on the wiki pages. We will re-factor as we go, see what emerges, and work from there."

By doing this, Sam is creating a single conversation -- you have to be there to play. He is making the conversation open to participation but resistent to bloviating. And he is forgoing any editorial function of his own, pace wiki gardening, which is open to everyone else as well. Who knows if this will succeed as a pure standards effort, but as an attempt to convene a concrete conversation while avoiding personality wars, it has already generated an enormous amount of valuable input and a huge amount of good will.

Most wikis that matter don't operate on a public scale, being used for coordination of small and focussed groups. (IAwiki.net is about the largest I've seen.) Most wikis that operate on a public scale don't have much impact -- the social facts of the wikipedia are far more interesting than the content itself. The Echo wiki, though, is an interesting experiment in when, why and how to use a wiki to convene a large and heterogenous group to deal with a thorny and contentious problem, as well as possibly providing an antidote to personality as an organizing principle. [Corante: Social Software]

Put your money where your mouth is - nothing wrong with actually using the technology we preach about.  I met my wife on Match.com - so I feel like I'm uniquely qualified to talk about cyber dating.

Clay is backing up the need for ThreadsML.  This Wiki conversation is an incredible new form of interaction and collaboration. Now imagine being able to start OTHER kinds of new collaboration - starting off in an email exchange, migrating to a message board/mail list - then shifting to Wiki status - only to end up as an on-line outline - re-entrant at any time.

That what ThreadsML is all about.

 Adam Curry | iLife 

iPhoto log tool. Can't get it to work myself just yet, but the idea is killer: iPhoto posting to any weblog supporting the metaweblog api. Kewl [Adam Curry: Adam Curry's Weblog]

Coolio.  This is a recursor to where iLife is going.  Expect iCommunity soon.

 Echo | Mark Pilgrim | RSS 2.0 

Mark Pilgrim is making total sense. If he does his work openly we'll all learn a lot because Mark is a great teacher. [Scripting News]

52 comments and growing.  This is fun!

Come on everybody, let me hear you scream: Leave RSS alone!

"BigDave" needs kidney transplant, bloggers team up to help. Dave Jacobs needs a kidney transplant. A veteran of Microsoft, Macromind, Marimba and Macromedia, where held executive positions in marketing and technology management, he's a former Fetish columnist at Wired magazine. Dave Winer, Marc Canter, Doc Searls, and others are joining blog-forces to get the word out, and help him find a donor:
There aren't many things we need in life to survive -- food, water, a warm place to rest, that's about it. My good friend, David Jacobs, 47, is different. He needs a new kidney to survive. He's suffered for a decade with a degenerative condition called polycystic kidney disease or PKD and has been on the kidney transplant waiting list for two years.

The past two months have been full of problems and complications and a couple of days ago, Dave he told me he was going to take his appeal for a kidney donor public. Until now he’s been extremely private about his condition, but he is hoping to not only find a potential donor for himself, but to raise awareness for organ donation in general. When he asked if I would help, of course I said yes.

Link to Dave Winer's post, Link to Marc Canter's post, Discuss [Boing Boing Blog]

And from Adam Curry....

  big dave. I have shared the holy herb with Dave and I pray for him daily to find an 0+ kidney donor.
[Adam Curry]

Quick, what's your blood type?.

If it's O, or you know somebody generous whose blood type is O, read the story of Dave Jacobs.

In fact, read it anyway. He may die if you don't.

Dave needs a kidney. He's dying for lack of one. His brother has already died. He and his wife have two kids and another on the way. They're also caring for the son of his late brother.

Spread the word.

Doc Searls]

Dave is here now - playing with Mimi. Thanks to Scoble, Doc and Xeni - to keep this meme going.

Readying Gateway's post-PC future. CEO Ted Waitt explains why he wants to move the company away from its roots as a PC maker. He's tried twice before to pull off a new strategy. Will the third time be a charm? [CNET News.com]

Gateway is positioning itself as a 'branded integrator' - which means they've taken the digital convergence pill and swallowed it deep and true.  We now have Microsoft, Sony, HP and Gateway leading the way.

Hopefully somebody there is gonna ask themselves "what software can we use to differentiate our offering?"

That's where 'we' come in.

Supernova.

I hate it when two conferences collide. Worse when there are three. But that's what's happening next week with The O'Reilly Open Source Convention (OSCon) in Portland, Pulver's Supernova in Washington, D.C. and the Burton Group's Catalyst conference in San Francisco.

OSCon runs July 7-11, Supernova runs July 9-10 and Catalyst runs July 9-11. Slipping back and forth between the three isn't as easy as it was to do the same between OSCon and in San Diego two years ago. (Here are notes from Craig, Dave and myself, back then.)

OSCon is a professional necessity for me (since I work the Open Source beat). But I want to put in a plug for the other two — and Supernova especially. Decentralization is the theme, and Kevin is driving the conversation very nicely with only one show under his belt so far.

Of the three conferences, I believe Supernova has the most need for support, and the most important topical focus as well.

I say that because I believe decentralization is THE theme for our times. It's what the Net and the Web were about in the first place. It's what Cluetrain was about. It's what the successes of Net-roots movements like MeetUp, MoveOn, DigitalConsumer.org, AOTC, Warblogging, Peaceblogging and the Howard Dean campaign are all about. It's what blogging was about, too.

I say was because I'm concerned right now that blogging risks centralization. A year from now, don't be surprised if everyone with an AOL, an MSN or a .Mac account automatically has a blog, and if those blogs use noncompatible means to interoperate with each other. Just like we've seen with instant messaging since the beginning.

And don't think that other companies with an interest in blogs, such as Google and IBM, won't find their own ways to defeat interoperation for both competitive and idealistic reasons, no matter how well-intended they may be. They want to make better blogging tools, sell better blogging back-end systems, better ways to put advertising on blogs and better ways to do other stuff. But better isn't always best. Often (though not always) means better everything: including protocols, formats, and standards that are bettered all the way to isolation and well-rationalized noninteroperability. Instead of an open market with lots of interop, you've got a bunch of isolated silos. It's not a long trip, and it's often travelled unconsiously.

Or consciously.

Apple has conciously, and astutely, played this game for years. Its iChat AV system, for example, is really wonderful. It does a jaw-dropping job. I've been blown away by the quality of its audio, its video, it's ability to employ devices like ordinary webcams and camcorders. But it only interoperates with itself. Maybe one day it'll interoperate with other chat/IM systems. But it's in Apple's interest to not interoperate right now. Just like it was in Apple's interest to launch an MP3 player that didn't interoperate with anything other than the company's own host systems. To its credit, Apple eventually made iPod work with Windows (in a way that left it open to working with Linux as well). But it still used noninteroperability as a strategy. Credit where due: iChat will drive Apple CPU sales, big time, in large part because it's non-interoperable. Even while Apple has done a terrific job of driving open interop standards like USB and FireWire. If you see the strategy, the irony goes away.

Back to blogging. As I understand them, standards like RSS and XML-RPC, as originally conceived, and as still largely implemented, have the virtue of POGE: the Principle of Good Enough. Big-vendor-driven standards like SOAP have a way of going off into non-interoperable directions, based on the compeitive ideals of their participants.

I know Dave Winer has received some heavy shit for being a "control freak" and worse. But to me it seems he's just trying to protect POGE standards like RSS and XML-RPC from those who seek to improve or replace them.

Every category is a coal mine. We need our canaries. We may not like the sounds Dave makes when he chokes on gasses the rest of us can't smell, but we owe it to ourselves to listen.

Seems to me Wes was listening when he wrote this:

When one side is committed to worse-is-better and the other to pedantic perfectionism, a fork is the best thing that can happen.

The follow-up questions for me are, 1) Will perfectionism out-muscle worse-is-better because it's better-funded? And, 2) Where will it go if it succeeds? Don't assume that perfectionism will make a naturally better world, or build a better Web. Perfectionisms are highly arguable, and arguments of the perfectionist sort result in all kinds of forkages that disperse market power, especially for the independent developers who create and develop categories that are open to anybody and everybody.

For context, let's go back and visit the NEA principles that the Net imperfectly embodies:

  1. Nobody owns it.
  2. Everybody can use it.
  3. Anybody can improve it.

Job One for the world's category canaries is making sure that the pursuit of #3 doesn't defeat #2.

Nothing could be more important to decentralization than that.

[The Doc Searls Weblog]

It looks like I'm gonna miss SuperNova as well - and I'm bummed.  I would really have loved it slugging it out with those 'inside the beltway' types.  That's Kevin's old world.  My best wishes go out to Kevin and the East Coast crowd.  I plan on participating virtually - as best I can.

UPDATE:  Doc updated his post - so I copied that additional bit in here.


Updated: 9/17/2003; 12:22:47 PM.