Use the user's default browser, not an in-app web flow, for authentication

[paced]

Please explain the problem/why you would want to see a change and any workarounds you might have in place.

Derived from this issue on the original repo. It reads:

I think it's a little bit sketchy to let a 3rd party application like this authenticate FB credentials within its own web-view. I know you guys aren't doing anything with nefarious, but it is a concern UX wise.

Also it's pretty annoying to have to fetch my credentials on FB / remember my password. Would be great if the app could open up the browser with the OAuth link and then poll the response.

[paced]

This is a really important feature. That being said, the upgrade to the latest Electron version is more important for usability as it immediately identified and fixed some problems people had with the previous app.

As a result, we are moving it to v0.10.0.

[paced]

This is going well. However, the app now needs to run an Express server to listen for the auth key. Probably no big deal, but it's worth mentioning publicly.

[paced]

v0.10.0 implements this.