Authentication flow without local server

The use of a local server listening on a fixed port for capturing the return of the OAuth flow is making it next to impossible to integrate properly into enterprise software: it is incompatible with Terminal Services/Citrix, interferes, might fail randomly due to firewall policies and might even cause a security issue (if two users go through the flow at the same time, the first user might receive the other user's token).

Since that functionality is mostly unnecessary when using an integrated web browser, I would suggest it being rewritten and the user of a local server dismissed.