xAuth keys have special privileges and twitter said they would not give them to us. The current implementation is the simplest for users. If we opened a browser window, we rely on the user needing to copy and paste from the browser into gwibber. I don't really see a problem with embedding a browser into the accounts dialog, it is just a browser and a user can either allow or deny gwibber access. If they don't allow it, then nothing is passed back to gwibber.
xAuth keys have special privileges and twitter said they would not give them to us. The current implementation is the simplest for users. If we opened a browser window, we rely on the user needing to copy and paste from the browser into gwibber. I don't really see a problem with embedding a browser into the accounts dialog, it is just a browser and a user can either allow or deny gwibber access. If they don't allow it, then nothing is passed back to gwibber.