9 Matching Annotations
  1. Jul 2019
    1. hasFeature() method. In the code below I ask if the browser has implemented the Core 2.0 & 3.0 specification.

      hasFeature() has been deprecated. It always returns true now. https://dom.spec.whatwg.org/#dom-domimplementation-hasfeature

    2. In Safari, Chrome, and Opera the document.doctype does not appear in the document.childNodes list.

      This doesn't seem to be true in modern Safari and Chrome anymore. document.doctype == document.childNodes[0] evaluates to true in both Safari 12 and Chrome 75.

  2. Mar 2019
    1. A locally unique and never reassigned identifier within the Issuer for the End-User, which is intended to be consumed by the Client

      I wonder why this ID must be "unique and never reassigned...within the Issuer". This effectively makes it a trackable ID if clients work together.

      What would break if this ID is unique within the (Issuer, client) combination.

  3. Feb 2019
    1. Less than a third of the apps that collect identifiers take only the Advertising ID, as recommended by Google's best practices for developers.

      33% apps violate Google Advertising ID policy

  4. Aug 2018
    1. The Economist, another longtime Blendle publishing partner that has stories featured in both the European and US versions of the platform. Alexandre says revenue from single-article sales is going to be incremental to The Economist’s bottom line for the foreseeable future, but she thinks it has a role to play in driving sign-ups to the Economist.com.
    2. Taylor says Blendle probably won’t be a long-term part of her media diet because of sharing issues. “I just want to share some articles with friends of mine,” she says, “and some of those friends have limited budgets and will not be signing up for Blendle.”
    3. Currently around one in five of those who register end up connecting their credit card to the service to continue reading.

      Blend teaser conversion rate

  5. Jul 2018
    1. There's a network effect. You have to be on the same annotation service as the people whose annotations you want to see. This leads to centralization.

      A Mastadon-like federated model can solve this problem.

    1. MUST NOT contain a fragment component

      Why not?