February 2008


A few years back I realized that my knees and ankles were hurting because I’d put too many miles on my running shoes. No permanent injuries resulted, but a friend who outran his shoes wasn’t so lucky, and he’s got back problems for life.

This is a business opportunity. If you’re a runner, spending $100 every six (or even three) months is infinitely preferable to injury. You’d think that shoe sellers would make it easy to do that, but they don’t. I’d happily authorize regular replacements, but nobody’s ever offered me that option.

Partly I guess this is a failure of service-oriented thinking. My local seller thinks service means taking good care of me when I walk in, and he does. But I think service should also mean helping me manage a lifelong shoe-replacement regimen, and that notion seems not to have sunk in.

Of course planned obsolescence also gets in the way. Once I find a shoe I like, I try to stick with it, but the manufacturers won’t let me. The model I know works well usually isn’t available next time around, so I have to try something different. That’d complicate any kind of subscription service.

I can sort of understand the difference between, say, prescription drugs, which are commodities that I can replace on a subscription basis, and running shoes, which are both fashion items and (supposedly) evolving technologies. But for me, and maybe for a lot of people, what I really want is to regard the running shoe as a commodity I can replace on a subscription basis.

I wonder what else belongs in this category: Products that sellers don’t want to commodify, but that if managed this way would produce recurring revenue and create the opportunity for lifelong service relationships.

For this week’s ITConversations show, introduced by special guest introducer Lynne Windley, I got together with Valdis Krebs, who’s been mapping and analyzing social networks since Mark Zuckerberg was in diapers.

I can’t remember how I first got to know Valdis, but this snippet from a 2004 interview — for an InfoWorld cover story on enterprise social software — gives you a sense of what he does and how he thinks:

IW: Social network analysis can reveal that highly connected people are more valuable than the org chart or salary plan suggests. Is this becoming a factor?

VK: Yes. I did a project with an investment bank, and they took into account who was most valuable in getting a deal done, and factored that into the bonus. I’ve had execs inside and outside IBM saying, “If this data is true, then I’m not paying the people who bubbled up to the top what they’re worth.”

IW: Does it cut the other way, too?

VK: We wouldn’t take a job that we knew would lead to a resource action.

IW: Resource action?

VK: Layoff.

Now that everybody in Silicon Valley has become an armchair social network analyst with an opinion about the nature and uses of the “social graph” I thought it’d be useful to check in with Valdis for a long-range perspective on current trends. Bottom line: He thinks social networks that you have to explicitly join are artificial and ungraphable. But we agreed that these first-generation online social networks are fostering a culture of self-disclosure, and that they may lead to a second generation of more naturalistic systems: bottom-up, ad-hoc, peer-to-peer.

I’ve interviewed a couple of people who attended and/or spoke at last year’s Code4Lib conference: Art Rhyno, and Beth Jefferson. Code4Lib brings together IT-oriented librarians, and library-oriented IT folk, to create what seems like a truly unique event. I’m really looking forward to attending Code4Lib 2008 next week in Portland, where, as an adopted member of this strange tribe, I’ll be giving a talk on Thursday morning.

Back in October I interviewed Sean Nolan, chief architect for HealthVault. Now he’s launched a blog, and in his latest post he writes:

  • Microsoft will make the complete HealthVault XML interface protocol specification public.
  • With this information, developers will be able to reimplement the HealthVault service and run their own versions of the system.
  • Microsoft will irrevocably promise that we will not make patent claims against you for implementing the specification, subject to the terms of the OSP.

Excellent! My take on HealthVault is that it’s doing the right things in the right ways. This announcement confirms that.

People are trying, once again, to kickstart the music scene here in my town. The other day I received two emails, each containing a schedule for a newly-activated local venue. In the past, I’ve advised folks to add this information to Eventful, which in turn feeds my my local aggregator. That hasn’t happened much, and when I sat down and did some of the data entry myself, I could see why. It’s such a drag!

There are really two very different scenarios for managing event data online: one personal, the other public. On the personal front, using services like Evite or Windows Live Events, you’re doing a single event: a meeting, a birthday party. It’s OK to fill in a form field by field.

But for public events, venue operators will typically want to do batch entry. And when you’ve got a schedule of dozens of events, it’s painful to decompose everything into fields and pump them into forms.

Here’s a piece of one of the schedules that was emailed to me:

March 15, 2008 (Saturday) Chris Fitz Band
March 20, 2008 (Thursday) Blues Jam w/ Otis Doncaster
March 22, 2008 (Saturday) Groove Theory

It was quick and easy for the author of that email to write out the schedule in that way. But it was really slow and difficult for me to input the same information to Eventful. Even though venue operators are highly motivated to do it, I can see why they often don’t.

So here’s how I speeded things up. I started with a template for a URL that invokes the Eventful API:

http://api.evdb.com/rest/events/new?app_key=XX&venue_id=XX&title=XX&start_time=2008-XX-XX+20:30

Then I made a bunch of copies, and tweaked them like so:

…title=Chris+Fitz&start_time=2008-03-15+20:30
…title=Otis+Doncaster&start_time=2008-03-20+20:30
…title=Groove+Theory&start_time=2008-03-22+20:30

Because all the events start at 8:30, I only need to adjust the title, month, and day for each record. It’s not only way quicker and easier to enter data this way, it’s also quicker and easier to check and correct. When I was done I put the email into one window, the new file into another, and compared. Corrections here are way easier than corrections that require you to navigate to an online database record and edit it in a form.

Finally I inserted the curl command in front of each record, yielding a script that invokes the set of URLs:

curl http://api.evdb.com/ … title=Chris+Fitz&start_time=2008-03-15+20:30
curl http://api.evdb.com/ … title=Otis+Doncaster&start_time=2008-03-20+20:30
curl http://api.evdb.com/ … title=Groove+Theory&start_time=2008-03-22+20:30

I saved this script as eventful.cmd, ran it on the Windows command line, and produced this result.

Now clearly this method is too geeky for a typical venue operator. But an online service like Eventful could smooth out the rough edges. I can easily imagine an unstructured input form that includes a template like the one I’ve shown here, invites people to copy and tweak it, and runs a batch insertion. It would need to let people preview the results before committing them, but that’s doable.

It seems to me that a lot of information systems expect civilians to do per-item data entry, but not batch entry. For that, they provide APIs for geeks to use. But as we see here, these two styles of data entry aren’t necessarily very far apart. And by applying a bit of Wiki-like inferencing to a more English-like script, they could be brought even closer.

The friction of data entry remains the single largest obstacle to bootstrapping the data web. Efforts to overcome that friction, and reduce the distance between what civilians can do with forms and what geeks can do with scripts, could make a huge difference.

This headline from Adrian Holovaty’s blog speaks volumes about the state of online data in 2008: EveryBlock hiring a Python screen-scraping expert. The recently-launched EveryBlock, a generalization of ChicagoCrime.org, extends that model to other cities and to a broader range of data types. I interviewed Adrian this week for an upcoming ITConversations show, and he confirmed that while some structured data sources are available from the first three EveryBlock cities — Chicago, San Francisco, and New York — the bulk of the data comes from scraping web pages.

One day soon, the person who lands that job will find himself or herself having this converation at a cocktail party:

Friend: So, what do you do in this new job?

Screen Scraper: I write software to extract data from websites.

F: Where does the data come from?

S: It’s in a database. The website’s software reads the database and turns it into web pages.

F: So somebody got paid to write software to turn the database into web pages, and now you’re getting paid to write software that turns those web pages back into a database?

S: Yeah, basically.

F: So if they just gave you the database you’d be out of a job?

S: No. I’d have a much more interesting job. I’d be able to spend more time finding useful patterns in the data, and writing software to enable other people to find useful patterns in the data.

The irony is that I’d be great at that job. For me, web screen-scraping provides the kind of challenge that other people get from, say, solving crossword puzzles. But it’s not the highest and best use of anyone’s time.

Data friction can be intentional or not. When it’s intentional, you might have to file a FOIA request to get it. But in a lot of cases, it’s unintentional. The data is public, and intended to be widely seen and used, but isn’t readily reusable.

Consider the following two restaurant inspection records for Bully’s Deli in New York:

1. in the NYC Department of Health website

2. in EveryBlock

It’s the same data, from the same source, but EveryBlock makes better use of it. In the NYC website, you can search by ZIP code and number of violations. In EveryBlock you can search more powerfully, and you can ask and answer questions that matter to you. Maybe you care about shellfish. Have any Manhattan restaurants been cited recently for use of unapproved shellfish? Yes: five since January 21.

What EveryBlock is doing is completely aligned with the interests of the NYC Department of Health. Tax dollars are paying for those restaurant inspections. The information is published in order to make New York a safer and healthier place. It’s great to have this data available in any form, and it’s great to see EveryBlock adding value to it.

Now it’s time to grease the wheels.

Here’s one way that can happen. An enlightened city government can decide to publish this kind of data in a resuable way. I’ve written extensively about Washington DC’s groundbreaking DCStat program which does exactly that. I can’t wait to see what happens when EveryBlock goes to Washington.

But city governments shouldn’t have to go out of their way to provide web-facing data services and feeds. Databases should natively support them. That’s the idea behind Astoria (ADO.NET Services), which is discussed in this interview with Pablo Castro. If the NYC Department of Health had that kind of access layer sitting on top of its database, it wouldn’t put EveryBlock’s screen-scraper out of a job, it would just make that job a whole lot more interesting and effective.

For this week’s ITConversations show I interviewed Joel Selanikio — a pediatrician, former CDC epidemiologist, and co-founder of DataDyne, a non-profit consultancy dedicated to improving the quantity and quality of public health data. DataDyne’s EpiSurveyor is:

…a free, open source tool enabling anyone to very easily create a handheld data entry form, collect data on a mobile device, and then transfer the data back to a desktop or laptop for analysis.

I’ve actually interviewed Joel once before, but an audio glitch torpedoed the podcast. I did, however, rescue chunks of that interview which I published as a transcript on my blog.

The launching point for this interview was an article Joel published, at the BBC News site, entitled The invisible computer revolution. Joel wrote:

The question we should be asking ourselves, then, is not “how can we buy, and support, and supply electricity for, a laptop for every schoolteacher” (much less every schoolchild), but rather “what mobile software can we write that would really add value for a schoolteacher (or student, or health worker, or businessperson) and that could run on the computer they already have in their pocket?”

Joel’s point, which was also a central theme of my conversation with Ken Banks, is that SMS is the only pervasive data network in places like sub-Saharan Africa. It can, and should, be pressed into service in ways that don’t occur to those of us swimming in an ocean of high-speed Internet connectivity.

You wouldn’t think that 140-character messages would be a useful way to deliver, say, medical information — at least, I wouldn’t. But then, even for those of us with bandwidth to burn, Twitter is demonstrating all kinds of unexpected uses for SMS.

A publishing system optimized to deliver documents to SMS readers wouldn’t be of interest to those of us who can easily browse the web. But it would be a big deal to billions who can’t.

On Sunday, in a New York Times story about Popfly, John Markoff wrote:

Because the company chose to design Popfly using a Microsoft Web graphics and animation technology called Silverlight, it will be treated with suspicion by an Internet universe that is increasingly committed to open standards.

Disclaimer: I work for Microsoft, and John Montgomery, who leads the Popfly project, has been a friend since our days together at BYTE. That said, I think this overstates Popfly’s relationship to Silverlight. Although the Popfly designer runs in Silverlight, mashups created in Popfly don’t require it. Most are just made of plain old HTML and JavaScript.

Elsewhere in the article, this quote from Tim O’Reilly appears:

Popfly shows me that Microsoft still thinks this is all about software, rather than about accumulating data via network effects, which to me is the core of Web 2.0. They are using Popfly to push Silverlight, rather than really trying to get into the mashup game.

Silverlight, as I’ve said, isn’t Popfly’s focus. I do agree that Popfly doesn’t operate in the cloud in the same way as, say, Yahoo! Pipes. While the article doesn’t mention Pipes, I often hear Popfly and Pipes mentioned in the same context. Both are mashup creators, but they are architecturally very different — in complementary ways. Because Pipes is a great example of data-oriented network effects, and because I’ve sometimes confused myself about the differences between Popfly and Pipes, it’s helpful to spell them out.

Mashup engine

Popfly’s mashup engine is a hybrid. There’s a service running in the cloud, but your browser can do a lot of work too.

Pipes’ mashup engine lives entirely in the cloud.

Sharing and discovery

Both systems provide a cloud-based environment for sharing and discovering mashups, and the components of mashups.

Inputs

Both systems can mash up data flowing from a variety of services on the web, including those that produce RSS feeds and other kinds of XML outputs.

Outputs

Popfly ends at the glass. The output is an HTML/JavaScript page or widget that renders in your browser. Although the components used to produce that output live in the cloud, the final result ends in your browser and isn’t available for downstream processing in the cloud.

Pipes can keep going. The output is a data feed that may or may not drive a browser-based display. But even when it does, the output is still available for downstream processing in the cloud — for example, as RSS.

Programming

In Popfly, you do basic stuff with a special-purpose visual programming language that runs in the cloud. You do advanced stuff with JavaScript running in the browser.

In Pipes, you only use a special-purpose visual programming language that runs in the cloud.

It gets confusing, even to me, because you can sometimes use both systems to achieve the same result. Consider this FluxnetTowers mashup in Popfly, which maps the locations of a worldwide network of C02 flux sensors. I just now made a simplified version in Pipes. I’m sure it’s possible to reproduce the annotations shown in the Popfly version. But from my perspective it’d be harder, because Pipes lacks the general-purpose programming available in Popfly thanks to JavaScript.

Suppose you wanted to include that same tower data in a widget on your WordPress blog, though. Here, Pipes would be the choice. WordPress lives in the cloud, and so does Pipes, so you can make Pipes produce a feed that WordPress consumes. But you couldn’t use Popfly in this scenario because a cloud-based service like WordPress can’t access the output of Popfly’s browser-based mashup engine.

Pipes likes to aggregate, transform, and filter data feeds within the cloud, and can produce a few kinds of renderings in your browser. Popfly likes to aggregate, transform, and filter data feeds from the cloud, and can produce arbitrary renderings in your browser. They’re complementary because Popfly can consume and render data feeds coming from Pipes.

Reacting to a Washington Post story on crime in Second Life, Gardner Campbell is troubled by calls for increased surveillance in virtual worlds. But while the notion of being watched by the authorities is as creepy in cyberspace as it is in the real world, we pay less attention to another kind of surveillance. Whether I am piloting my avatar through Second Life, or walking around in my hometown, I am myself a watcher who can, increasingly, record what I see. Whether the authorities surveil or not, we’re doing it to one another.

The funniest screencast I ever made was this snarky 3-minute video report on an IBM press conference I attended in Second Life. It’s a side-splitter, really, you should watch it, and yet it makes me slightly uncomfortable. Anyone in Second Life can, at any time, switch on a virtual movie camera and record everything that’s happening. And there’s no indication of that, nobody sees a camera.

As a teenager, I loved taking candid photos with my dad’s 35mm Exacta. At one point he told me you can get a side-looking lens so people won’t know they’re being photographed. At that point I started to think about the aboriginal notion that a photograph can steal a bit your soul. I’ve been conflicted about candid photography ever since.

Last week I was in the Alewife station on Boston’s Red Line, and saw something I’ve always been curious about. The escalator was completely disassembled for repair. Here’s what the steps look like:

And here’s a worker replacing the rollers on the giant bicycle chain that drives the thing:

As I was taking this shot, one of the workers joked about how I might be a spy for the MBTA, checking up on their work. He was mostly, but I think not entirely, kidding. It was a slightly uncomfortable moment.

Collectively, all of us now wield immense powers of surveillance. Whether the subjects of that surveillance are avatars or real people is beside the point. It isn’t necessarily the authorities who are doing the surveillance. We are doing it to one another. It happens every time somebody is tagged in a photo on Facebook or Flickr. It gets easier all the time.

Is this a good thing or bad thing? A bit of both, I think, hence my inner conflict, and my eternal fascination with David Brin’s The Transparent Society. Who will watch the watchers? The question becomes very different when we are all watchers, recorders, and publishers.

Hugh McGuire recently pointed to a New Scientist blog entry that begins:

A bunch of sources are reporting on a University College London study into how people born after the arrival of the internet – sometimes dubbed the Google generation – handle information. The top line is, they’re not very good at it.

The link points to a press release, entitled Pioneering research shows ‘Google Generation’ is a myth, which summarizes a 35-page report in PDF format. That report in turn summarizes a whole series of “work packages” (more PDF files) identified as the full project documentation.

Let’s trace one of the assertions made in the report, as retransmitted by Information Week:

Also, it’s not true that young people pick up computer skills by trial-and-error. “The popular view that Google Generation teenagers are twiddling away on a new device while their parents are still reading the manual is a complete reversal of reality,” researchers said.

Fascinating. I’d like to know more. How did the researchers arrive at this conclusion? Here’s the piece of the report summary that Information Week sourced:

They pick up computer skills by trial-and-error

Our verdict: This is a complete myth. The popular view that Google generation teenagers are twiddling away on a new device while their parents are still reading the manual is a complete reversal of reality, as Ofcom survey(22) findings confirm.

Ofcom? There’s no link, but footnote 22 says Ibid, referring to footnote 21, which says: Communications Market Report: Converging Communications Markets. Ofcom, August 2007. No link.

Maybe the “work packages” say more about this? In package 2 I found this:

The source? Ofcom (2006). No link. Unclear what the superscript 6 means, as the references in this report are not numbered, but they do mention:

Ofcom (2007) Communications Market Report: Converging Communications Markets. Research Document. London, UK: Office for Communications

Ofcom (2006). The Consumer Experience. London, UK: Office for Communications

So I searched for Ofcom (2006), The Consumer Experience, and found, you guessed it, another PDF, the relevant part of which appears to be section 2.4.2: Profile of those who experience difficulties when using technology. But nothing I can find there, or elsewhere in this report, says anything about who is or isn’t likely to learn about technology by reading the manual. And nothing in Ofcom(2007) either.

At this point I have to stop and remind myself what I was looking for in the first place: Evidence that it is a myth that kids learn by doing, and adults by reading the manual. All I have found is a flock of PDF files that mention one another obliquely, and in ways I cannot even correlate. No links. No data.

Now, the message of this highly-touted “Google generation” report, as refracted through the lens of Information Week, is:

Information literacy has not improved with the widening access to technology. Instead, the speed of Web searching means little time is spent evaluating information for relevance, accuracy, or authority.

And that may well be true. But do you see the irony here? The study making this claim was constructed and published in a way that resists all efforts to evaluate its relevance, accuracy, or authority. Which hardly matters, since none of the reporting about the study seems to have made any such effort.

Pioneering research shows ‘Google Generation’ is a myth? So far as I can see, that report says more about the researchers who wrote it, and about the reporters who reacted to it, than it says about any real or imaginary trends.

Larry Lessig’s video in support of Barack Obama is making the rounds in the blogosphere. Scanning the transcript I found a comment entitled Andrew Sullivan which reads:

Consider this hypothetical. It’s November 2008. A young Pakistani Muslim is watching television and sees that this man—Barack Hussein Obama—is the new face of America. In one simple image, America’s soft power has been ratcheted up not a notch, but a logarithm. A brown-skinned man whose father was an African, who grew up in Indonesia and Hawaii, who attended a majority-Muslim school as a boy, is now the alleged enemy. If you wanted the crudest but most effective weapon against the demonization of America that fuels Islamist ideology, Obama’s face gets close. It proves them wrong about what America is in ways no words can.

I’ve read that paragraph before. But not in the Lessig transcript. It comes from this Andrew Sullivan article in The Atlantic.

Why append it to the Lessig transcript? I think the anonymous commenter — who, however, chooses to identify himself or herself with the law firm Latham and Watkins — is drawing attention to the similarity between that paragraph and this one which does appear in the Lessig transcript:

So I want you to shut your eyes and imagine what it will seem like to a young man in Iraq or in Iran, who wakes up on January 21st, 2009, and sees the picture of this man as the president of the United States. A man who opposed the war at the beginning, a man who worked his way up from almost nothing, a man who came from a mother and a father of mixed cultures and mixed societies, who came from a broken home to overcome all of that to become the leader in his class, at the Harvard Law Review, and an extraordinary success as a politician. How can they see us when they see us as having chosen this man as our president?

Was Lessig’s paragraph influenced by Sullivan’s, which it’s reasonable to suppose he has read? My guess is that it was. If so, was the influence conscious or unconscious? My guess: unconscious.

This reminded me of Malcolm Gladwell’s 2004 New Yorker article on plagiarism, Something Borrowed, in which he recounts how one of his own New Yorker articles was pretty blatantly plagiarized by Bryony Lavery, the author of a play called Frozen. The incident prompts him to reflect on the nature of influence, and he muses:

When I read the original reviews of “Frozen,” I noticed that time and again critics would use, without attribution, some version of the sentence “The difference between a crime of evil and a crime of illness is the difference between a sin and a symptom.” That’s my phrase, of course. I wrote it. Lavery borrowed it from me, and now the critics were borrowing it from her. The plagiarist was being plagiarized. In this case, there is no “art” defense: nothing new was being done with that line. And this was not “news.” Yet do I really own “sins and symptoms”? There is a quote by Gandhi, it turns out, using the same two words, and I’m sure that if I were to plow through the body of English literature I would find the path littered with crimes of evil and crimes of illness.

Now here’s where it gets really twisty. In Something Borrowed, Gladwell refers to Lessig:

Creative property, Lessig reminds us, has many lives — the newspaper arrives at our door, it becomes part of the archive of human knowledge, then it wraps fish. And, by the time ideas pass into their third and fourth lives, we lose track of where they came from, and we lose control of where they are going.

See also several of Gladwell’s blog entries about a more recent case in which:

Harvard sophomore Kaavya Viswanathan plagiarizes a series of passages from Megan McCafferty’s teen novels “Sloppy Seconds” and “Second Helpings” for her debut novel: “How Opal Mehta Got Kissed, Got Wild, and Got a Life.”

On his blog, Gladwell initially makes the same sort of defense for Viswanathan that he made for Lavery in the New Yorker piece. Then his readers call him out, and he winds up agreeing with them that it was a different case.

But I digress. The real point here is that nowadays, even as ideas pass into their third and fourth lives, we don’t necessarily lose track of where they came from. A couple of years ago, Tim O’Reilly wrote a blog post entitled Act your way into a new way of thinking, which he said was “a fabulous quote from Richard Pascale’s book Delivering Results.” Tim added this postscript:

P.S. Very cool to be able to find the original source for the first quote via Google book search. As it came to me, it was simply labeled “Richard Pascale, Stanford Business School.”

At the time, I commented:

> Very cool to be able to find the original source”

And, to track the meme! From this it does appear Pascale is the original source:

http://books.google.com/books?q=%22act+our+way+into+a+new+way+of+thinking%22

Fascinating to see who cites him and who doesn’t.

Weirdly, I only just now noticed that both Tim and I wrongly attributed Delivering Results to Richard Pascale. In fact, the author is David Ulrich, not Richard Pascale.

But that doesn’t affect my point. Whether or not Lessig’s paragraph was influenced by Sullivan’s, the ways in which we influence one another are becoming more transparent, more traceable.

To complete this twisty excursion, I was looking up The Anxiety of Influence, by Harold Bloom, and found this eponymous blog posting from Lorcan Dempsey, in which he was surprised to find Bloom so prominent in the original WorldCat Identities tag cloud, and in which he cites a Tim O’Reilly post expressing similar surprise:

Who knew that as far as libraries are concerned, Harold Bloom is right up there with Brahms and Chopin. That’s one influential literary critic!

OK, I’ve reached my connection limit for now. But the fact that all these connections are traceable is a wonderful thing.

For this week’s ITConversations podcast I asked Phil Windley to review the work he’s done — with several groups of his students — to develop a software framework for managing online reputation. Phil explains:

Reputation is a very personal thing. The way you think about a person we both know in common, and the way I think about that person, is different. We talk about Joe having a reputation, but in fact, Joe doesn’t have a reputation, every single person has a different feeling and way of thinking about Joe. Reputation is your story about me. I don’t control my reputation, I only control some factors that you might or might not use to calculate it. I don’t control all of them, and you may take factors into account that I have no control over.

If we’re going to bring that social system, developed over thousands of years, to the Net, we need to mimic that opportunity as closely as possible. So the idea of our rules language was to allow you to create your own algorithms abouthow you determine the reputation of something or someone, and to allow me to create a different one.

Of course, if my calculations about Joe and your calculations about Joe refer to the same public, or omnidirectional, digital identity, then they can be merged. And by referring to my digital identity and yours, somebody else will be able to aggregate our calculations about Joe, and propagate them transitively.

That scenario entails both risks and benefits. At the moment, it’s easier for most people to imagine the risks. Phil says:

Offline we all give up information about ourselves all the time, trading privacy for convenience, and we have a pretty good feel for how that information is compartmentalized — not always, and there are obvious problems — but if I tell somebody in one business my name, that won’t mean the business down the street finds out about my transactions. Online, all of those intuitions have been switched around, and we’ve come to believe that giving up as little information as possible is the right thing.

The phrase “giving up information” has a negative connatation. We haven’t yet established norms for “declaring information” in a positive sense, and we have no intuitions about the benefits that doing so might yield. But we may find that by declaring information about ourselves, we can help make the stories that are being told about us — whether we participate in them or not — truer and more useful.


Well, that was a nice change of pace. Back in the land of the “wintry mix” — rain/sleet/snow — the first thing that caught my eye was a full-page ad in the local paper promoting the benefits of oil heat. Sponsored by the Oil Heat Council of New Hampshire, and featuring local icon Fritz Weatherbee wearing his trademark bowtie, the ad is a mosaic of smiling faces with captions like:

“New technology reduced my oil consumption by 25%.”

“Oil heat is safe.”

“It’s local. My oil heat dealer is also my neighbor.”

“Budgeting programs make oil heat affordable.”

“Oil heat made it easier to sell our home.”

I guess the emerging alternatives are being taken seriously. You’ve gotta love the rhetoric. Oil is local? Should’ve put that on the top ten list.