I've been wondering why many Nostr web apps that support NIP-46 "Bunker Login" only seem to support the case where the bunker initiates the connection. When a user isn't logged in, there's no easy way to transfer the token created by the bunker (unless you use an external messenger or email, which is a clunky solution).
It seems much more convenient for the client to create the token, display it as a QR code, and have the signer(nostr:npub1am3ermkr250dywukzqnaug64cred3x5jht6f3kdhfp3h0rgtjlpqecxrv7) scan it.
I recently learned while working on Jumble's code that the reason for this was a lack of support in nostr-tools for the client-initiated token creation method. Now that nostr-tools supports this feature, supporting the login flow to allow the client to create and send the token to the bunker would make the entire process much smoother.