Man... I think we've gotten used to Alby being there in the past , going through it now from the perspective of a new user that wants to create a nostr keypair using a nostr signing tool/manager (browser extension in this case), its, at least currently, a bad experience.

Password? Sure.

Register for an Alby account or use one of your Lighting hookups? wtf? As a new-user-pov, I'd go like "ok, let's create an alby account", then oh wait, no u can't, you have to get an invite code from x or y or z. WTF? all of this just to try and make a nostr account? I've been blinded and won't recommend, at least for now, Alby anymore to new users, unless the process becomes: install > password (skippable) > insert nsec or generate new pair > done / optional process of Alby LN service.

I had it as the first button for the 'registration' process on my project but yanked it out now.

Looking for alternatives and testing them, the best ones seem to be development-dead (Keys.Band, which as far as I'm concerned just needs an nsec extraction function/ui, and Flamingo, which is a bit slow).

The good options after that are the OG nos2x and Nostr Connect (a pretty version of it basically with a bit more nice additions like hex and nprofile key extraction).

I hope someone just forks keys.band and adds nsec extraction, and Flamingo's faster setup, plus Alby's opening of a browser tab to direct the user to setup (saves 2-4 clicks). Would also be nice to have finer permission control. That would be it.