I think your biggest confusion was when i showed how you could connect the bridge to an existing account that you hadn't yet logged into yet in that session (ie facebook linked to account created with twitter). I could hide that option but the aim was to prevent people from accidentally creating 2 different yumps account, one for each login. Perhaps it can be refined. Perhaps the text on that link should say something like "WAIT! If you already have an account on YUMPS, don't click submit to create a new account, but click here to login with your other account and connect this bridge to that account."
-mouser
Yep, that's what I mean. Notice that I did understand the whole process, but I'm pretty sure that a naive user would never be able to finish it. I agree, the problem may only be in the text of that option

I should note that it is quite easy and less confusing to add a new bridged account AFTER you are logged in (from the Manage Bridges) page.
-mouser
Yep, I imagined so, that's why it seemed a bit overkill to have that "bridge this account with existing account" option, I'm not sure if that would happen much. Also, related to this, if someone did create another yumps account, is there a way to "merge" it (or bridge it?) with another existing one?
As you can see, the issues you are raising are EXACTLY the kinds of issues that YUMPS is meant to handle well. While user sccount creation and management is a small side detail for most web services -- it is one of the central focuses for YUMPS -- so I intend to make it better and more robust than anything else out there.
-mouser
Awesome

That really does look good!