1.17.0

This update addresses some important privacy issues with the Bugsnag implementation. Before this release, it was possible for the current authentication token and WiFi password to be included in error reports (see #139 for details). This update hardens data sanitization to hopefully exclude any sort of credentials.

The scope of any actual data leaks should be minimal. I'm the only one with access to the Bugsnag data, and I don't sell it or give it away to any third parties. The error reports are also not guaranteed to trigger (only on certain failures), so most users should be unaffected. Finally, even if data was sent, the only way for it to be used is to have access to your internal network. Since externally identifiable information like your public IP is never collected, obtaining that access is impossible.

To be extra safe, I'm deleting all existing errors from Bugsnag:

Thank you to @sand7000 for catching this. Please update ASAP.