From 9adbcaf262d75bb938e03e8f6f3566d55f7a732f Mon Sep 17 00:00:00 2001
From: csagan5 <32685696+csagan5@users.noreply.github.com>
Date: Mon, 19 Mar 2018 00:45:49 +0100
Subject: [PATCH] Add F.A.Q. about HTTPS everywhere

---
 README.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/README.md b/README.md
index d12a1a8a..a88b0b3d 100644
--- a/README.md
+++ b/README.md
@@ -30,6 +30,10 @@ ETH donations address: `0xf47ff39223d828f99fec5ab53bd068c5c0522042`
 No.
 This is not a limitation of Bromite but of all Chromium-based projects in general, as general public is not allowed to use Google's APIs for free unless when using Chrome.
 
+## Can you add HTTPS everywhere?
+No.
+We cannot add add-ons to Bromite (merely some features) and anyway HTTPS everywhere in particular is too invasive to be easily maintained across new releases.
+
 # Features
 
 * adblocking (currently baked-in, no configuration options available)