VRM

You are currently browsing the archive for the VRM category.

Not want.

Need.

If a site has one of these…

social-signin

… what is the least information they need from the user?

Seems to me that “social” login buttons like these are meant for the convenience of the user. But too often liberties are taken with them.

For example, here is what one company says in its terms & conditions:

Certain functionality may enable you to log-in using Facebook Connect, a Facebook, Inc. application, which is intended to provide interconnectivity between the Services and your Facebook.com profile. By using the Connect feature, you permit us to access your facebook.com profile, including without limitation,  information about you, your friends and privacy settings. When you use the Connect feature, you also agree to allow Facebook, Inc. to use information about your activities on our site and to access your facebook.com cookies.

This is an otherwise respectful (and respectable) company, which is why I’m not naming them here. They are also a retailer, and not supported by advertising. Nor is their offering “social” in the “social media” sense.

And, while the company might want Facebook profile stuff to better understand their customers, do they need it?

In answering the question, What do fully respectful sites need from social login?, it helps to ask another question: What does the individual need from that button, other than to log in with one click?

I’m asking these questions because this button here…

respect-connect-button

… needs definition of what respectful login is.

As I said in Time for Digital Emancipation, the definition (via the Respect Trust Framework) is that the user and the site respect each other’s boundaries. So we need to say what those boundaries are, or what they might be under different conditions. But a good place to start is by asking what the bare minimum needs of a site are.

So, what are they?

Civilization is a draft. Provisional. Scaffolded. Under construction. For example:

DEC. OF INDEP. 1

That’s Thomas Jefferson‘s rough draft of the Declaration of Independence. The Declaration hasn’t changed since July 4, 1776, but the Constitution built on it has been amended thirty-three times, so far. The thirteenth of those abolished slavery, at the close of the Civil War, seventy-seven years after the Constitution was ratified.

Today we are in another struggle for equality, this time on the Net. As Brian Grimmer put it to me, “Digital emancipation is the struggle of the century.”

There is an ironic distance between those first two words: digital and emancipation. The digital world by itself is free. Its boundaries are those of binary math: ones and zeroes. Connecting that world is a network designed to put no restrictions on personal (or any) power, while reducing nearly to zero the functional distance between everybody and everything. Costs too. Meanwhile, most of what we experience on the Net takes place on the World Wide Web, which is not the Net but a layer on top of it. The Web is built on architectural framework called client-server. Within that framework, browsers are clients, and sites are servers. So the relationship looks like this:

calf-cow

In other words, client-server is calf-cow. (I was once told that “client-server” was chosen because “it sounded better than ‘slave-master.’” If anyone has the facts on that, let us know.)

Bruce Schneier gives us another metapor for this asymmetry:

It’s a feudal world out there.

Some of us have pledged our allegiance to Google: We have Gmail accounts, we use Google Calendar and Google Docs, and we have Android phones. Others have pledged allegiance to Apple: We have Macintosh laptops, iPhones, and iPads; and we let iCloud automatically synchronize and back up everything. Still others of us let Microsoft do it all. Or we buy our music and e-books from Amazon, which keeps records of what we own and allows downloading to a Kindle, computer, or phone. Some of us have pretty much abandoned e-mail altogether … for Facebook.

These vendors are becoming our feudal lords, and we are becoming their vassals.

It’s handy being a vassal. For example, you get to use these shortcuts into websites that require logins:

social-signin

To see how much personal data you risk spilling when you click on the Facebook one, visit iSharedWhat (by Joe Andrieu) for a test run. That spilled data can be used in many ways, including surveillance. The Direct Marketing Association tells us the purpose of surveillance is to give you a better “internet experience” through “interest-based advertising—ads that are intended for you, based on what you do online.” The DMA also provides tools for you to manage experiences of what they call “your ads,” by clicking on this tiny image here:

adchoicesbutton

It appears in the corners of ads from companies in the DMA’s AdChoice program. Here is one:

scottrade

The “AdChoices” text appears when you mouse over the icon. When I click on it, I get this:

scottradepopdown

Like most companies’ privacy policies, Scottrade’s says this: “Scottrade reserves the right to make changes to this Online Privacy Policy at any time.” But never mind that. Instead look at the links that follow. One of those leads to Opt Out From Behavioral Advertising By Participating Companies (BETA). There you can selectively opt out of advertising by dozens of companies. (There are hundreds of those, however. Most don’t allow opting out.)

I suppose that’s kind of them; but for you and me it’s a lot easier just to block all ads and tracking on our own, with a browser extension or add-on. This is why Adblock Plus tops Firefox’s browser add-ons list, which includes many other similar products as well. (The latest is Privacy Badger, from the EFF, which Don Marti visits here.)

Good as they are, ad and tracking blockers are still just prophylactics. They make captivity more bearable, but they don’t emancipate us. For that we need are first person technologies: ways to engage as equals on the open Net, including the feudal Web.

One way to start is by agreeing about how we respect each other. The Respect Trust Framework, for example, is a constitution of sorts, “designed to be self-reinforcing through use of a peer-to-peer reputation system.” Every person and company agreeing to the framework is a peer. Here are the five principles to which all members agree:

Promise We will respect each other’s digital boundaries

Every Member promises to respect the right of every other Member to control the Member Information they share within the network and the communications they receive within the network.

Permission We will negotiate with each other in good faith

As part of this promise, every Member agrees that all sharing of Member Information and sending of communications will be by permission, and to be honest and direct about the purpose(s) for which permission is sought.

Protection We will protect the identity and data entrusted to us

As part of this promise, every Member agrees to provide reasonable protection for the privacy and security of Member Information shared with that Member.

Portability We will support other Members’ freedom of movement

As part of this promise, every Member agrees that if it hosts Member Information on behalf of another Member, the right to possess, access, control, and share the hosted information, including the right to move it to another host, belongs to the hosted Member.

Proof We will reasonably cooperate for the good of all Members

As part of this promise, every Member agrees to share the reputation metadata necessary for the health of the network, including feedback about compliance with this trust framework, and to not engage in any practices intended to game or subvert the reputation system.

The Respect Network has gathered several dozen founding partners in a common effort to leverage the Respect Trust Framework into common use, and within it a market for VRM and services that help out. I’m involved with two of those partners: The Searls Group (my own consultancy, for which Respect Network is a client) and Customer Commons (in which I am a board member).

This summer Respect Network launched a crowd-funding campaign to get this new social login button rolling:

respect-connect-button

It’s called the Respect Connect button, and it embodies all the principles above; but especially the first one: We will respect each others’ digital boundaries. This makes itthe first safe social login button.

Think of the Respect Connect button project as a barn raising. There are lots of planks (and skills) you can bring, but the main ones will be your =names (“equals names”). These are sovereign identifiers you own and manage for yourself — unlike, say, your Twitter @ handle, which Twitter owns. (Organizations — companies, associations, governments — have +names and things have *names.)

Mine is =Doc.

Selling =names are CSPs: Cloud Service Providers. There are five so far (based, respectively, in Las Vegas, Vienna, London, New York/Jerusalem and Perth):

bosonweb-logo danube_clouds-logo paoga-logo emmett_global-logo onexus-logo

Here’s a key feature: they are substituable. You can port your =name from one to the other as easily as you port your phone number from one company to another. (In fact the company that does this in the background for both your =name and your phone number is Neustar, another Respect Network partner.)

You can also self-host your own personal cloud.

I just got back from a world tour of places where much scaffolding work is going up around this and many other ways customers and companies can respect each other and grow markets. I’ll be reporting more on all of it in coming posts. Meanwhile, enjoy some photos.

 

I’ve been asked how EULAs — End User License Agreements — might affect the Internet of Things, now becoming better known as the IoT. Good question. The topic is hot:

google-iot-trend

Development, however, is another story. There we are headed straight into a log-jam that Phil Windley calls the Compuserve of Things. In the 80′s and early ’90s, Compuserve was as close as any of us could get to experiencing the real Internet (which was available only to a limited selection of governments, universities and big companies). Compuserve’s competitors were AOL (originally America OnLine), Prodigy, MSN and a few others not worth mentioning.

The problem was that all online services were closed and proprietary. Communication between them was difficult or impossible. Your Compuserve email only worked with other Compuserve members. Same with your Prodigy and AOL mail. Same with instant messaging (which retains its old proprietary problems even to this day.)

Where we are headed today is not the Internet of Things, but the Google of Things, the Apple of Things, the Microsoft of Things, and low-effort sports and war stories in the media misdirecting attention away from the real Internet and toward fights between giants.

Also evolving away from the Net will be the Every-BigCo-of-things, and their suppliers of proprietary platforms. (Let’s call that one EBCoT.) Every one of these, of course, will have its own EULA.

The Internet has no EULA. It just has an A, for Agreement. That’s because the Internet is defined by protocols, which are manners — agreements — among the things it connects.

For the trillions of things in the world to work in the actual Internet, they need be subject to that same agreement (and others like it, tuned for things other than computers), but not licenses from controlling parties, because that would not be the Internet.

EULAs suck already anyway, for two legacy reasons: 1) they are one-sided and coercive; and 2) nobody reads them other than the lawyers who write them. Let’s unpack both problems.

Most EULAs are what legal folk call “contracts of adhesion.” That term was coined by Friedrich Kessler in 1943, at the apex of the Industrial Age (when Industry was causing, fighting and winning WWII). Adhesive contracts, Kessler said, were the only way any one company could achieve legal scale with masses of customers and users.

But what worked as an upside for industry had a downside for everybody else, because adhesive contracts came at a cost. Freedom of contract, long a form of vernacular law in everyday life, was shoved aside by industrial expedience.

What Kessler saw as both an efficient hack and a moral drag became more of both in the Information Age in which we live today. And it be a far bigger drag if it encumbers every Thing we want to put on the Internet.

Most of us don’t read EULAs, or the privacy policies that often accompany them, because to do so is both useless and time consuming. They are useless because they exist mostly to scrape off liability and other inconveniences on the customer or user. And they suck up time because they are written in legalese, by and for lawyers, rather than the rest of us.

So: what can we do? I’ll take that up in the next post.

Bonus link: Tony Faddel on Nest’s independence from Google and why he doesn’t like “Internet of Things” as a label.

nytimesriverDave says “The New York Times home page needs a re-think.” But he doesn’t stop there, because thinking isn’t enough and complaining is worse than useless. (As I’ve often found. For example, here.)

We need to hack up something new, different, better and — most of all — simpler and easier to implement than anything the Times can do on its own.

(The Times is kinda busy now anyway. And it’s not inclined to simplicity, especially on the Web. That’s not a knock. We’re talking DNA here. But the Times can listen and act, as it did back when Martin Nisenholtz and his team followed Dave’s lead and adopted RSS, reforming and reinvigorating the whole publishing business in the process. We want the same kind of adoption and effects again this time.)

The simplest thing you can do as a programmer is leverage something Dave came up with years ago called river of news. As a reader you can blog, tweet and otherwise submit to the world your suggestions.

Hashtag: #timesriver.

Tagline: All the news that’s fit to flow.

Here’s Dave’s own current set of rivers.

That’s a handy model, but neither Dave nor I want that to restrict your thinking or your coding. We want new thinking, new hacking, new (and renewed) heads on the case and fingers on keyboards.

For that Dave has convened a hackathon. Here’s how he got it rolling:

Here’s an OPML file with all the NYT feeds I could find, in Oct 2012.#

Your task: Build a website using the flow of these feeds. A new way to sample the flow of news from the NYT.#

Here’s what I’m using now, designed years ago. Surely you can do better!#

Share a pointer to your work with this hashtag: #nytfeedfun.#

There’s a lot of data flowing through there. #

A picture of a slice of cheese cake.

PS: Deadline? We’re having an RSS meetup in NYC in mid-June.#

Guidance from my (non-programming) corner:::

Think about turning the Times from a static thing to a live one* — literally, from a paper to a river.

Think about how a river forms. Its sources are tributaries: branches that flow in, not out. The biggest rivers sustain life in their waters and alongside their banks. They are at the very core of culture and civilization. And they pour out through a delta to the ocean. The ocean is the Web. The delta is whatever we make it.

I’ll be writing more about this topic in the coming days and weeks, both in service to journalism’s cause (whatever it is — and I mean that seriously) and to wrap my tour of duty as a visiting scholar at NYU’s Arthur L. Carter,Journalism Institute. (In that I’m following the large footsteps of Dave, who served in the same post under our friend and mentor Jay Rosen.)

So hack away. I’m very eager to see the results — but not as eager as I hope the Times itself will be — for everybody’s sake. (I’m serious about that too. The Times is the anchor institution for civilization as well as journalism. Helping it adapt may be the highest calling we have.)

* Some background on the static/live distinction, written almost a decade ago, and now more relevant than ever.

Back in the mid-’00s, a group of us in Santa Barbara got some balls rolling toward fiber-ing up the City and/or the County (by the same name), since it was clear that Cox Communications, our monopoly high-speed Internet provider, cared less about our city than the rest of the ones it served. And, when we met with Cox, that’s pretty much what they told us as well: that Santa Barbara was relatively small and far away from the company’s Atlanta headquarters. Our main upside, they said, was that whatever we ended up getting would be already proven elsewhere.

Since then I’ve had a few problems with Cox, but in the last year service has actually been pretty good, as cable Internet goes. I’ve measured as high as 80Mbps down and 18Mbps up. We had a gathering of techies at our house in January, all doing heavy data lifting with their laptops and smart mobiles, without a hitch. And, when I’m elsewhere, I get to watch our Dish Network TV rig over a Slingbox and DishAnywhere, in HD. That means Cox is giving me adequate upstream as well as downstream data traffic capacity. Not bad. (Here is the current set of data plans for Santa Barbara. Not sure which one we have. Note that all have data caps. Far as I know we’ve never hit any.)

But, as they say in bad late night ads, that’s not all. Now comes news that Cox is planning gigabit fiber to homes as well as businesses. In other words, to do for its footprint what Google is doing for Kansas City, Provo and Austin.

So here is an appeal to Cox, on behalf of Santa Barbara: front-burner us this time.

Thanks.

Aral Balkan is doing a bang-up job getting Indie rolling as an adjectival meme. He’s doing it with his Indie PhoneIndie Tech Manifesto and a talk titled Free is a Lie.

To put the Indie movement in context, it helps to realize that it’s been on the tech road at least since 1964, when Paul Baranone of the Internet’s architects, gave us this design for a network:

Meaning the one on the right. The one on the left was common in those days and the one in the middle was considered inevitable. But the one on the right was radical. First, it reduced to one the “attack surface” of the network. Take out one node or one link and the rest stayed up. Second, it also served as the handy design spec for the protocols that now define the Internet. Aral, the Indie Phone and the IndieManifesto are all about the one on the right: Distributed. So, for that matter, is The Cluetrain Manifesto. For example:

That was Chris Locke’s line. “Markets are conversations” (one of my lines) and “Hyperlinks subvert hierarchy” (one of David Weinberger’s) also come from the same spot.

Marketing comes from A and B. Never C. Thus, as Jakob Nielsen told me after Cluetrain came out, “You guys defected from marketing. You sided with markets, against marketing.” Meaning we sided with individual human beings, as well as society in general. But certainly not with marketing — even though all three of us made a living in marketing. Perhaps not surprisingly, Cluetrain became, and remains, a favorite of marketers, many of which continue to defect. (Bonus link.)

Independent, sovereign, autonomous, personal and heterarchical are all adjectives for what one gets from a distributed network. (This may call forth an acronym, or at least an initialism.) By whatever name it is an essential camp, because each of us is all six of those things (including distributed). We need tech that enables those things and gives us full agency.

We won’t get them from the centralizers of the world. Or decentralizers that don’t go all the way from B to C. We need new stuff that comes from the truly personal side: from C. It helps that C — distributed — is also central to the mentality, ethos and methodologies of hacking (in the positive senses of the word).

Ever since the Net went viral in the mid-’90s, we’ve built out “solutions” mostly on the models of A and B: of centralized and decentralized. But too rarely all the way to C: the fully personal. This is understandable, given the flywheels of industry, which have the heft of Jupiter and have been spinning ever since Industry won the Industrial Revolution.

But one fully personal exception stands out: the browser. It was born to be the best instrument of individuality we could have, even though it has lately become more of a shopping cart than a car. (That was one point of Earth to Mozilla: Come back home.) If we want the browser to be fully personal (e.g. private) again — as it was in the first place, before commercial imperatives were laid upon it, and the Web looked like a library (which one would browse) rather than a shopping mall — Mozilla is our best hope for making that happen. There are no other candidates. And it’s clear to me that they do want to work toward that goal.

We won’t get rid of centralization and hierarchy. Nor should we, because there are many things centralization and hierarchy do best, and we need them to operate civilization. Our personal tools also need to engage with many of them. But we also can’t expect either centralization or decentralization to give us distributed solutions, any more than we can get government or business to give us individuality, or for hierarchy to give us heterarchy. The best we’ll get from them is respect: for us, and for the new tools we bring to the market’s table.

Aral is right when he tweets that Mozilla’s dependence on Google is an elephant in the room. It’s an obvious issue. But the distributed mentality and ethos is alive and well inside Mozilla — and, for that matter, Google. I suspect it even resides in some corner of Mark Zuckerberg’s cerebrum. (He’s too much of a hacker for it not to be there.) Dismissing Mozilla as a tool of Google throws out babies with bathwater — important and essential ones, I believe.

Meanwhile we need a name for the movement that’s happening here, and I think Aral’s right that “Indie” might be it. “Distributed” sounds like what happens at the end of a supply chain. “Heterarchical” is good, but has five syllables and sounds too academic. “Sovereign” is only three syllables (or two, depending) and is gaining some currency, but it more commonly applies to countries than to people. “Personal” is good, but maybe too common. And the Indie Web is already catching on in tech circles. And indie itself is already established as a nickname for “independent.”  So I like it.

I would also like to see the whole topic come up at VRM Day and IIW, which run from 5 to 8 May in Mountain View. The links for those:

http://VRMday2014a.eventbrite.com

http://iiworkshop.org (register at http://bit.ly/1hWpNn5)

Over on the ProjectVRM blog I make a long-form case for why Facebook buying WhatsApp for $19 billion dollars in cash and stock is a Good Thing for VRM. Here I’ll make the case for why it should uncork a fresh wave of investment in start-ups and innovation at already-ups.

  1. Payments are headed to mobile, for real. WhatsApp has already expanded from text to photography, video and more. Payments are a tall order, but they’re on the table in a much bigger way now, and not just for WhatsFace.
  2. Meet space and meat space are now one. This should be good for all the brick-and-mortar businesses in the world. But they’ll need to be ready to work with the new systems coming to market, and not just lamenting scan & scram. And, speaking of new systems…
  3. Intentcasting will become the norm. Right now we live, at least online, in an attention economy, where surfing on the Web requires swimming upstream against a torrent of unwanted messages, nearly all of which are annoying, useless, ill-mannered or all three. Replacing it will be an intention economy in which we do the advertising, and not just the sellers of the world.
  4. Free customers will prove they are more valuable than captive ones. Because they can. They will operate more and more outside the feudal empires companies have been operating throughout the history of mass marketing. And, because of this…
  5. Economic signaling will become much more loud and clear. Both ways. Demand will have many more, and better, ways of informing Supply. And vice versa. For example…
  6. Everything we buy and own can have a cloud of its own. And that cloud can be the platform for relationship between customer and company. VRM and CRM can finally connect and constantly improve what customers and companies do for each other. And we’ll get along better because relationships will be based on truly agreeable terms.
  7. Every one of us will have our own clouds too. These will be our own secure personal spaces in the connected world. Each will have its own open source operating systems (e.g. CloudOS), programming languages (e.g. KRL), privacy canon (e.g. the Respect Trust Framework) and protocols (e.g. XDI).
  8. Market based marketing. Once free customers prove more valuable than captive ones, marketers will find that actually talking to people will have a lot more leverage than trying to herd them like cattle.
  9. Mobile advertising is proving to have some negative value. Stop right now and read Four Numbers That Explain Why Facebook Acquired WhatsApp, a post by Sequoia Capital, WhatsApp’s main VC. In it they show a note on WhatsApp CEO Jan Koum’s desk, from his partner and co-founder, Brian Acton. Explains Sequoia, “Jan and Brian ignored conventional wisdom. Rather than target users with ads — an approach they had grown to dislike during their time at Yahoo — they chose the opposite tack and charged a dollar for a product that is based on knowing as little about you as possible. WhatsApp does not collect personal information like your name, gender, address, or age. Registration is authenticated using a phone number, a significant innovation that eliminates the frustration of remembering a username and password. Once delivered, messages are deleted from WhatsApp’s servers.” Then look at what Fred Wilson says about online advertising as a source of pollution. (He starts 23 minutes in. More here.)
  10. The pendulum is swinging away from centralization. The Net’s founding protocols described and supported a fully distributed architecture, in which every node on the network is a functional distance of zero from every other node. This is what made each of us far more powerful on the Net than we ever were in the world of mainframes, or in the worlds of private networks controlled by companies or governments. There are still plenty of centralities working on the open Net, but they also have vulnerabilities, as we’re finding in post-Snowden time. It’s also significant that Whatsapp uses a customized version of XMPP (originally called Jabber), the open protocol created by Jeremie Miller and the team now working on Telehash, described as “a secure wire protocol powering a decentralized overlay network for apps and devices.”

I’m sure there are plenty more, but that should provide enough for investors to chew on. Start-ups too. A lot of doors opened up yesterday. I didn’t hear any close.

— is happening this weekend in New York, San Francisco and elsewhere. Read all about it here, here and here.

I’ll be there to help start things off, at 10am tomorrow. (Registration starts at 9am.) My job on the opening panel is to make a 2-3 minute statement of what I’d like to see in the form of legal hackery. Here goes:

  1. Restore freedom of contract and obsolete contracts of adhesion by creating standardized terms individuals can assert. I have two chapters in The Intention Economy devoted to this. (The Cyberlaw Clinic at the Berkman Center is also working on these — and corresponding terms on the business side — for Customer Commons. What gets hacked this weekend can feed into that work.)
  2. Create better means for expressing personal policies and preferences (such as Do Not Track) than are currently available — and putting these in the individual’s own tool box, rather than appearing only as choices presented by others, such as browser makers.
  3. Create graphical elements (e.g. the r-button) for both the above.

On the panel I will advocate for individuals as independent entities with full agency, rather than merely “users” of others’ systems, or victims of privacy abuse awaiting policy relief. This means I will argue for thinking and hacking toward building and filing the individual’s own tool box, rather than just tweaking the broken technical and legal systems we already have. (Though doing that is good too. Others will be there to advocate and hack on that.)

It is essential that we think outside the browser for this. While the browser began as something like your car on the information superhighway, it has since become a shopping cart that gets re-skinned with every commercial site you visit, and infested at each with tracking beacons so you can be a subject of constant surveillance. This is even true of Firefox, which I love (and within which I am writing this), and which (through Mozilla) is providing space for the San Francisco hackathon.

Let me go a little deeper on this. An example of what’s right and wrong in the browser space right now can be found Christian Heilmann‘s post, Why “Just Use Adblock” Should Never Be a Professional Answer. In it he says many good things that I agree with, enthusiastically. But he also gets one big thing wrong:

Whether we like it or not, ads are what makes the current internet work. They are what ensures the “free” we crave and benefit from, and if you dig deep enough you will find that nobody working in web development or design is not in one way or another paid by income stemming from ad sales on the web.

Saying ads are what make the Internet work is like like saying cities are what make geology work. Yes, the Internet supports commercial activity, but it is not reducible to it. For each of us to enjoy full agency on the Web, this distinction needs to be clear from the start.

Browser makers are stuck right now between many rocks (their users) and a hard place (advertising-supported websites). On the one hand they want to do right for users, and on the other they want to do right for what the ad industry now calls “publishers”. Since surveillance-fed “personalization” is big with those publishers, and lots of users don’t like it (AdBlock Plus is the top browser extention, by far), the browser makers are caught in the middle. You can see the trouble they have with this conflict in A User Personalization Proposal for Firefox, which was floated by Justin Fox of Mozilla last July. In it he writes,

We want to see even more personalization across the Web from large and small sites, but in a transparent way that retains user control. The team at Mozilla Labs is focused on exploring ways to move the Web forward, and has thought a lot about how the browser could play a role in making useful content personalization a reality.

The blowback in the comments was harsh and huge. One sample:

The last thing the internet needs is more “personalization” (read: “invasion of my privacy”). All your marketing jargon does nothing to hide the fact that this is just another tool to allow advertisers, website owners, the NSA, and others to track users online habits and, despite any good intentions you might have, it’s rife with the potential for abuse.

I’m not bringing this up to give Mozilla or the other browser makers a hard time, but to suggest that the solutions we need start outside the browser. (And seeing them that way may also be good for the browser folks.)

Simply put, what we need most are tools for ourselves, that help in our dealings with all other parties. Not just protections from bad actors, or ways to make bad practices less bad.

See ya there.

Fred WilsonI’m bummed that I missed LeWeb, but I’m glad I got to see and hear Fred Wilson’s talk there, given on Tuesday. I can’t recommend it more highly. Go listen. It might be the most leveraged prophesy you’re ever going to hear.

I’m biased in that judgement, because the trends Fred visits are ones I’ve devoted my life to urging forward. You can read about them in Linux Journal (starting in 1996), The Cluetrain Manifesto (1999, 2000, 2011), this blog (starting in 1999), ProjectVRM (starting in 2006) and The Intention Economy (2012). (Bonus links: What I said at Le Web in 2007 on stage and in an interview.)

He unpacks three megatrends, with an additional focus on four sectors. Here are my notes from the talk. Some of it is quotage, but little of it is verbatim. If you want to quote Fred, go to the source and listen.

1) We are making a transition from bureaucratic hierarchies to technology-driven networks. The former is the way the world has been organized for the last two hundred years. Markets, government, businesses are all pyramids. Transaction and communication costs were so high in the industrial era that these pyramids were the best way to organize work and run systems. But now technology-driven networks are replacing bureaucracies. Examples…

Twitter. Replaces the newspaper. The old army of reporters that reported to divisional editors who chose what would appear in limited spaces and distribute through printing mills and trucked to your doorstep was slow moving and bureaucratic. Now all of us are reporters. The crowd determines what’s important. This is an example of a tech-driven network.

YouTube. TV was hierarchical. Now all of us are video creators.

SoundCloud. Anybody can create audio or music. No labels. No radio or music industry required.

We first saw this trend in media and entertainment. Now we’re seeing it in AirBnB, One Fine Stay. Creative industries like Kickstarter and VHX. Learning with Codecademy and DuoLingo for languages.

We are very early with all of these and more to come.

2) Unbundling. This has to do with the way services are packaged and taken to market. In the traditional world, you only got to buy the thing that had everything in it. Now tech is changing that. More focused, best of breed, delivered a la carte. Now on mobile and internet you get better everything. Best of sports, fashion, classified advertising.

Banking is being unbundled. Banks used to do everything. Now entrepreneurs are picking off services. Lending Club. Funding Circle. auxsmoney in Germany. Taking profitable lending franchises away. Working capital. c2fo. Management services. All new, all based on networks.

Education. It’s expensive to put a lot of students in a building with a professor up front of every class. You needed a library. Administration. Very inefficient, costly, pyramidal and centralized. Now you can get books instantly. Research is no longer as highly centralized and capital dependent. See Science Exchange: collaboration on an open public network.  All this too is also early.

Entertainment. Used to be that you’d get it all on cable. Now we get Netflix and YouTube on our phones. Hulu. A la carte. Airplay, Chromecast.

3) We are all now personally a node on the network. We are all now nodes on the network, connected all the time. Mobiles are key. If forced to make a choice between phone and desktop, we go with the phone. (About 80% of the LeWeb audience did, along with Fred.) In the larger world, Android is being adopted massively on cheap phones. Uber, Halo.

This change is profoundly impacting the world of transportation. Rental cars. Delivery. Payments. Venmo, Dwolla, Square. Peer to peer. You can send money to anybody. For dating there’s Tinder. Again, this is new. It’s early.

The four sectors…

a) Money. Not just Bitcoin. At its core Bitcoin is a protocol: the financial and transactoinal protocol for the Net. We haven’t had one until now. As of today it is becoming a layer of internet infrastructure, through a ledger called the blockchain that is global. All transactions are cleared publicly in the blockchain. Entrepreneurs will build tech and services on this. Payments and money will flow the way content now flows. No company will control it. Others’ lock on our money will be gone.

b) Health and wellness. Health care is regulated and expensive. Health and wellness is the opposite. It’s what keeps you out of the hospitals. (QS is here.) The biologies of our bodies will be visible to us and connected. Some communications will be personal and private, some networked, some with your doctor and so on. Small example: many people today gamify their weight loss.

c) Data leakage. When the industrial revolution came along, we had polluting. It took a century to even start dealing with it. In the information revolution, the pollution is data. It’s what allows Google, Facebook and the government spy on us when we don’t want them to. We have no control over that. Yet.

d) Trust and identity. We have allowed Google, Facebook, Amazon and Twitter to be our identity services. It’s very convenient, but we are giving them access to all we do. This isn’t good. Prediction: a bitcoin-like service, a protocol, that is distributed and global, not controlled by anybody, architected like the Internet, that will emerge, that will give us control over identity, trust and data. When that emerges I’ll let you know. I haven’t seen it yet.

Talk to me, Fred. :-)

towerRadio used to be wireless audio on a broadcast band. That’s still the short version of every dictionary definition.

But now radio is streamed audio. That was already the case when webcasting* showed up in the ’90s, and even more so with the rise of Last.fm, SiriusXM, Pandora, rdio, Spotify and every other audio service delivered over the Net.

And now Apple delivers the crowning blow, with this:

This isn’t just the height of presumption on Apple’s part. It’s a body-snatch on all of radio, as well as a straight-up knock-off of Pandora.

But it’s actually worse for radio than it looks here.

What used to be called Radio (iTunes’ collection of webcasting radio stations), which had already been pushed down one directory level to “Music,” is now available only under a new button called “Internet.” (See the screenshot above.) Worse, it won’t appear unless you open preferences in iTunes and check a box to turn it on.

So Apple clearly hates radio as we’ve always known it, and could hardly be more passive-aggressive about subordinating it to their own closed, exclusive, silo’d and proprietary service. (Here’s some bonus evidence.)

So where does this leave plain old over-the-air radio — you know, the kind that fades away when you drive out of town?

Simply put, in a new context. That context is the Net. It’s the new broadcast band. Here on the Net (where you are right now), audio servers are the new transmitters and mobile devices are the new portable radios.

So, some advice.

For stations, networks and chains:

  1. Normalize to the Net. That doesn’t mean just “digital first.” It means recognizing that the Internet is your coverage area, and the new native land for all forms of radio, including Satellite. This is the lecture that @JeffJarvis has given for years, correctly, to his friend @HowardStern and to @SiriusXM, where Howard (also correctly) anchors the whole link-up.
  2. Recognize that the Net does not belong to the cable and phone companies but to nobody, which is why it covers the world. Think of it as a world of ends (where every audio source and every listener is a separate end), and NEA — nobody owns it, everybody can use it, and anybody can improve it. Including you.
  3. Choose a streaming URL (or a set of URLs) for your station(s) that will be as permanent as your over-the-air dial positions. Make sure you’re streaming in .mp3 or some other standard codec that all mobile apps can receive. (Right now the burden of finding a streaming URL in the first place is a pain in the ass.)
  4. Transmit over the air in HD. Yes, HD has problems, and the adoption rate is still low. But it’s an all-digital bridge between net-casting and over-the-air.
  5. Continue to use RDS (RDBS in the U.S.) with your analog signals. That way it will display your identity and content on radios equipped to do so, most of which, so far, are in cars.
  6. Support every possible app that moves toward re-creating the old dial-based radio experience. The closest I’ve seen so far is the BBC’s iPlayer app, which isn’t available in the U.S.
  7. Have truly unique programming. If you’re running what dozens or hundreds of other stations are running, you’re just a relay.
  8. Look toward making more money from subscriptions and voluntary donations than from advertising. More about that below.
  9. Think in terms of relationships, and not just listeners. This is essential because listeners have communication power now too. Don’t waste it by looking at them only as populations. This isn’t easy, because the grooves of one-way-one-to-many non-relating are nearly a century deep. But those who relate best will win biggest.
  10. Make podcasting a normal and easy part of your mix of offerings. More listeners will listen, more of the time (which they will make for themselves.) And, if you can’t easily podcast because you’re doing music, see the last section below.

For app developers:

  1. Keep up the pioneering work done by Tune InWunderradioPRX’s Public Radio PlayerStitcher and the rest. But note this…
  2.  No app yet (to my knowledge, at least) re-creates the simple experience we got from knobs, dials and uncomplicated read-outs on good old-fashioned radios. In effect we’re still stuck where mp3 players were before the iPad came along with its scroll wheel. Only now the shitty experience is on our mobile devices, including our Apple i-things.
  3. Ease the experience of listening, and recording (like with DAR.fm), across everything possible. I know this isn’t easy, because chains like Clear Channel (with its iHeartRadio) and the BBC like to limit listening within their app to their own stations. But this isn’t what most listeners want.
  4. Work toward a single easy non-proprietary way to support subscription services (such as SiriusXM) and volunteer-pay services, (such as public radio stations in the U.S). Everybody with that model will make more money, much more easily, if the process isn’t different for every station, every network, every service.
  5. Symbolize relationships (especially paid ones) with UI elements that are easy to read and universally used and accepted. I recommend the r-button, which the VRM development community came up with, and which is there for the taking. The ⊂ represents the person’s side of the relationship, while the ⊃ is the ‘caster’s. If you’re interested, talk to me about it.
  6. Think relationships, not just listeners.

For equipment makers:

  1. Quit making shitty radios. The receiving circuitry and antennas for most home and portable radios have been awful for awhile now, and I don’t expect them to get better. But I think there is room for some companies still making radios to put out a few actually good ones. And include HD.
  2. Ibiquity (developer and licensor of HD Radio technology): change your game. Adoption by equipment makers is clearly too slow and too hard. Hell, you’ve been around since 2001, and now you’re bragging on just the first car to feature it. This search on Amazon for “HD Radio” should bring up lots of results, rather than a few hens’ teeth.
  3. Make radios that hunt easily from over the air analog to HD Radio to streams on the Net.

For everybody:

  1. Lobby to get rid of the completely aversive royalty system for webcasting, and its inequities with over-the-air broadcasting. Replace it with something sane and respectful of the all-digital world in which we now live.
  2. In respect to the link above, note this language: Sections 112 and 114 require that rates for the statutory licenses for webcasting and for ephemeral recordings must be the rates that most clearly represent the rates that would have been negotiated in the marketplace between a willing buyer and a willing seller. That boldfaced language is a relic of the DMCA, which was passed in ’98 — just three years after the dawn of the graphical browser, before anybody could imagine that the Net could support willing buyers and sellers of streamed music. The effect of this has been to marginalize or kill music podcasting, to name just one victim. Nobody wants the rights-holders to get screwed, but everybody should recognize by now that its the music itself, and the relationships between artists, distributors (including radio service operators) and listeners that are getting screwed by the current system. And that we can do better. Hell, it’s almost 2014. Let’s get this done.

* “Webcasting” should have been called “netcasting” in the first place. As Wikipedia says at the moment (at that last link), “Essentially, webcasting is ‘broadcasting’ over the Internet.” The difference is important because the Web is something that runs on the Net, rather than a synonym for the Net.

« Older entries