From 008cdd48c1086aa6c0ed8951cfca21cfed3b1b0c Mon Sep 17 00:00:00 2001
From: Dominic Ricottone <me@dominic-ricottone.com>
Date: Tue, 10 Aug 2021 09:24:06 -0400
Subject: [PATCH] Washing my hands of content security policy

Why do I even need to do this for a local application? This isn't a
website. Content security policy is pointless anyway.

Node packages depend on all sorts of styling and evaluation. It isn't
possible to set a content security policy without many many exceptions.
At minimum, Monca seems to need unsafe-inline styling and unsafe-eval
scripting.
---
 index.html | 1 -
 1 file changed, 1 deletion(-)
diff --git a/index.html b/index.html
index 2a2319f..5f6f845 100644
--- a/index.html
+++ b/index.html
@@ -7,7 +7,6 @@
     <meta name="description" content="" />
     <link rel="stylesheet" href="node_modules/github-markdown-css/github-markdown.css" />
     <link rel="stylesheet" href="style.css" />
-    <meta http-equiv="Content-Security-Policy" content="default-src 'self'; style-src 'unsafe-inline' file:" />
   </head>
   <body>
     <div class="sidebar">
-- 
2.45.2

