Category: user-driven (Page 5 of 8)

Let’s turn Do Not Track into a dialog

Do Not Track (DNT), by resembling Do Not Call in name, sounds like a form of prophylaxis.  It isn’t. Instead it’s a request by an individual with a browser not to be tracked by a website or its third parties. As a request, DNT also presents an interesting opportunity for dialogue between user and site, shopper and retailer, or anybody and anything. I laid out one possibility recently in my Inkwell conversation at The Well. Here’s a link to the page, and here’s the text of the post:

The future I expect is one in which buyers have many more tools than they have now, that the tools will be theirs, and that these will enable buyers to work with many different sellers in the same way.

One primitive tool now coming together is “Do Not Track” (or DNT): http://en.wikipedia.org/wiki/Do_Not_Track It’s an HTTP header in a user’s browser that signals intention to a website. Browser add-ons or extensions for blocking tracking, and blocking ads, are also tools, but neither constitute a social protocol, because they are user-side only. The website in most cases doesn’t know ad or tracking blocking being used, or why. On the other hand, DNT is a social gesture. It also isn’t hostile. It just expresses a reasonable intention (defaulted to “on” in the physical world) not to be followed around.

But DNT opens the door to much more. Think of it as the opening to dialog:

User: Don’t track me.
Site: Okay, what would you like us to do?
User: Share the data I shed here back to me in a standard form, specified here (names a source).
Site: Okay. Anything else?
User: Here are my other preferences and policies, and means for matching them up with yours to see where we can agree.
Site: Good. Here are ours.
User: Good. Here is where they match up and we can move forward.
Site: Here are the interfaces to our CRM (Customer Relationship Management) system, so your VRM (Vendor Relationship Management) system can interact with it.
User: Good. From now on my browser will tell me we have a working relationship when I’m at your site, and I can look at what’s happening on both sides of it.

None of this can be contemplated in relationships defined entirely by the sellers, all of which are silo’d and different from each other, which is what we’ve had on the commercial Web since 1995. But it can be contemplated in the brick & mortar world, which we’ve had since Ur. What we’re proposing with VRM is nothing more than bringing conversation-based relationships that are well understood in the brick-and-mortar world into the commercial Web world, and weaving better marketplaces in the process.

A bit more about how the above might work:
http://blogs.law.harvard.edu/vrm/2012/02/23/how-about-using-the-no-track-button-we-already-have/

And a bit more about what’s wrong with the commercial Web (so far, and it’s not hard to fix) here:
http://blogs.law.harvard.edu/vrm/2012/02/21/stop-making-cows-stop-being-calves /

So, to move forward, consider this post a shout-out to VRM developers, to the Tracking Protection Working Group at the W3C, to browser developers, to colleagues at Berkman (where Chris Soghoian was a fellow, about at the time he helped think up DNT) — and to everybody with the will and the ways to move forward on this thing.

And hey: it’s also our good luck that the next IIW is coming up at the Computer History Museum in Mountain View, from October 23rd to 25th. IIW is the perfect place to meet and start hashing out DNT-D (I just made that up: DNT-Dialog) directions. IIW is an unconference: no keynotes, panelists or vendor booths. Participants vet and choose their own topics and break out into meeting rooms and tables. It’s an ideal venue for getting stuff done, which always happens, and why this is the 15th of them.

Meanwhile, let’s get in touch with each other and start making it happen.

Can we each be our own Amazon?

The most far-out chapter in  is one set in a future when free customers are known to be more valuable than captive ones. It’s called “The Promised Market,” and describes the imagined activities of a family traveling to a wedding in San Diego. Among the graces their lives enjoy are these (in the order the chapter presents them):

  1. Customer freedom and intentions are not restrained by one-sided “agreements” provided only by sellers and service providers.
  2. — service organizations working as agents for the customer — are a major breed among user driven services.
  3. The competencies of nearly all companies are exposed through interactive that customers and others can engage in real time. These will be fundamental to what calls .
  4. s (now also called intentcasts), will be common and widespread means for demand finding and driving supply in the marketplace.
  5. Augmented reality views of the marketplace will be normative, as will mobile payments through virtual wallets on mobile devices.
  6. Loyalty will be defined by customers as well as sellers, in ways that do far more for both than today’s one-sided and coercive loyalty programs.
  7. Relationships between customers and vendors will be genuine, two-way, and defined cooperatively by both sides, which will each possess the technical means to carry appropriate relationship burdens. In other words, VRM and CRM will work together, at many touch-points.
  8. Customers will be able to proffer prices on their own, independently of intermediaries (though those, as fourth parties, can be involved). Something like EmanciPay will facilitate the process.
  9. Supply chains will become “empathic” as well as mechanical. That is, supply chains will be sensitive to the demand chain: signals of demand, in the context of genuine relationships, from customers and fourth parties.
  10. The advertising bubble of today has burst, because the economic benefits of knowing actual customer intention — and relating to customers as independent and powerful economic actors, worthy of genuine relationships rather than coercive — bob will have became obvious and operative. Advertising will continue to do what it does best, but not more.
  11. Search has evolved to become far more user-driven and interactive, involving agents other than search engines.
  12. Bob Frankston‘s will be taken for granted. There will still be businesses that provide connections, but nobody will be trapped into any one provider’s “plan” that excludes connection through other providers. This will open vast new opportunities for economic activity in the marketplace.

In , Sheila Bounford provides the first in-depth volley on that chapter, focusing on #4: personal RFPs. I’ll try to condense her case:

I’ve written recently of a certain frustration with the seemingly endless futurology discussions going on in the publishing world, and it’s probably for this reason that I had to fight my way through the hypothesis in this chapter. However on subsequent reflection I’ve found that thinking about the way in which Amazon currently behaves as a customer through its Advantage programme sheds light on Searls’ suggestions and projections…

What Searls describes as the future for individual consumers is in fact very close to the empowered relationship that Amazon currently enjoys with its many suppliers via Amazon Advantage…  Amazon is the customer – and a highly empowered one at that.

Any supplier trading with Amazon via Advantage (and that includes most UK publishing houses and a significant portion of American publishers) has to meet all of the criteria specified by Amazon in order to be accepted into Advantage and must communicate online through formats and channels entirely prescribed and controlled by Amazon…

Alone, an individual customer is never going to be able to exert the same kind of leverage over vendors in the market place as a giant like Amazon. However individual customers online are greater than the sum of their parts: making up a crucial market for retailers and service providers. Online, customers have a much louder voice, and a much greater ability to collect, organise and mobilise than offline. Searls posits that as online customers become more attuned to their lack of privacy and control – in particular of data that they consider personal – in current normative contracts of adhesion, they will require and elect to participate in VRM programmes that empower them as individual customers and not leave them as faceless, impotent consumers.

So? So Amazon provides us with a neat example of what it might look like if we, as individuals, could control our suppliers and set our terms of engagement. That’s going to be a very different online world to the one we trade in now.  Although I confess to frustration with the hot air generated by publishing futurology, it seems to me that the potential for the emergence VRM and online customer empowerment is one aspect of the future we’d all do well to work towards and plan for.

From the start of ProjectVRM, Iain Henderson (now of The Customer’s Voice) has been pointing to B2B as the future model for B2C. Not only are B2B relationships rich, complex and rewarding in ways that B2C are not today (with their simplifications through customer captivity and disempowerment), he says, but they also provide helpful modeling for B2C as customers obtain more freedom and empowerment, outside the systems built to capture and milk them.

Amazon Advantage indeed does provide an helpful example of where we should be headed as VRM-enabled customers. Since writing the book (which, except for a few late tweaks, was finished last December) I have become more aware than ever of Amazon’s near-monopoly power in the book marketplace, and possibly in other categories as well. I have heard many retailers complain about “scan and scram” customers who treat brick-and-mortar stores as showrooms for Amazon. But perhaps the modeling isn’t bad in the sense that we ought to have monopoly power over our selves. Today the norm in B2C is to disregard that need by customers. In the future I expect that need to be respected, simply because it produces more for everybody in the marketplace.

It is highly astute of Sheila to look toward Amazon as a model for individual customers. I love it when others think of stuff I haven’t, and add to shared understanding — especially of a subject as protean as this one. So I look forward to the follow-up posts this week on her blog.

Scaling business in parallel

Companies and customers need to be able to deal with each other in two ways: as individuals and as groups.

As of today companies can deal with customers both ways. They can get personal with customers, and they can deal with customers en masse. Without the latter capability, mass marketing would not be possible.

Customers, on the other hand, can only deal with companies as individuals, one at a time. Dealing with companies as groups is still a challenge. Consider the way you engage companies in the marketplace, both online and off. Your dealings with companies, on the whole, are separate and sequential. Nothing wrong with that, but it lacks scale. Hence: opportunity.

We can arrive at that opportunity space by looking at company and personal dealings, each with two kinds of engagement circuits: serial and parallel.

Start with a small company, say a store with customers who line up at the counter. That store  deals with customers in a serial way:

business, serial

The customers come to the counter, one after another, in a series. Energy in the form of goods goes out, and money comes back.

As companies scale up in size, however, they’d rather deal with many customers in parallel rather than in series. A parallel circuit looks like this:

business, parallel

Here customers are dealt with as a group: many at once, and in the same way. This, in an extremely simplified form, is a diagram of mass marketing. While it is still possible for a company to deal with customers individually, the idea is to deal with as many customers as possible at once and in the same ways.

I use electronic symbols in those circuits because resistance (the zig-zag symbol) adds up in series, while it goes down in parallel. This too is a virtue of mass marketing. Thus one-to-many works very well, and has proven so ever since Industry won the Industrial Revolution.

Over on the customers’ side, the marketplace on the whole looks like this:

customer, serial

The customer goes from one company to the next. This is not a problem on the vendors’ side, except to the degree that vendors would rather customers not shop elsewhere. This is why vendors come up with loyalty programs and other schemes to increase “switching costs” and to otherwise extract as much money and commitment as possible out of the customer.

But, from the customer’s side, it would also be cool if they could enjoy scale in parallel across many companies, like this:

In the physical world this is all but unthinkable. But the Internet makes it very thinkable, because the Net reduces nearly to zero the functional distance between any two entities, and presents an open space across which many connections can be made, at once if necessary, with few limits on the number or scope of possibilities. There is also no limit to the new forms of interaction that can happen here.

For example, a customer could scale in parallel by expressing demand to multiple vendors at the same time, or could change her contact information at once with many companies. In fact this is basically what VRM projects are about: scaling in parallel across many other entites. (Not just vendors, but also elected officials, government agencies, churches, clubs, and so on.)

It is easy to see how companies can feel threatened by this. For a century and a half we in business have made a virtue of “targeting,” “acquiring,” “capturing,” “managing,” “locking in” and “owning” customers. But think about the free market for a minute. Shouldn’t free customers be more valuable than captive ones? Wouldn’t it be better if customers and prospects could send many more, and better, signals to the marketplace, and to vendors as well, if they were capable of having their own native ways of dealing, consistently, across multiple vendors?

We have that now with email and other forms of messaging. But why stop there?

Naturally, it’s easy to ask, Could social media such as Facebook, Google+ and Twitter provide some of what we need here? Maybe, but the problem is that they are not ours, and they don’t work for us — in the sense that they are accountable to us. They work for advertisers. Email, IM and browsing aren’t owned by anybody. They are also substitutable. For example, you can move your mail from Gmail to your own server or elsewhere if you like. Google doesn’t own email’s protocols. No browser company owns HTTP, HTML or any of the Web’s protocols.

The other problem with social solutions is that they’re not personal. And that’s the scale we’re talking about here: adding parallel capabilities to individuals. Sure, aggregation is possible, and a good thing. (And a number of VRM projects are of the aggregating-demand sort.) But the fallow ground is under our own feet. That’s where the biggest market opportunity is located. Also where, still, it is most ignored. Except, of course, here.

[Continued in VRM/CX + CRM/CX.]

Coming to terms

We lie every time we “accept” terms that we haven’t read — a pro forma  behavior that is all but required by the calf-cow model of the Web that’s prevailed since 1995. We need to change that. And so we are.

StandardLabel.org is working on “A clear, consistent way for websites to say what they do with the data they share, before we share it.” While its recent Kickstarter campaign came up a bit short, the work continues. Here is one (prototypical) way that label might look:

(The actual image I wanted there was this one, but heard it wasn’t showing up in all browsers, so I went with the one above.)

The StandardLabel folks also have a survey, which I recommend taking.

CommonTerms intends “to solve the problem of non-accessible online legal texts in a way similar to how Creative Commons made different copyright licenses accessible,” adding, “We thought that by analyzing existing agreements, we could identify the most common terms, and then create icons to symbolize them.” Background:

The CommonTerms project is coordinated by Metamatrix AB andsponsored by Internetfonden.se

The project is a result of a session on “sustainable web development” by Pär Lannerö and Thomas Bjelkeman at the Sweden Social Web Camp, in August 2010.

Their prototype, focused on icons, stars Pär and looks like this:

Par and  Lars-Erik Jakobsson (icon), Gregg BernsteinCarl TörnquistHanna ArkestålMax WalterMattias AspelundAnders Carlman have since added BiggestLie.com, source of the image at the top of this post, plus this one here, which I just earned:

The idea is to start getting real about what we’re all doing and not doing.

What we’re doing is lying: i.e. agreeing not only to what we don’t read, but to the rotted status quo of which one-sided non-agreements are a part. What we’ve not been doing for most of the last 17 years is solving the problem.

But, thanks to the work above (plus whatever I’ve missed), we are doing some things. So are PDEC.cc and companies like Personal. Other work is happening with personal clouds. (PDEC is on that case too.) Aza Raskin‘s Privacy Icons are an effort in this same direction. (CommonTerms has a longer list.)

Still, looks to me like most of the work being done so far is on the cow side of the calf-cow relationship. On our side, we need to stop being calves, for real. That is, we need to have full agency in the original sense of the word: power to cause intended effects on our own.

For that we will need machine- and user-readable ways to express own terms, preferences and policies, so they can be read by sites (the cows) and matched up. That’s the idea behind EmanciTerm, described in How about using the ‘No Track’ button we already have? and in The Intention Economy. There I explain,

With full agency, however, an individual can say, in the first person voice, “I own my data, I control who gets access to it, and I specify what I wish to happen under what conditions.” In the latter category, those wishes might include:

  • Don’t track my activities outside of this site.
  • Don’t put cookies in my browser for anything other than helping us remember each other and where we were.
  • Make data collected about me available in a standard, open format.
  • Please meet my fourth-party agent, Personal.com (or whomever).

These are EmanciTerms, and there will be corresponding ones on the vendor’s side. Once they are made simple and straightforward enough, they should become normative to the point where they serve as de facto stan- dards, in practice.

Since the terms should be agreeable and can be expressed in text that code can parse, the process of arriving at agreements can be automated.

For example, when using a public wi-fi access point, a person’s EmanciTerms might say, “I will not knowingly hog this shared resource, for example, by watching high-def video on it,” or “I will not engage in illegal activities here.” If the provider of the access point has a VRM-ready service that is willing to deal with the user on his or her own EmanciTerms as well as those of the provider, it should be possible to automate the formalities and let the user bypass the usual “read and accept our agreement” ritual.

Not everything we express in the proposed ceremony here has to be one side of a binding agreement. If we express these terms as preferences or policies they can still be heard, even if they’re not agreed to. Being heard is one idea behind BiggestLie. But the cows can’t fix this on their own. We need to work both sides.

The only problem with all this is that our work is scattered. Let’s get it together.

VRM at IIW

VRM was a hot topic at IIW last week, with at least one VRM or VRM-related breakout per session — and that was on top of the VRM workshop held at Ericsson on Monday, April 30, the day before IIW started. (Thanks to Nitin Shah and the Ericsson folks for making the time and space available, in a great facility.) Here’s a quick rundown from the #IIW14 wiki:

Tuesday, May 1, Session 1

Tuesday, May 1,Session 2

Tuesday, May 1, Session 3

Tuesday, May 1,Session 4

Tuesday, May 1,Session 5

Wednesday, May 2, Session 1

Wednesday, May 2,Session 2

Wednesday, May 2,Session 3

Wednesday, May 2,Session 4

Wednesday, May 2,Session 5

Thurssday, May 3,Sessions 1-5

On Friday, May 4, I also visited with Jeremie Miller, Jason Cavnar and the Locker Project / Singly team in San Francisco. Very impressed with what they’re up to as well.

Bonus IIW linkage:

Self-sovereign vs. administrative identity

You know who you are. So does the IRS, the DMV, and every website and service online where you have a login and a password for.

But none of those entities really knows you. What they know is what the techies call a namespace. That namespace is not your identity. Instead, it’s an identifier. That identifier is an administrative construction. It’s something created so bureaucracies and technical systems could do what they do.

Who you are isn’t just how you appear in the namespaces of administrative entities. Who you are isn’t even the name your parents gave you. It’s your single, unitary and sovereign self, which remains fixed at the source—you—no matter what you’re called.

The names that matter most to you are the one you were given at birth and the ones you choose to be called by. Neither is fixed. You can change your names without changing who you are. So can others, but managing how you are known is a self-sovereign power. Samuel Clemens used the pen name Mark Twain. Walt Whitman, the great author of Song of Myself, did not call himself Walter.

Yes, some names come about socially, but the choice to use them for ourselves is personal. Take my own example. The name my parents gave me was David. Many friends and relatives still call me David or Dave. Many more, however, call me Doc. That name is what remains of Doctor Dave, which is what I was called on the radio and in a humor column in North Carolina in the late ’70s. (That image above was how I appeared in the column. I was around 30 then. I actually look like that now.) My surname is one my father chose to spell the same as did his father, but not his grandparents.  (They went by Searles.)

The nickname Doc came along after I started a company with two other guys, one of whom was named David. He and the other guy (the late great Ray Simone, who also drew the Doctor Dave image above) called me Doctor Dave around the office, and with clients and suppliers. After awhile three syllables seemed too many, and they all just called me Doc. Also relevant: David was actually David’s middle name. His first was Paul.

Nicknames are often context-dependent. People who knew me through business called me Doc. Everybody else called me David or Dave.

That was in North Carolina, where I had lived for most of the two decades before our company opened an office in Silicon Valley and I went out there prospecting. That was in the Fall of ’85. I knew almost nobody in California, other than a few business contacts who called me Doc. But I wasn’t sure about keeping Doc as a nickname, since in a way I was starting over in a new place. So,  I market tested Doc vs. David when I went to the Comdex conference in October of that year in Las Vegas.  The test was simple. I had two badges made. One said David Searls and the other said Doc Searls. I was there four days and alternated between the two badges. Afterwards everybody remembered Doc and nobody remembered David. So I decided not to dump the nickname, and it stuck.

My point is that I still had control over what I chose to be called. I had sovereign authority over that.

The problem I’m trying to surface here is that we need full respect for self-sovereign identities, and identifiers, before we can solve the problem of highly fractured and incompatible administrative identifiers — a problem that has only become worse with the growth of the Web, where by design we are always the submissive and dependent party: calves to administrative cows.

MoxyTongue puts it this way:

You are a social ID-slave by default today.

I want a Human ID; a personal data construct with sovereign source authority.

Society uses a social construct to give me an Administrative ID.

The difference is origin.

I do not participate in Society primarily as an AdminID.

I am a Human ID by sovereign source authority, backed by American Rights that I know how to wield administratively and matriculate accordingly.

Structure yields results. Therefore, if we get the origin of ID correct, we can get the data administration framework oriented right.

A Human ID -led Society with embedded structural Rights and empowerments is the socio-economic game changer.

That is my NSTIC proposal. That’s my open proposal: a new data administration framework for identity.

Deployed across Society by opt-in opportunity structure.

Deployable across a global ecosystem by data design.

I see an ID as a door. The existence of the door is a social construct… a decision…

But once that decision is made, it is Human executed in every regard.

ID-slavery is what we have by administrative structure today. Our managerial intent in servicing it is flawed by design.

A Human ID comes with #vrm baked in. Such is the bi-directional transactional authority, multi-role nature of it.

And most important… we all approach the door on equal Terms… one door…infinite possibilities.

Self-driven socio-economic structure.

Call it whatever you want…it starts with your identity being structured right.

VRM for me grew out of two things:

  1. The unfinished work of Cluetrain. The ‘one clue to get’ there said “our reach exceeds your grasp.” But it didn’t, and it still doesn’t. Much of the grasp is administrative, and it has to do with defining, for us, who we are. That’s a bug, not a feature.
  2. The unfinished work of the digital identity development community, which I believe will remain unfinished as long as we try to solve one symptom with another one. The symptom we’re trying to solve is regarding administrative IDs as independent variables, rather than as dependent ones. Until we recognize that the only true independent variable is the soul of the independent self, we’ll continue to seek administrative solutions to the problem of administrative identity slavery.

Have you ever noticed that when somebody says “That’s a good question?” it’s usually because they don’t yet have an answer? That applies here. To the question of how we make sovereign-source identity the independent variable, I don’t have an answer. But I do want to work on it.

I’ll be doing that tomorrow at a meeting on identity in Silicon Valley. On May 1-3 in Mountain View we’ll be holding the Internet Identity Workshop again. It’s our fourteenth, and it’s a terrific unconference. If you care about this stuff, you should come. Your sovereign self would like that.

How about using the ‘No Track’ button we already have?

left r-buttonright r-buttonFor as long as we’ve had economies, demand and supply have been attracted to each other like a pair of magnets. Ideally, they should match up evenly and produce good outcomes. But sometimes one side comes to dominate the other, with bad effects along with good ones. Such has been the case on the Web ever since it went commercial with the invention of the cookie in 1995, resulting in a calf-cow model in which the demand side — that’s you and me — plays the submissive role of mere “users,” who pretty much have to put up with whatever rules websites set on the supply side.

Consistent with Lord Acton’s axiom (“Power corrupts; absolute power corrupts absolutely”) the near absolute power of website cows over user calves has resulted in near-absolute corruption of website ethics in respect to personal privacy.

This has been a subject of productive obsession by Julia Anguin and her team of reporters at The Wall Street Journal, which have been producing the What They Know series (shortcut: http://wsj.com/wtk) since July 30, 2010, when Julia by-lined The Web’s New Gold Mine: Your Secrets. The next day I called that piece a turning point. And I still believe that.

Today came another one, again in the Journal, in Julia’s latest, titled Web Firms to Adopt ‘No Track’ Button. She begins,

A coalition of Internet giants including Google Inc. has agreed to support a do-not-track button to be embedded in most Web browsers—a move that the industry had been resisting for more than a year.

The reversal is being announced as part of the White House’s call for Congress to pass a “privacy bill of rights,” that will give people greater control over the personal data collected about them.

The long White House press release headline reads,

We Can’t Wait: Obama Administration Unveils Blueprint for a “Privacy Bill of Rights” to Protect Consumers Online

Internet Advertising Networks Announces Commitment to “Do-Not-Track” Technology to Allow Consumers to Control Online Tracking

Obviously, government and industry have been working together on this one. Which is good, as far as it goes. Toward that point, Julia adds,

The new do-not-track button isn’t going to stop all Web tracking. The companies have agreed to stop using the data about people’s Web browsing habits to customize ads, and have agreed not to use the data for employment, credit, health-care or insurance purposes. But the data can still be used for some purposes such as “market research” and “product development” and can still be obtained by law enforcement officers.

The do-not-track button also wouldn’t block companies such as Facebook Inc. from tracking their members through “Like” buttons and other functions.

“It’s a good start,” said Christopher Calabrese, legislative counsel at the American Civil Liberties Union. “But we want you to be able to not be tracked at all if you so choose.”

In the New York Times’ White House, Consumers in Mind, Offers Online Privacy Guidelines Edward Wyatt writes,

The framework for a new privacy code moves electronic commerce closer to a one-click, one-touch process by which users can tell Internet companies whether they want their online activity tracked.

Much remains to be done before consumers can click on a button in their Web browser to set their privacy standards. Congress will probably have to write legislation governing the collection and use of personal data, officials said, something that is unlikely to occur this year. And the companies that make browsers — Google, Microsoft, Apple and others — will have to agree to the new standards.

No they won’t. Buttons can be plug-ins to existing browsers. And work has already been done. VRM developers are on the case, and their ranks are growing. We have dozens of developers (at that last link) working on equipping both the demand and the supply side with tools for engaging as independent and respectful parties. In fact we already have a button that can say “Don’t track me,” plus much more — for both sides. Its calle the R-button, and it looks like this: ⊂ ⊃. (And yes, those symbols are real characters. Took a long time to find them, but they do exist.)

Yours — the user’s — is on the left. The website’s is on the right. On a browser it might look like this:

r-button in a browser

Underneath both those buttons can go many things, including preferences, policies, terms, offers, or anything else — on both sides. One of those terms can be “do not track me.” It might point to a fourth party (see explanations here and here) which, on behalf of the user or customer, maintains settings that control sharing of personal data, including the conditions that must be met. A number of development projects and companies are already on this case. All the above falls into a category we call EmanciTerm. Much has been happening as well around personal data stores (PDSes), also called “lockers,” “services” and “vaults.” These include:

Three of those are in the U.S., one in Austria, one in France, one in South Africa, and three in the U.K. (All helping drive the Midata project by the U.K. government, by the way.) And those are just companies with PDSes. There are many others working on allied technologies, standards, protocols and much more. They’re all just flying below media radar because media like to look at what big suppliers and governments are doing. Speaking of which… 🙂

Here’s Julia again:

Google is expected to enable do-not-track in its Chrome Web browser by the end of this year.

Susan Wojcicki, senior vice president of advertising at Google, said the company is pleased to join “a broad industry agreement to respect the ‘Do Not Track’ header in a consistent and meaningful way that offers users choice and clearly explained browser controls.”

White House Deputy Chief Technology Officer Daniel Weitzner said the do-not-track option should clear up confusion among consumers who “think they are expressing a preference and it ends up, for a set of technical reasons, that they are not.”

Some critics said the industry’s move could throw a wrench in a separate year-long effort by the World Wide Web consortium to set an international standard for do-not-track. But Mr. Ingis said he hopes the consortium could “build off of” the industry’s approach.

So here’s an invitation to the White House, Google, the 3wC, interested BigCos (including CRM companies), developers of all sizes and journalists who are interested in building out genuine and cooperative relationships between demand and supply::::

Join us at IIW — the Internet Identity Workshop — in Mountain View, May 1-3. This is the unconference where developers and other helpful parties gather to talk things over and move development forward. No speakers, no panels, no BS. Just good conversation and productive work. It’s our fourteenth one, and they’ve all been highly productive.

As for the r-button, take it and run with it. It’s there for the development. It’s meaningful. We’re past square one. We’d love to have all the participation we can get, from the big guys as well as the little ones listed above and here.

To help get your thinking started, visit this presentation of one r-button scenario, by Adam Marcus of MIT. Here’s another view of the same work, which came of of a Google Summer of Code project through ProjectVRM and the Berkman Center:

(Props to Oshani Seneviratne and David Karger, also both of MIT, and Ahmad Bakhiet, of Kings College London, for work on that project.)

If we leave fixing the calf-cow problem entirely up to the BigCos and BigGov, it won’t get fixed. We have to work from the demand side as well. In economies, customers are the 100%.

Here are some other stories, mostly gathered by Zemanta:

All look at the symptoms, and supply-side cures. Time for the demand side to demand answers from itself. Fortunately, we’ve been listening, and the answers are coming.

Oh, and by the way, Mozilla has been offering “do not track” for a long time. Other tools are also available:

Stop making cows. Quit being calves.

Emoji_u1f42e.svg The World Wide Web that invented in 1990 was a collection of linked documents. The Web we have today is a collection not just of documents (some of which we quaintly call pages), but of real estate we call sites. This Web is mostly a commercial one.

Even if most sites aren’t commercial (I don’t know), most search results bring up commercial sites anyway, thanks both to the abundance of commercial sites on the Web, and “search engine optimization” (SEO) by commercial site operators. Online ad spending in the U.S. alone will hit $40 billion this year, and much of that money river runs through Google and Bing.

But that’s a feature, not a bug. The bug is that we’ve framed our understanding of the Web around locations and not around the fabric of connections that define both the Net and the Web at the deepest level. That’s why nearly every new business idea starts with real estate: a site with an address. Or, in the ranching-based lingo of marketing, a brand.

The problem isn’t with the sites themselves, or even with the real estate model we use to describe and understand them. It’s with their underlying architecture, called client-server.

Client-server, by design, subordinates visitors to websites. It does this by putting nearly all responsibility on the server side, so visitors are just users or consumers, rather than participants with equal power and shared responsibility in truly two-way relationship between equals. Thus the client-server relationship is roughly that of calf to cow:

calf-cow

From the teats of the cow-server, the calf-client sucks the milk of HTML and Javascript, plus : text files deposited by a website’s server in a visitor’s browser. Their original purpose was to help both the site and the visitor (the cow and the calf) remember where they were last time they met, and to retain other helpful information, such as logins and passwords.

But cookies also became a way for commercial cows and their business friends (aka third parties) to keep track of their calves, reporting back where those calves traveled, the  cows they suckled, the stuff they click on. Based on what they learn from tracking, the cows can — alone or with assistance from third parties, produce “personalized” milk in the form of customized pages and ads. This motivation is all the rage today, especially around advertising.

Nearly all the investment on ‘relating’ is still on the sell side: the cow side, because that’s where all the power is concentrated, thanks to client-server. So we keep making better cows and cow-based systems, forgetting that the calves are actual human beings called customers. We also overlook opportunity in helping demand drive supply, rather than just in helping supply drive demand.

But some of us haven’t forgotten. One is Phil Windley, a Ph.D. computer scientist, former CIO of Utah, co-founder of , and the inventor and lead maintainer of a language called , plus the rules engine for executing KRL code. (Both are open source.) The rules are the individual’s own. The rules engine can go anywhere. No cow required.

To describe the box outside of which Phil thinks, he gives a great presentation on the history of e-commerce. It goes like this:

1995: Invention of the Cookie.
The End.

To describe where he’s going (along with Kynetx and the rest of the VRM development community), Phil wrote a new book, The Live Web (a term you might have first read about here), and has been publishing a series of blog posts that deal with what he calls . Think of your Personal Event Network as the Live Web that you, as a human being (rather than as a calf) operate. Live. In real time. Your own way. You can take advantage of services offered by the servers of the world (through APIs, for example). But it’s your network, and it’s built with your own relationships. It doesn’t replace client-server, but it gives servers lots to do besides being cows. In fact, the opportunities are boundless, because they’re in wide-open virgin territory.

A Personal Event Network puts you at the center of your Live Web, with your own apps, and your own rules for what follows from events in your web of relationships. “Personal event networks interact with each other as equals,” Phil says. “They aren’t client server in nature.” Here’s how Phil draws one example:

Personal Event Network

Look at the three items indside the personal cloud:

  • At the center are apps. We’re already familiar with those on our computers and mobile devices. While they might have connections to outside services, they are personal tools of our own. They are neither calves nor cows.
  • On the left is an RFQ, or a Request For Quote, also called a .
  • On the right are rules, written in KRL.

Together those control how we interact with all the devices and services on the outside, on the Live Web. Note that those outside items are not functioning as cows, even though they also live in the commercial Web’s client-server world. They are being engaged outside the cow function, mostly through s.

Here’s how Phil explains how this works for a guy named Tim, who has a relationship with a flower shop, described here:

Tim’s personal event network has a number of apps installed. It’s also is listening on many event channels. These channels are carrying events about everything from Tim’s phone and appliances to merchants he frequents.

REI and the flowershop both have separate channels into Tim’s personal event network. Consequently, Tim can

  • Manage them independently. If REI starts spamming Tim with events he doesn’t like, he can simply delete the channel and they’re gone.
  • Permission them independently. Tim might want to get certain events from REI and other’s from the flowershop. Which events can be carried on which channels is up to Tim.
  • Respond to them independently. Tim might want to get notification events from the flowershop delivered to his phone today because it’s his wife’s birthday whereas normally merchant communications are sent to his mail box.

Tim is in charge of whether and how events are delivered. He manages the channel, delivery, and response while the publishers of these event choose the content.

This cannot be done within the bovine graces of any one company — not Apple, Facebook, Google or Microsoft — no matter how rich their services might be, and no matter how well they treat their users and customers. And not matter how much they might insist that they’re not really treating their users and customers as calves.

But they’re still playing the cow role, and we’re still stuck as calves. That’s why we keep looking for better cows.

For example take The Real Problem With Google’s New Privacy Policy, in . The subtitle explains, “The tech giant owes users better tools to manage their information.” Well, that might be true. But we also need our own tools for managing relationships with Google — and every other site and service on the Web. And we need those tools to work the same way with every company, rather than different ways with every company.

(We have this, for example, with email, thanks to open, standard and widely deployed protocols. Email is fully human, even if we submit to playing the half-calf role inside, say, Gmail. We can still take our whole email pile outside of Gmail and put it on any other server, or host it ourselves. Email’s protocols and standards support that degree of independence, and therefore of humanity as well.)

Another example is The Ecommerce Revolution is All About You, in . Here’s the closing paragraph:

So shoppers, be prepared to give up your data. In the coming year, we’re going to see many more retail sites ramping up data-driven discovery. And e-commerce sites who aren’t thinking about how to mine social and other forms of data are probably going to be left in the dust by the Amazons and Netflix’s of the next wave of personalization.

Credit where due to Amazon and Netflix: their personalization is best-of-breed. Their breed just happens to be bovine.

As it did in 1995, Amazon today provides their own milk and cookies for their own calf-customers. As a loyal Amazon customer, I have no problem being its calf. But I can’t easily take my data (preferences, history, reviews etc.) from Amazon and use it myself, in my own ways, and for my own purposes. It’s their data, not mine.

The problem with this — for both Amazon and me — is that Amazon isn’t the whole World Live Web. I don’t shop only at Amazon, and I would like better ways of interacting with all sellers than any one seller alone can provide, even if they’re the world’s best online seller. (Which Amazon, arguably, is.)

So sure, the Ecommerce Revolution is “about us.” But if it’s our revolution, why aren’t we getting more of our own tools and weapons? Why should we keep depending on sellers’ personalization systems to do all the work of providing relevance for us as shoppers? Should we give up our data to those companies just so they can raise the click-through rates of their messages from one in less than a hundred to one in ninety-eight — especially when many of the misses will now be creepily “personalized” as well?

Shouldn’t we know more about what to do with our data than any seller can guess at? And if we don’t know yet, why not create companies that help us buy at least as well as other companies are help sellers sell?

Well, those kinds of companies are being created, and you’ll find a pile of them listed here, Kynetx among them.

VCs need to start looking seriously at development on the demand side. Kynetx is one among dozens of companies that are flying below the radar of too many VCs just looking at better cows, and better ways to sell — or worse, to “target,” “capture,” “acquire,” “lock in” and “manage” customers as if they were slaves or cattle.

The idea that free markets are your-choice-of-captor is a relic of a dying mass-market-driven mentality from the pre-Internet age. Free markets need free customers. And we’ll get them, because we’ll be them.

We — the customers — are where the money that matters most comes from. Driving that money into the marketplace are our own intentions as sovereign and independent human beings.

In the next few years we’ll build an Intention Economy, driven by customers equipped with their own tools, and their own ways of interacting with sellers, including their own terms of engagement. This was the promise of the Net and the Web in the first place, and we’ve awaited delivery for long enough.

Time’s up. The age of captivity is ending. Start placing your bets on the demand side.

Ting rings the opening bell

Here, according to the ProjectVRM wiki, are the ideal characteristics of VRM tools:

  1. VRM tools are personal. As with hammers, wallets, cars and mobile phones, people use them as individuals,. They are social only in secondary ways.
  2. VRM tools help customers express intent. These include preferences, policies, terms and means of engagement, authorizations, requests and anything else that’s possible in a free market, outside any one vendor’s silo or ranch.
  3. VRM tools help customers engage. This can be with each other, or with any organization, including (and especially) its CRM system.
  4. VRM tools help customers manage. This includes both their own data and systems and their relationships with other entities, and their systems.
  5. VRM tools are substitutable. This means no source of VRM tools can lock users in

Note “mobile phones” in #1. Like a car or a wallet, a mobile phone is personal. Ir also supports our independence, helps us express intent, and is substitutable. Bearing all these things (and more) in mind, Ting.com has come to market with the clear intent of doing the best it can to support customers’ VRM intentions.

Go down Joe Andrieu’s list of user driven services

  1. Impulse from the User
  2. Control
  3. Transparency
  4. Data Portability
  5. Service Endpoint Portability
  6. Self Hosting
  7. User Generativity
  8. Improvability
  9. Self-managed Identity
  10. Duty of Care

… and you’ll find that Ting comes about as close as any mobile phone company can come to respecting all those things.

Ting is an MVNO — a Mobile Virtual Network Operator. That means it operates as a phone company, but does not own facilities. Instead it re-sells the raw base offerings (minutes, texts, quantities of data) that it buys from a carrier with facilities. In this case, Sprint. It works everywhere in the U.S. that Sprint does, but it has a much more friendly and sensible set of offerings and pricings than any of the major mobile phone companies. It’s about as gimmick-free as you can get. That is, Ting is the very opposite of what Scott Adams in The Dilbert Future calls a “confusopoly.” Sez Scott,

A confusopoly is a situation in which companies pretend to compete on price, service, and features but in fact they are just trying to confuse customers so no one can do comparison shopping.

Cell [mobile] phone companies are the best example of confusopolies. The average consumer finds it impossible to decipher which carrier has the best deal, so carriers don’t have normal market pressure to lower prices. It’s a virtual cartel without the illegal part.

Ting is a VRM company. Its management and other personnel have been involved in many VRM discussions and events, and a number of VRM folk have been involved in Ting’s beta as well. Our family, for example. So far we’re loving it. The data service especially is surprisingly good. At our kid’s high school in rural New Hampshire, both voice and data service is pretty much perfect.

Here are some of the stories about the Ting launch that have hit so far:

Plus these from Zemanta:

Complaining vs. Buying

Q: “What’s the difference between a tweeter and a customer?”

A: “One complains, the other buys.”

Just had to write that down. The Q and the A came in the midst of a VRM conference call that also touched on CRM, VRM+CRM, sCRM, trust frameworks, identity and other stuff.

Not saying that’s a fair characterization, by the way. Just that it’s an interesting one.

« Older posts Newer posts »

© 2024 ProjectVRM

Theme by Anders NorenUp ↑