Tiny markdown parser, makes tutorial screens editing much simpler

media/tutorials/tut-cooccurrence.md

@@ -0,0 +1,11 @@
+___Co-Occurrence___ allows you to find requests that happen often at the same time as the selected domain. Hence it will give you a hint what Apps might be involved in the activity.
+
+How do you interpret these results? Lets look at an example:
+
+<IMG>
+
+The domain __example.org__ had __14__ requests with an _average time divergence_ of __0.71 seconds__. That is, these 14 domain calls happend, on average, less then a second before or after the original request of the selected domain.
+
+Close temporal proximity and high occurrence counts are both indicators for domain correlation. Results are sorted by a ranking index (__9.__) which strikes a balance between the two. Preferring entries with higher counts as well as low time divergence.
+
+_Tip:_ As a visual guide you can look for the colored bar beside each value. The larger the bar, the greater the correlation.

media/tutorials/tut-recording-1.md

@@ -0,0 +1,5 @@
+# What are Recordings?
+
+Similar to the default logging, recordings will intercept every request and log it for later review. App recordings are usually 3 – 5 minutes long and cover a single application. You can utilize recordings for App analysis or to get a ground truth on background traffic.
+
+Optionally, you can help us by providing your app specific recordings. Together with your findings we can create a community driven privacy monitor. The research results will help you and others avoid Apps that unnecessarily share data with third-party providers.

media/tutorials/tut-recording-2.md

@@ -0,0 +1,5 @@
+# Share results
+
+This step is completely __optional__. You can choose to share your results with us. We can compare similar applications and suggest privacy friendly alternatives. Together with other likeminded individuals we can increase the awareness for privacy friendly design.
+
+Thank you very much.

media/tutorials/tut-recording-howto.md

@@ -0,0 +1,16 @@
+# How to record?
+
+There are two types: app specific recordings and general background activity. The former are usually 3 – 5 minutes long, the latter need to be at least an hour long.
+
+## App recording
+
+Before you begin make sure that you quit all running applications and wait a few seconds. Tap on the 'App' recording button and switch to the application you'd like to inspect. Use the App as you would normally. Try to get to all corners and functionality the App provides. When you feel that you have captured enough content, come back to _AppCheck_ and stop the recording.
+
+## Background recording
+
+Will answer one simple question: What communications happen while you aren't using your device. You should solely start a background recording when you know you aren't going to use your device in the near future. For example, before you go to bed.
+As soon as you start using your device, you should stop the recording to avoid distorting the results.
+
+## Afterwards
+
+Upon completion you will find your recording in the section below. You can review your results and remove any user specific information if necessary.

media/tutorials/tut-welcome-1.md

@@ -0,0 +1,5 @@
+# Welcome
+
+AppCheck helps you identify which applications communicate with third parties. It does so by logging network requests. AppCheck learns only the destination addresses, not the actual data that is exchanged.
+
+Your data belongs to you. Therefore, monitoring and analysis take place on your device only. The app does not share any data with us or any other third-party. Unless you choose to.

media/tutorials/tut-welcome-2.md

@@ -0,0 +1,4 @@
+# How it works
+
+AppCheck creates a local VPN tunnel to intercept all network connections. For each connection AppCheck looks into the DNS headers only, namely the domain names. 
+These domain names are logged in the background while the VPN is active. That means, AppCheck does not have to be active in the foreground. You can close the app and come back later to see the results.