Telemetry Article (#44)

* Write boilerplate telemetry

* Write skeleton

* Write first paragraph telemetry

* Write second paragraph

* Tweak bullet list

* Write third paragraph

* Quickfix: add to bullet list

* Summarize bullets

* Same as ~1

* Phrasing! Boom!

* Hey! Phrasing!

* Um, phrasing?

* Add step-by-step opt-out

* Write closing paragraph

* Quickfix: link

* Apply feedback from j-selby and Schplee

* Hard wrap article to 80 cols
(Wow, I'm surprised hugo didn't shit itself handling the newlines.)

* Add screenshots

* Apply fixes from @B3n30 and @bunnei

* Added image alt-text optimized for screen readers

* Replace MSFT link with text

* Change screenshot platform to Windows 10

* Add banner by @bunnei

* Add telemetry ID paragraph

* Add forum post ID

site/content/entry/telemetry-and-why-thats-a-good-thing.md

@@ -0,0 +1,66 @@
++++
+date = "2017-08-26T21:04:00-04:00"
+title = "Telemetry (And Why That's A Good Thing)"
+tags = [ "citra-release" ]
+author = "anodium"
+forum = 3095
++++
+
+Citra has some [issues](https://github.com/citra-emu/citra/issues), and by its
+nature as an open source project, they are visible to everyone and fixable by
+anyone. Unfortunately though, most contributions are made by
+[a small minority of developers](https://github.com/citra-emu/citra/graphs/contributors).
+These developers have found it difficult to prioritize their efforts, since the
+majority of issue reports are written scattered across Discord, Reddit, forums,
+IRC, and too many other places to count.
+
+Because of this, the Citra team has put together a framework to report data about
+how Citra is used to our server, and use that data to discover what are the most
+popular games and hardware configurations, where emulated games crash in Citra
+most often, and more. We had considered including this in last month's progress
+report, but we decided that it would be best to publish this on its own, so it
+gets the attention it deserves. We're very aware that privacy is important to
+many of our users, and so from the earliest planning stage we knew we must be as
+transparent and open about this as possible.
+
+The telemetry framework will collect information such as:
+
+ * Information about the version of Citra you are using
+ * Performance data for the games you play
+ * Your Citra configuration settings
+ * Information about your computer hardware (e.g. GPU, CPU, and OS type)
+ * Emulation errors and crash information
+
+Not everyone is comfortable sharing information about their system, so we've made it easy to opt-out:
+
+<p style="text-align: center; padding: 1%;">
+<img style="padding: 0% 0% 1% 0%;" height="75%" width="75%" alt="Alt, E, C" src="/images/entry/telemetry-and-why-thats-a-good-thing/optout1.png" />
+<br />
+First, head to the Citra "Emulation" → "Configure..." menu.
+</p>
+
+<p style="text-align: center; padding: 1%;">
+<img style="padding: 0% 0% 1% 0%;" height="75%" width="75%" alt="Right arrow, Right arrow, Right arrow, Right arrow, Right arrow, Right arrow, Right arrow" src="/images/entry/telemetry-and-why-thats-a-good-thing/optout2.png" />
+<br />
+Then, head into the "Web" tab.
+</p>
+
+<p style="text-align: center; padding: 1%;">
+<img style="padding: 0% 0% 1% 0%;" height="75%" width="75%" alt="Tab, Tab, Tab, Tab, Tab, Space" src="/images/entry/telemetry-and-why-thats-a-good-thing/optout3.png" />
+<br />
+And finally, untick the box titled "Share anonymous usage data with the Citra team".
+</p>
+
+You may have also noticed the field titled "Telemetry ID" in the screenshots, this
+is an identifier generated randomly on install which is used instead of your IP
+address. This makes data collection entirely anonymous, unless you choose to log in.
+You can also reset your telemetry ID if you'd like by clicking "Regenerate". The
+new ID will also be completely random, and so it would be treated as a wholly new
+identity.
+
+Telemetry is an extremely useful developer tool, as they allow the developer to
+be more aware of the users' needs and priorities accurately, rather than guessing.
+But it is only as useful as the data obtained, which is why we urge users to not
+opt-out, so the data can be as accurate and correct as possible. Just as innacurate
+measurements can damage a device during calibration, innacurate statistical data
+will only cause damage to Citra.