There are still some rough edges to FB account setup/migration: You can cancel/save the account before you finish allowing Adium access. The location of the start of the migration process is probably not ideal: Not all accounts will be auto-migrated (stats indicate that there are at least 9k users with more than one account). Only accounts that are set to login automatically or the user manually logs in or edits will start the process. Sending another AIEditAccount notification when the old FB account starts to be edited will generate a beep. Also, if there are multiple FB accounts set to auto-login there will be a beep or two. When the webview finishes, the edit account view should be updated to reflect success/failure. The old account probably shouldn't be listed as an available new account. I couldn't get my accounts to go to away/idle, docs say "Setting the user idle using a show element in presence stanzas".
Since this Facebook implementation will be more reliable than the previous and it is in the top 4 used protocols according to sparkle stats (http://sparkle.adium.im/?year=2011&week=10&graph=bar#IMServices) we could increase its priority (move it to the top half of the new account selector). There was some support for this decision in #adium-devl, but if we're going by usage then GTalk should move up and Jabber down. -- Frank
