Category: Terms & Conditions (page 2 of 2)

It’s People vs. Advertising, not Publishers vs. Adblockers

By now hundreds of millions of people have gone to the privacy aisles of the pharmacy departments  in their local app stores and chosen a brand of sunblock to protect themselves from unwanted exposure to the harmful rays of advertising online.

There are many choices among potions on those shelves, but basically they do one, two or three of these things:

blockers

The most popular ad blocker, Adblock Plus, is configurable to do all three, but defaults to allow “acceptable”* ads and not to block tracking.

Tracking protection products, such as Baycloud Bouncer, Ghostery, Privacy Badger and RedMorph, are not ad blockers, but can be mistaken for them. (That’s what happens for me when I’m looking at Wired through Privacy Badger on Firefox.)

It is important to recognize these distinctions, for two reasons:

  1. Ad blocking, allowing “acceptable” ads, and tracking protection are different things.
  2. All three of those things answer market demand. They are clear evidence of the marketplace at work.

Meanwhle, nearly all press coverage of what’s going on here defaults to “(name of publisher or website here) vs. ad blockers.”

This  misdirects attention away from what is actually going on: people making choices in the open market to protect themselves from intrusions they do not want.

Ad blocking and tracking protection are effects, not causes. Blame for them should not go to the people protecting themselves, or to those providing them with means for protection, but to the sources and agents of harm. Those are:

  1. Companies producing ads (aka brands)
  2. Companies distributing the ads
  3. Companies publishing the ads
  4. All producers of unwanted tracking

That’s it.

Until we shift discussion to the simple causes and effects of supply and demand, with full respect for individual human beings and the legitimate choices they make in the open marketplace, to protect the sovereign personal spaces in their lives online, we’ll be stuck in war and sports coverage that misses the simple facts underlying the whole damn thing.

Until we get straight what’s going on here, we won’t be able to save those who pay for and benefit from advertising online.

Which I am convinced we can do. I’ve written plenty about that already here.

* These are controversial. I don’t go into that here, however, because I want to shift attention from spin to facts.

 

 

Save

Save

Save

Save

Save

Save

Save

At last, a protocol to connect VRM and CRM

person-entity

We’ve been waiting a long time for a protocol to connect VRM (customers’ Vendor Relationship Management) with CRM (vendors’ Customer Relationship Management).

Now we have one. It’s called JLINC, and it’s from JLINC Labs. It’s also open source. You’ll find it at Github, here. It’s still early, at v.0.3. So there’s lots of opportunity for developers and constructive hackers of all kinds to get involved.

Specifically, JLINC is a protocol for sharing data protected by the terms under which it is shared, such as those under development by Customer Commons and the Consent and Information Sharing Working Group (CISWG) at Kantara.

The sharing instance is permanently recorded in a distributed ledger (such as a blockchain) so that both sharer and recipient have a permanent record of what was agreed to. Additionally, both parties can build up an aggregated view of their information sharing over time, so they (or their systems) can learn from and optimize it.

The central concept in JLINC is an Information Sharing Agreement (ISA). This allows for—

  1. the schema related to the data being shared so that the data can be understood by the recipient without prior agreement
  2. the terms associated with the data being shared so that they can be understood by the recipient without prior negotiation
  3. the sharing instance, and any subsequent onward sharing under the same terms, to be permanently recorded on a distributed ledger of subsequent use (compliance and analytics)

To test and demonstrate how this works, JLINC built a demonstrator to bring these three scenarios to life. The first one tackled is Intentcasting , a long-awaited promise of VRM. With an Intencast, the customer advertises her intention to buy something, essentially becoming a qualified lead. (Here are all the ProjectVRM blog posts here with the Intentcasting tag.)

Obviously, the customer can’t blab her buying intention out to the whole world, or marketers would swarm her like flies, suck up her exposed data, spam her with offers, and sell or give away her data to countless other parties.

With JLINC, intention data is made available only when the customer’s terms are signed. Those terms specify permitted uses. Here is one such set (written for site visiting, rather than intentcasting):

UserSubmittedTerms2ndDraft

These say the person’s (first party’s) data is being shared exclusively with the second party (the site), for no limit in time, for the site’s use only, provided the site also obey the customer’s Do Not Track signal. I’m showing it because it lays out one way terms can work in a familiar setting

For JLINC’s intentcasting demonstration, terms were limited to second party use only, and a duration of thirty days. But here’s the important part: the intentcast spoke to a Salesforce CRM system, which was able to—

  1. accept or reject the terms, and
  2. respond to the intentcast with an offer,
  3. while the handshake between the two was recorded in a blockchain both parties could access

This means that JLINC is not only a working protocol, but that there are ways for VRM tools and systems to use JLINC to engage CRM systems. It also means there are countless new development opportunities on both sides, working together or separately.

Here’s another cool thing:  the two biggest CRM companies, Salesforce and Oracle, will hold their big annual gatherings in the next few weeks. This means JLINC and VRM+CRM can be the subjects of both conversation and hacking at either or both events. Specifically, here are the dates:

  1. Oracle’s OpenWorld 2016 will be September 18-22.
  2. Salesforce’s Dreamforce 2016  will be October 4-7.

Both will be at the Moscone Center in San Francisco.

Conveniently, the next VRM Day and IIW will both also happen, as usual, at the end of October:

  1. VRM Day will be October 24.
  2. Internet Identity Workshop (IIW’s XXIIIth) will be October 25-27.

Both will take place at the Computer History Museum, in downtown Silicon Valley. And JLINC, which was launched at the last VRM Day, is sure to be a main topic of discussion, starting at VRM Day and continuing through IIW, which I consider the most leveraged conference in the world, especially for the price.

If all goes well, we’ll have some examples of VRM+(Oracle and/or Salesforce) CRM to show off at Demo Day at IIW.

Love to see other CRM vendors show up too. You listening, SugarCRM? (I spoke about VRM+CRM at SugarCon in 2011. Here’s my deck from that talk. What we lacked then, and since, was a protocol for that “+”. Now we have it. )

Big HT to Iain Henderson of both JLINC Labs and Customer Commons, for guiding this post, as well as conducting the test that showed, hey, it can be done!

 

 

 

 

Save

The Castle Doctrine

home castle

The Castle doctrine has been around a long time. Cicero (106–43 BCE) wrote, “What more sacred, what more strongly guarded by every holy feeling, than a man’s own home?” In Book 4, Chapter 16 of his Commentaries on the Laws of England, William Blackstone (1723–1780 CE) added, “And the law of England has so particular and tender a regard to the immunity of a man’s house, that it stiles it his castle, and will never suffer it to be violated with impunity: agreeing herein with the sentiments of ancient Rome…”

Since you’re reading this online, let me ask, what’s your house here? What sacred space do you strongly guard, and never suffer to be violated with impunity?

At the very least, it should be your browser.

But, unless you’re running tracking protection in the browser you’re using right now, companies you’ve never heard of (and some you have) are watching you read this, and eager to use or sell personal data about you, so you can be delivered the human behavior hack called “interest based advertising.”

Shoshana Zuboff, of Harvard Business School, has a term for this:surveillance capitalism, defined as “a wholly new subspecies of capitalism in which profits derive from the unilateral surveillance and modification of human behavior.”

Almost across the board, advertising-supported publishers have handed their business over to adtech, the surveillance-based (they call it “interactive”) wing of advertising. Adtech doesn’t see your browser as a sacred personal space, but instead as a shopping cart with ad space that you push around from site to site.

So here is a helpful fact: we don’t go anywhere when we use our browsers. Our browser homes are in our computers, laptops and mobile devices. When we “visit” a web page or site with our browsers, we actually just request its contents (using the hypertext protocol called http or https).

In no case do we consciously ask to be spied on, or abused by content we didn’t ask for or expect. That’s why we have every right to field-strip out anything we don’t want when it arrives at our browsers’ doors.

The castle doctrine is what hundreds of millions of us practice when we use tracking protection and ad blockers. It is what called the new Brave browser into the marketplace. It’s why Mozilla has been cranking up privacy protections with every new version of Firefox . It’s why Apple’s new content blocking feature treats adtech the way chemo treats cancer. It’s why respectful publishers will comply with CHEDDAR. It’s why Customer Commons is becoming the place to choose No Trespassing signs potential intruders will obey. And it’s why #NoStalking is a good deal for publishers.

The job of every entity I named in the last paragraph — and every other one in a position to improve personal privacy online — is to bring as much respect to the castle doctrine in the virtual world as we’ve had in the physical one for more than two thousand years.

It should help to remember that it’s still early. We’ve only had commercial activity on the Internet since April 1995. But we’ve also waited long enough. Let’s finish making our homes online the safe places they should have been in the first place.

 

Why #NoStalking is a good deal for publishers

"Just give me ads not based on tracking me.."

That line, scribbled on a whiteboard at VRM Day recently at the Computer History Museum, expresses the unspoken social contract we’ve always had with ad-supported print publications in the physical world. But we never needed to say it in that world, for the same reason we never needed to say “don’t follow me out of your store,” or “don’t use ink that will give me an infection.” Nobody ever would have considered doing anything that ridiculously ill-mannered.

But following us, and infecting our digital bodies (e.g. our browsers) with microbes that spy on us, is pro forma for ad-supported publishers on the Internet. That’s why Do Not Track was created in 2007, and a big reason why since then hundreds of millions of us have installed ad blockers and tracking protection of various kinds in our browsers and mobile devices.

But blocking ads also breaks that old social contract. In that sense it’s also ill-mannered (though not ridiculously so, given the ickyness that typifies so much advertising online).

What if we wanted to restore that social contract, for the good of publishers that are stuck in their own ill-mannered death spiral?

The first and easiest way is by running tracking protection alone. There are many ways of doing that. There are settings you can make in some browsers, plus add-ons or extensions from Aloodo, BaycloudDisconnect, the EFF and others.

The second is requesting refined settings from browser makers. That’s  what @JuliaAnguin does in this tweet about the new Brave browser:

Julia Angwin's request to Brave

But why depend on each browser to provide us with a separate setting, with different rules? How about having our own pro forma rule we could express through all our browsers and apps?

We have the answer, and it’s called the NoStalking rule. In fact, it’s already being worked out and formalized at the Kantara Initiative and will live at Customer Commons, where it will be legible at all three of these levels:

3way

It will work because it’s a good one for both sides. Individuals proffering the #NoStalking term get guilt-free use of the goods they come to the publisher for, and the publisher gets to stay in business — and improve that business by running advertising that is actually valued by its recipients.

The offer can be expressed in one line of code in a browser, and accepted by corresponding code on the publisher’s side. The browser code can be run natively (as, for example, a choice in the Brave menu above) or through an extension such as an ad or tracking blocker. In those cases the blocker would open the valve to non-tracking-based advertising.

On the publisher’s side, the agreement can be automatic. Or simply de facto, meaning the publisher only runs non-tracking based ads anyway. (As does, for example, Medium.) In that case, the publisher is compliant with CHEDDAR, which was outlined by Don Marti (of Aloodo, above) and discussed  both at VRM Day and then at  IIW, in May. Here’s an icon-like image for CHEDDAR, drawn by Craig Burton on his phone:

Sketch - 7

To explain CHEDDAR, Don wrote this on the same whiteboard where the NoStalking term above also appeared:

cheddar

For the A in CHEDDAR, if we want the NoStalking agreement to be accountable from both sides, it might help to have a consent receipt. That spec is in the works too.

What matters most is that individuals get full respect as sovereign actors operating with full agency in the marketplace. That means it isn’t good enough just for sites to behave well. Sites also need to respond to friendly signals of intent coming directly from individuals visiting those sites. That’s why the NoProfiling agreement is important. It’s the first of many other possible signals as well.

It also matters that the NoProfiling agreement may be the first of its kind in the online world: one where the individual is the one extending the offer and the business is the one agreeing to it, rather than the other way around.

At VRM Day and IIW, we had participants affiliated with the EFF, Mozilla, Privacy Badger, Adblock Plus, Consent Receipt, PDEC (Personal Data Ecosystem Consortium),  and the CISWG (Consent & InfoSharing Working Group), among others. Work has continued since then, and includes people from the publishing, advertising and other interested communities. There’s a lot to be encouraged about.

In case anybody wonders if advertising can work as well if it’s not based on tracking, check out Pedro Gardete: The Real Price of Cheap Talk: Do customers benefit from highly targeted online ads?  by Eilene Zimmerman (@eilenez) in Insights by Stanford Business. The gist:

Now a new paper from Stanford Graduate School of Business professor Pedro Gardete and Yakov Bart, a professor at Northeastern University, sheds light on who is likely to benefit from personalized advertising and identifies managerial best practices.

The researchers found that highly targeted and personalized ads may not translate to higher profits for companies because consumers find those ads less persuasive. In fact, in some cases the most effective strategy is for consumers to keep information private and for businesses to track less of it.

You can also mine the oeuvres of Bob Hoffman and Don Marti for lots of other material that makes clear that the best advertising is actual advertising, and not stalking-based direct marketing that only looks like advertising.

Our next step, while we work on all this, is to put together an FAQ on why the #NoProfiling deal is a good one for everybody. Look for that at Customer Commons, where terms behind more good deals that customers offer will show up in the coming months.

Newer posts

© 2018 ProjectVRM

Theme by Anders NorenUp ↑