Added FAQs

For #106

.documentation/addon description/de/description.txt

@@ -1,5 +1,7 @@
 Dieses Add-on ermöglicht es Nutzern, Webseiten davon abzuhalten, sie über Javascript APIs zu identifizieren. Nutzer können auswählen, ob die APIs komplett auf bestimmten oder allen Seiten blockiert werden (dies wird die Funktionalität einiger Seiten beeinträchtigen) oder bei den identifikationsfreundlichen Auslese-Funktionen falsche Werte vorzutäuschen.
 
+Bei Problemen konsultieren Sie bitte zuerst <a href="https://canvasblocker.kkapsner.de/faq/">FAQ</a>. Falls Sie Fehler finden oder Verbesserungsvorschläge haben, teilen Sie mir das bitte auf https://github.com/kkapsner/CanvasBlocker/issues mit.
+
 <b>WICHTIG</b>: Sie sollten nur ein Addon/eine Einstellung aktiv haben, die eine API beschützt. Ansonsten können Sie massive Performanceprobleme bekommen. (Z.B. EclipsedMoon für Palemoon hat 'canvas.poison', was bekanntermaßen Probleme verursacht: https://github.com/kkapsner/CanvasBlocker/issues/253#issuecomment-459499290)
 privacy.resistFingerprinting kann aber problemlos aktiviert werden und der Fingerprinting-Schutz muss nicht deaktiviert werden.
 
@@ -39,6 +41,4 @@ Die verschiedenen Blockiermodi sind:
 		<li>nur Einträge der Whitelist erlauben: Nur Seiten, die in der Whitelist gelistet sind, dürfen die beschützten APIs verwenden.</li>
 		<li>nur Einträge der Blacklist blockieren: Blockiere die beschützten APIs nur auf den Seiten der Blacklist.</li>
 		<li>alles erlauben: Ignoriere alle Listen und erlaube die beschützten APIs auf allen Webseiten.</li>
-	</ul>
-
-Falls Sie Fehler finden oder Verbesserungsvorschläge haben, teilen Sie mir das bitte auf https://github.com/kkapsner/CanvasBlocker/issues mit.
+	</ul>

.documentation/addon description/en/description.txt

@@ -1,5 +1,7 @@
 This add-on allows users to prevent websites from using some Javascript APIs to fingerprint them. Users can choose to block the APIs entirely on some or all websites (which may break some websites) or fake its fingerprinting-friendly readout API.
 
+If you encounter any problems please check the <a href="https://canvasblocker.kkapsner.de/faq/">FAQ</a> first. Please report issues and feature requests at https://github.com/kkapsner/CanvasBlocker/issues
+
 <b>IMPORTANT</b>: you should only have ONE addon/setting set that protects an API. Otherwise you could face massive performance issues. (E.g. EclipsedMoon for Palemoon has 'canvas.poison' which is known to cause issues: https://github.com/kkapsner/CanvasBlocker/issues/253#issuecomment-459499290)
 But setting privacy.resistFingerprinting to true and/or using the new fingerprinting protection introduced with Firefox 67 is fine.
 
@@ -41,5 +43,3 @@ The different block modes are:
 		<li> block only black list: Block the protected APIs only for websites on the black list.</li>
 		<li> allow everything: Ignore all lists and allow the protected APIs on all websites.</li>
 	</ul>
-
-Please report issues and feature requests at https://github.com/kkapsner/CanvasBlocker/issues

.documentation/faq/funding.md

@@ -0,0 +1,9 @@
+How is CanvasBlocker funded?
+-------
+There is no steady monetary funding of CanvasBlocker. Donations are accepted and help to cover some expenses. But since these are not that high it is not sure if a steady funding with any obligations will be accepted.
+
+There is also no plan to monetize CanvasBlocker in any way.
+
+All the development work is done by kkapsner in their spare time and no salary or compensation is paid for it.
+
+So it's all done voluntarily for fun and free.

.documentation/faq/howToSupport.md

@@ -0,0 +1,5 @@
+How can I support CanvasBlocker?
+------
+The best way to support CanvasBlocker is to give feedback. If something is not working like it should or something could be improved please open an [issue](https://github.com/kkapsner/CanvasBlocker/issues/new). Reviews at [addons.mozilla.org](https://addons.mozilla.org/firefox/addon/canvasblocker/reviews/) can also help to increase the user base but it is a very bad platform to communicate issues and improvements.
+
+If you want to contribute with your own spare time you can help to improve the [translations](https://github.com/kkapsner/CanvasBlocker/issues/420). Code contributions can also be done in form of pull requests but will be reviewed very thoroughly.

.documentation/faq/index.php

@@ -0,0 +1,21 @@
+<!DOCTYPE html>
+<html>
+	<head>
+		<title>
+			CanvasBlocker FAQs
+		</title>
+	</head>
+	<body>
+		<header><h1>CanvasBlocker FAQs</h1></header>
+		<?php
+		include_once("../../kamiKatze/autoload.php");
+		$parser = new MarkdownParser();
+		foreach (new DirectoryIterator("./") as $file){
+			if (!$file->isDot() && !$file->isDir() && $file->getExtension() === "md"){
+				$markdown = $parser->parse(file_get_contents($file->getPathname()));
+				echo $markdown->view("html");
+			}
+		}
+		?>
+	</body>
+</html>

.documentation/faq/permissions.md

@@ -0,0 +1,10 @@
+Why does CanvasBlocker need permission X?
+------
+Here is the list of permission that CanvasBlocker needs and the reason why it's needed:
+
+ * <all_urls> and tabs: CanvasBlocker needs to be able to interact with all possible urls and tabs as fingerprinting attempts could be done everywhere.
+ * storage: to store the settings the storage.local API is used.
+ * activeTab: not needed - will be removed in the next release
+ * webRequest and webRequestBlocking: to insert the CSR headers in a request in order to protect the data-URLs. Once [this bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1475831) has been fixed I can completely remove the data-URI protection (see [here](https://github.com/kkapsner/CanvasBlocker/issues/208) for further information).
+ * contextualIdentities and cookies: for support of browser containers. I would like to make this optional for only people that use containers but I cannot (see [here](https://github.com/kkapsner/CanvasBlocker/issues/381) for further information).
+ * privacy: this permission is needed to read if the user has privacy.resistFingerprinting enabled. A notice about a slightly changed behaviour of CanvasBlocker is displayed in the settings page in that case.

.documentation/faq/uniqueFingerprint.md

@@ -0,0 +1,10 @@
+Page X claims my fingerprint is unique.
+------
+Having a unique fingerprint is fine as long as it changes. With the default settings of CanvasBlocker the fingerprint should change all the time. But also with other settings (e.g. the stealth preset) that do not change the fingerprint all the time the fingerprint should be unique per domain and therefore prevent tracking. To test this you can check the different fingerprints on [canvasblocker.kkapsner.de](https://canvasblocker.kkapsner.de/test/) and [canvasblocker2.kkapsner.de](https://canvasblocker2.kkapsner.de/test/).
+
+My fingerprint does not change when I reload page X.
+------
+Some pages do not recalculate the fingerprint upon reload. Make sure you force the recomputation.
+But also some CanvasBlocker settings make it to not change the fingerprint upon reload (e.g. the stealth preset).
+
+If you have privacy.resistFingerprinting enabled the fingerprints also may stay the same. But in this case you are not trackable as the fingerprint does not leak any information about your system. See [here](https://github.com/kkapsner/CanvasBlocker/issues/158) and [here](https://github.com/ghacksuserjs/ghacks-user.js/issues/767) for further information.