Yo, nos2x redesign by @HoloKat is fully working now, I will do some polish then we can merge it into main, I not sure about the Nostr Connect name or we still use nos2x name
Login to reply
Replies (36)
I looks much, much better. Great work.
Karnage is a beast...a cat beast? 🤔
[817735]
Looking like a million bucks, I owe you another 5k sats once’s it’s merged 🤩
Looks neat 👏
What did you use to record this, fellow Arc user?
I promised to chip in. Time to see if NWC can handle 100K sats.
Don’t merge it into main. @fiatjaf doesn’t want that
Launch as a separate extension probably
Nice design!
Is it? one is typescript SDK, another is chrome extension. I don't see any issues.
Ty ser
Nip-46 is literally Nostr Connect 🐶🐾🫡
Not merging I don’t think. Separate extension.
Is it a chrome extension? If not I don’t see an issue.
Up to you, but I would avoid it, since we have logins that use nip-46 and the buttons marked as Nostr Connect. Confuses the user, not a great experience 🐶🐾🫡
Looks absolutely terrific! And I love the new name. It’s much clearer.
Understood.
Please add a feature for multiple keys.
Hey man , what css framework do you use ?
Me? None. I haven’t done any front end dev in a while
Oh , okay. Thanks.
Nostr Connect is a better name in my opinion. Will be more discoverable and easily understood by end users.
Nicely done @HoloKat
🙇♂️
Love it, what recording tool is that? it looks awesome
Nostr Connect is a bad name. I would create something with key-safety-signer. What about 1Signer? Or NostrPass?
NostrPass 👀
NostrPass sounds good. Or NostrAuth, NostrSigner. Something like that
Where did the Authorize <kind> for <x> go? I need that
Is this a NIP-07 extension that has the same name of NIP-46? 😅
Does nos2x have support for encrypting private keys at rest?
I agree.
It is better to look for a new name, perhaps crediting the original work.
nos2x-classy ? :D