Add content verification

Signed-off-by: Jacob Kiers <jacob@jacobkiers.net>

content/posts/2021-08-17-serving-blog-content-over-dns.md

@@ -73,7 +73,7 @@ In short: just because I could. It was one of those ideas I was wondering idly a
 ### Has it any practical use?
 
 It is not intended to have any. Since DNS records are fairly small, serving images or something would quickly start
-consuming 100s of requests per second. I wouldn't want to do that to Cloudflare 😉
+consuming 100s of requests per second. I wouldn't want to do that to Cloudflare.
 
 It would be an interesting experiment to see how feasible that is.
 

content/scripts/verifier.js

@@ -0,0 +1,21 @@
+class Verifier {
+    /***
+     * @param content Content
+     */
+    async verify(content) {
+        if (!window.isSecureContext) return;
+        if (typeof TextEncoder === "undefined") return;
+        if (typeof crypto === "undefined") return;
+        const encoder = new TextEncoder();
+        const digestBuffer = await crypto.subtle.digest(content.index.hashAlgorithm, encoder.encode(content.content));
+
+        const hashArray = Array.from(new Uint8Array(digestBuffer));                     // convert buffer to byte array
+        const digest = hashArray.map(b => b.toString(16).padStart(2, '0')).join(''); // convert bytes to hex string
+
+        if (content.index.hash === digest) {
+            document.getElementById("verification").innerHTML =
+                "The hash of the content is verified to correspond with the hash" +
+                " in the metadata. You are now reading exactly what was intended.";
+        }
+    }
+}