1. 44
    1. 16

      The “ni” in “ni://” stands for “named information,” for anyone else who’s wondering.

      1. 15

        I honestly thought it was a Monty Python reference.

        1. 30

          “You must fetch a shrubbery with the following SHA-256 digest…”

    2. 3

      Funnily, an early prototype of the Subresource Integrity specification used that syntax. Everyone hated it so we switched to the current grammar e.g., sha256-base64ofdigest. Not sure I remember why we use base64 instead of hexdigest. Maybe to win some bytes?

      (Aside: base64 gave us other issues: some browsers accept base64url, some don’t. Some are forgiving with padding, some aren’t)

      1. 2

        Everyone hated what, the ni:/// prefix? Otherwise it’s just sha-256-32;<base64url>

        1. 2

          Rethinking, maybe we took the other grammar for aligning with CSP hash sources (which were only supported for inline scripts back then). My memory is hazy on this.

    3. 3

      I’m not going into the binary and human speak-able versions. I don’t want to suffer.

      But no! Surely these are the interesting parts of the NFC.

      1. 3

        You forced my hand, binary and human-speakable formats added to the article.

        1. 3

          Thank you for your service.

    4. 2

      I implemented this in Go a while ago: https://codeberg.org/rumpelsepp/ni