Category: VRM (page 8 of 23)

VRM growing in the garden of privacy concerns

With Swedes: Closet VRM activists?T.Rob gives us a typically deep VRM post, exploring new territory, or old territory in a new way. The context (and the subject of an interesting thread on the ProjectVRM list) is the news behind headline of a Simon Davies post: Sweden’s data protection Authority bans Google cloud services over privacy concerns. Sez T.Rob,

So the big problem with privacy, VRM tools and the cloud isn’t that the technology needs to be invented, but rather that the current IT culture assumes the vendor has rights rather thanprivileges to harvest and exploit your data and that you must opt out rather than opt in.  If you start with an assumed right to the data, then of course the apps that get built ignore existing privacy enhancing technology.

T.Rob raises some creative existing solutions to password problems — solutions that have thus far been outside of VRM conversations. A concern I have, within VRM conversations, is framing solutions in terms and contexts of the existing marketing system, which is getting more and more complicated by the day. For a better look at that, see this post from January, and Don Marti’s first comment there, which points to this post here.

Having spent most of the last month outside the U.S., what I gather is that privacy is just as big a deal elsewhere — just a somewhat different deal. Here privacy is seen in terms of prophylaxis — and sometimes not-very-good prophylaxis. (Do Not Track, for example, is like hanging garlic on the door of your browser to ward off vampires.) In Canada and Europe it’s seen as an essential attribute of civilized life: one that must be designed into software, services and infrastructure. Leading influences on this approach are Ann Cavoukian, the Information and Privacy Commissioner for Ontario, and her office’s Privacy By Design initiative.

In fact we’ve had privacy by design for a long time in the physical world. Clothing, for example, is a privacy system. We use it to cover our “privates,” among other things. But, while we’ve had civilization for thousands of years, we’ve had the Net for only a couple decades or so. We have a long way to go. But we’ll get where we’re going faster if we’re not re-inventing the same wheels.

And I think we’ll get there better if we ground what we do in a clear understanding of what privacy is, and why it needs to guide the stuff we create and improve.

VRM at IIW

We had a packed house yesterday at VRM Day 2013a — more than fifty people — prepping for IIW , which starts today and runs for two more at the Computer History Museumin Mountain View.

IIW is an unconference. No keynotes, no panels, no sponsors controlling the agenda. At the beginning of each day, particpants (who aren’t just “attendees”) choose the topics they want to talk about, and from there on it’s all breakout sessions in separate rooms. So here are some of the session candidates we put up on the whiteboard(and also on the wiki at the first link above):

  • Intentcasting
  • Governance
  • Personal Clouds in general
  • Interoperability mapping
  • How to get 4th parties interested in verticals, e.g. health care, government, retail) “Medicine cabinet” instead of wallets
  • What average joe/jane use case(s) will drive adoption?
  • Use case deep dive — An active session, attendees simulate the use case communications between the device, pcloud, vendor, etc.
  • standards/patterns
  • Next-gen SSO (e.g.Persona)
  • Legal Hacks & License harmonization
  • Wallets & apps for transactions, photos, etc. Bitcoin as a VRM money clip, safe deposit box… (see session from the last IIW)
  • Tracking and ad blocking, and harmonizing methods and experiences
  • Bringing 4th parties into verticals, e.g…
  • Health Care VRM — “medicine cabinets” rather than “wallets”
  • Real estate
  • Banking (including credit cards, payments, transactions)
  • Retail
  • Sovereign vs./+ Administrative identities
  • Terms and policies (Customer Commons’ work, plus Patient Privacy Rights)
  • Symbols (e.g. around privacy)
  • XDI + KRL, messaging & events
  • Internet of me and my things
  • Drummond, for Respect Network:
  • Discovery “DNSSIC for #pclouds”
  • Respect Connect “Facebook connect without the downsides”
  • Dictionary seminars
  • Personal data pain points, e.g. filling out forms
  • Collect useful techs/APIs

There are lists within that list, but my patience and connectivity aren’t up to it, so I’ll leave that be for now.

Identity is personal

It’s as simple as that.

Identity is not corporate. That means no company is going to “win” at personal identity, any more than any company can win at being you or me. It makes no sense.

But meanwhile, there’s this big war going on over identity, that Mike Elgan of CultOfMac covers (from the Apple side) in Why the ‘i’ in iPhone Will Stand For ‘Identity’. Writes Mike,

Google honcho Eric Schmidt came right out and said it: “Google+ was created primarily as an identity service.”

And Om Malik nailed it when he said: “The real power of Facebook lies in controlling connected identity.”

Both Google and Facebook made big pushes to turn their social networks into solid identity services. And both those attempts have largely failed so far.

But Apple can win, Mike says. Here’s why:

think Apple can succeed where the social networks failed.

The reason is that Apple has a better deal for users. The social network proposed both a small stick and a small carrot: Use one account and use your real name because then everything is better. That approach failed.

Apple’s proposition is much better: Use the Identity iPhone, and stop keying in passwords, credit card numbers, billing information and more. As you cruise through the Internet, all the doors will open for you and you can securely use and buy and access anything you want without any work.

How Apple Will Use the Identity iPhone

Once you’ve associated your actual fingerprint with your iPhone, your iPhone becomes you — better than a photo ID, better than a signature, better than a password.

Today, a swipe of the finger on an iPhone conjures up the 4-digit passcode lock. If you spend some quality time with the Passcode Lock page in Settings, you can see that you have an option to turn it on or off, require it immediately or after one, five or fifteen minutes or after one or four hours. It also allows you to access or not access Passbook and the ability to reply to a message when the phone is locked.

All those settings may be identical to the fingerprint scanning feature of the next iPhone….

I believe Apple intends to build both NFC and fingerprint readers into iMacs and iPads.

When you set your iPhone next to the keyboard of your iMac, all your online activity will identity you to various sites, which means that you’ll have an “E-Z Pass” right through password dialogs and credit card pages. You’ll just be able to log in as you and buy stuff without typing anything…

In the Real World, you’ll be able to authenticate purchases either via Bluetooth or NFC, skipping the line at the movie theater, department store and gas station. You’ll be billed, and be able to pay for your restaurant meal without the waiter’s involvement. (Letting a stranger take your credit card out of your sight is one of the weakest links in the way commerce works right now.)

As I wrote in Identity systems, failing to communicate,

What’s fucked up about identity is that every site and service has its own identity system. None are yours. All are theirs, all are silo’d, and all are different. For this we can thank the calf-cow model of client-server computing, and we are stuck in it. That’s why we are forced to remember how we identify ourselves, separately, as calves, to many different cows, each of which act like they’re the only damn cow in the world.

And I gotta say, Apple sucks at being an identity cow. I am three different calves to Apple right now. That is, three different AppleIDs. I have spoken to Apple people many times about their need to merge customer namespaces, and they give me the same answer every time: it’s too hard. Worse, they’ve screwed it up over and over. An Apple mail account that was once  foo at mac.com then became  foo at me.com is now also  foo at icloud.com.  On that basis alone Apple amply demonstrates the namespace problem, which might be the oldest problem (that’s still with us) in all of computing.

Einstein saidNo problem can be solved from the same level of consciousness that created it. The namespace problem was created — and worsened — by companies creating more namespaces. One more bigfoot creating one more way to leverage its own private namespace to the whole world is not a solution. It’s one more problem to solve.

The only way to solve the identity problem is where the most pain is felt: at the individual level.

This is a very hard fact for enterprise-level solution-makers to grok, because at their level the solution is always yet another namespace or yet another bigfoot company pushing yet another technical solution. That, in effect, is what Mike says Apple will do here. And they will fail, just like Facebook, Google, Microsoft (remember Hailstorm and Passport?) and every other bigfoot has failed. Because they can’t solve it.

Meanwhile, we’ve solved this kind of thing before at the personal level, over and over, and we will do it again.

If you want to help work on it, come to the Internet Identity Workshop next week in Mountain View. That’s where the real work is happening.

 

Outlining -> VRM

Dave Winer‘s SmallPicture is a vendor I’ve been relating to from the start, mostly by cheering on development, for example of Fargo, the online outliner I describe here. Now that SmallPicture has a reader, I can copy and paste the HTML from my Fargo outline into WordPress under its HTML tab. This makes piling up and publishing outlines of links quite easy. So here goes:

VRM

VRM in France (where I am now)

Marketing

Personal Clouds and the Internet of Things

I hope some SmallPicture developers will show up at IIW, so we can talk about possibilities there.

Prepping for #VRM Day and #IIW

The 16th IIW (Internet Identity Workshop) is coming up, Tuesday to Thursday, 7-9 May, will be tat the Computer History Museum in Mountain View, CA. As usual, VRM will be a main topic, with lots of developers and other interested folk participating. Also as usual, we will have a VRM planning day on the Monday preceding: 6 May, also at the CHM. So that’s four straight days during which we’ll get to present, whiteboard, discuss and move forward the many projects we’re working on. From the top of my head at the moment:

  • Personal Clouds, including —
    • The Internet of Me and My Things
    • QS (Quantified Self) and Self-Hacking
  • Fully personal wallets, rather than branded ones that work only with payment silos and their partners
  • Intentcasting — where customers advertise their purchase intentions in a secure, private and trusted way, outside of any vendor’s silo
  • Browser add-ons, extensions, related developments
  • Licensing issues
  • Sovereign and administrative identity approaches, including Persona, formerly BrowserID, from Mozilla
  • Legal issues, such as creating terms and policies that individuals assert
  • Tracking and ad blocking, and harmonizing methods and experiences
  • Health Care VRM
  • Devices, such as the freedom box
  • VRM inSovereign vs./+ Administrative identities
    • Real estate
    • Banking (including credit cards, payments, transactions)
    • Retail
  • Personal data pain points, e.g. filling out forms
  • Trust networks
  • Harnessing adtech science and methods for customers, rather than only for vendors

The morning will be devoted to VRM issues, while the afternoon will concentrate on personal clouds.

We still have eight tickets left here. There is no charge to attend.

In the next few days here on the blog we’ll be going over some of the topics above. Input welcome.

 

VRN Linkage

A roundup of VRM-related tweets and posts…

Tweets:

Posts:

The best VRM post, ever

One of the most mind-blowing one-liners I ever heard tossed was this one:

“All the significant trends start with technologists.”

It was uttered by Marc Andreessen  during an interview I did with him for Linux Journal, in May 1998, for the August issue of the magazine, following up on Netscape’s open source release of Mozilla. The title of the piece was Betting on Darwin. It’s still up at that link, and an interesting piece of history.

That one-liner knocked me over because it is so obvious and true, yet easily overlooked. It is also exactly the reason I started ProjectVRM. I knew it needed technologists. Not just to develop code, but to fully understand  the challenges and opportunities that call technology forth into the world.

Lately one of those technologists has stepped forward and written the best VRM post I’ve ever read, including all of my own. It’s by T.Rob, in his blog The Odd is Silent. The title is Futurists Groundhog Day. An excerpt:

Why VRM?

VRM, or Vendor Relationship Management, is a new approach to conducting business in which the missing physical constraints have been replaced by technological and policy constraints that restore the balance of power between individuals and their vendors, and perhaps to some extent also their governments.

One of the issues is asymmetry in the cost of data collection.  Vendors spread the capital cost of data collection over a large population of customers.  Given enough time, the cost of data collection drops to near-zero or in some cases actually generates returns.  Consumers on the other hand have no such infrastructure.  You are co-owner of your transactional data but your grocer records each line item of your purchase in real time and you get a cryptic paper receipt which you have the option to transcribe into a database.  If you had a database.  And knew how to program.

VRM proposes to provide that platform so that individuals will have the means to capture more of their own data at a cost that is competitive with their vendors.  Indeed, the vision is that the vendors who already have that data will some day participate in the VRM ecosystem by sharing it with their customers, in real time and full resolution.  Instead of just a crappy paper receipt with unreadable abbreviated names, you’ll get the actual line items with UPC codes, prices and for some products possibly even the cradle-to-grave history and status.  You’d get your smart meter readings in real time so that you could program home automation behaviors based on load, utility rate, occupancy and so forth.  When you purchase online, the terms of the contract, price and all other metadata about the purchase would either be captured by you or delivered to you in real time by the vendor.

But VRM is about a lot more than just replacing today’s functionality.  Just as electric motors transcended the function occupied by stem engines, VRM enables entirely new capabilities.  Many are yet to be discovered but a key new capability is intentcasting.  This is a direct signal from the individual to the market about preferences, requirements and purchase intent.

Read the whole thing.

Bonus link.

Explaining VRM

In Rallying cry for innovation – and faith, Mark Sage puts up some long excerpts from a post I made to the ProjectVRM list, explaining VRM to a skeptical marketer. The bottom lines:

VRM isn’t complicated. It’s only about giving customers means toward two things: independence and engagement. To see how that can be done, one needs to stand on the side of the customer. So that’s what we’re doing.

Go to the first link above for the whole thing.

The VRM perspective

The VRM perspective is independence.Liberty Bell

This isn’t new. In fact, it’s as old as the Net. It is also nearly forgotten. Billions have never experienced it.

When the Net first came into common use, in 1995, independence was what anybody felt who started up a browser and surfed from place to place, or who built a site on a domain of one’s own, with its own name and email addresses.

To do anything substantive on the Net today, we use personalized services that require us to live inside corporate walled gardens. We have these with Google apps and Drive, Apple’s iCloud, and “social” systems such as Facebook and Twitter. Adobe and Microsoft are also now pushing hard for us to rent software as a service (SaaS), so we no longer own and run software for ourselves on our own machines.

Bruce Schneier compares today’s walled gardens to castles in a feudal system. We are vassals within these systems. Our job with VRM is not to fight these systems, but to equip individuals with their own tools of independence and engagement: to make them the points of integration for their own data, and of origination for what gets done with it.

To cease being vassals requires that we possess full agency: the power to act, with effect. We cannot do that without tools that are ours alone. Just as our bodies and souls are ours alone, yet also work in human society, we need tools that are ours alone, yet also work in the world of connections that comprises the Net.

To operate with full agency we need a full box of VRM tools — plus two other things. One is substitutability of the services we engage. The other is freedom of contract.

Substitutability means we have a choice, say, of intentcasting services, of quantified self gizmos and service providers, of health care data and service providers, and of trust networks and personal cloud service providers — just as we have a choice today among email service providers, including the choice to host our own email.

Freedom of contract means we don’t always have to subordinate our power and will to dominant parties in calf-cow ceremonies (e.g. clicking “accept” to one-sided terms we don’t read because there’s no point to it). We can design automated processes by which both parties come to mutually respectful agreements, just as we have with handshake agreements in the physical world.

Both of these virtues need to be design principles for VRM developers. If they are, we can save the Net by empowering ourselves.

 

The all-silo mobile marketplace

In the beginning was the browser, and the browser was yours. You drove it on the Information Superhighway of the World Wide Web:

As a driver, you experienced the same kind of independence that you did with a car. You had a private space inside a private vehicle that you alone operated. You thought and spoke about it with first person possessive pronouns. So, just as you still think and speak of my car, with my engine and my tires, you also thought and spoke of my browser with my bookmarks and my history.

But, because the Web was designed on the client-server model (aka calf-cow), sites could do what t hey wanted with your vehicle. So, while each site gave you both what you came for (pages, usually), it also gave you cookies to help you both remember where you were the last time you visited. And, for the convenience of you both, it also gave you a shopping cart. Thus, to them, and to you, this is what your browser became:

But there was a cost to this: you were no longer an independent human being with your own private space, but a shopper in the site’s private space. This asymmetry of power and dependence was — and remains — so absolute that it became pro forma for sites and services to use the first person possessive pronoun for you: myspace, myfitnesspal, myverizon. This only made sense in the context of not being able to say it for ourselves.

As a result, our browsers on the commercial Web are not really our own. They are re-skinned at each site with whatever the site wants to make of them:

On the commercial Web, we may still think we’re drivers, but inside each site we are passengers — or, in the now-favored lingo of retailing, “guests.”

Being guests rather than drivers has put us each in a slow-cook hell with these features/bugs:

  • Accumulating up to hundreds of different password-login combinations
  • Needing to fill and re-fill hundreds of mostly-redundant forms, over and over again
  • Submiting just as often to one-sided terms of service that we never read because there’s no point to it

This absolute submissiveness, this complete yielding of personal power to “providers” of all kinds, has boundless upsides. But it has been a Faustian bargain from the start. What we deal away is our time and our agency, both of which matter to our souls.

Seeing the success to be found in dominating customers online, brick-and-mortar retailers have replicated some of the same systems, requiring that regular customers carry around loyalty cards, one for each store. Here’s how “loyalty cards” shows up in Google’s Ngram Viewer:

The timing is no coincidence. Nor are the inconveniences these cards impose on customers and stores alike. But, so long as “free” means “your choice of captor,” the captive-captor system prevails.

That’s what’s happening in the mobile space as well.Shopping carts on websites have become the shopping apps on smartphones. The result is an all-proprietary subset of the World Wide Web:

And they proliferate. If you go to CVS, you get told to download an app. If you’ve already done that, you get told to download another one:

cvs pitch

Or so it appears. I just spent 20 minutes trying to figure out if the Pill Identifier is a feature of the CVS pharmacy app, or an app of its own. Hard to tell when you look up “cvs” on Apple’s App Store app:

To CVS, these are all conveniences for both of you. Never mind that these end up cluttering your phones. Nor that you can only get these (at least on the iPhone) at just Apple’s store, and that your phone company also controls what you can do with it (far more than any car company controls what you can do with the car you buy, lease or rent from them). The inconvenience is yours, not theirs.

The benefits, again, are enormous. For example, it is surely a good thing, for some people, to know what kinds of pills they have. And it’s a good thing that CVS provides a way to do that. But it’s CVS’s app, not yours.

To get the difference, consider an ordinary thermometer.  When you buy one from CVS, it’s yours when you walk out of the store. It isn’t CVS’s any more. Maybe it would be good if the thermometer were smart enough to communicate  your temperature to your doctor or to CVS. But that option should be yours, not CVS’s. Yet there are many who would urge CVS to get your temperature, if it can. And these are the people who are running the “big data” conversation today, at least around marketing.

We are already down a steep and slippery slope here.

See, once you have an app, it’s hard to know for sure what information about you and your life the app is sending back to the company, or to its third parties. According to the Wall Street Journal, countless apps are reporting on you and your activities to marketers, without telling you that’s what they’re doing. Or at least not in an obvious way. Yes, they have privacy policies, but nearly all of them reserve the right to change those. And yes, you do have the choice to not participate in the app marketplace. But as the world becomes more and more networked, that becomes less and less of a practical option.

In respect to the Faustian bargain with the all-silo marketplace, it doesn’t matter how good the silos get. They are still silos. Making better silos doesn’t solve the problem.

After awhile all this power asymmetry adds up, and at some point it breaks. Our job with VRM is to make that  break happen — by showing customers and providers alike that there are better ways to operate a free marketplace, starting with free customers. We do that through tools and services that are more like cars than like shopping carts: that make us both independent and equipped to engage.

A list of VRM developers is here.

Bonus links:

 

Older posts Newer posts

© 2018 ProjectVRM

Theme by Anders NorenUp ↑