Introducing nsec.app and nostr-login!
I've shown the prototype of https://nsec.app in December, and it's essentially an nsecbunker in your browser. It is non-custodial - your keys are stored locally in the browser, and apps can get access to your keys using NIP46. We've now turned that prototype into a real thing, and I invite you to try it. Shoutout to nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q for the designs!
Now how do we help Nostr apps adopt NIP46 for remote key access?
That's where nostr-login library comes in. If your app uses NIP07 to talk to a browser extension, then with just two lines of code you can make it talk over NIP46.
Both of these tools support the new OAuth-like flow proposed by Pablo. Below you can watch a demo of how nostr-login (added to my fork of Snort) works with Nsec.app (or would work with any other nsecbunker).
What this all means is that people could join Nostr on the web, without installing extensions or mobile apps, with their keys stored non-custodially in the Nsec.app, and then could log in to other Nostr apps without copying their private keys.
Demo: https://void.cat/d/JSWwYMTtbWxTDTLpe132Kr.mp4
Links:
Snort+nostr-login: https://snort.nostrapps.org
nsec app: https://github.com/nostrband/noauth
nsec app server: https://github.com/nostrband/noauthd
nostr-login: https://github.com/nostrband/nostr-login
これ試してみた。素晴らしいこれにしよう。
#m=image%2Fjpeg&dim=864x1920&blurhash=%5B184unxv9FWGsit7t8WC_0W9-%3AW900W9xtW98%5Et7D%25Rk%25Mt9xcWG00og-%3Ba%24%25MR%24-%3Aaw_1RhD%24W9&x=3d2e72462776d73311ce79f9b10a3ac563e9a356865133010d48743ffad95c6e
#m=image%2Fjpeg&dim=864x1920&blurhash=%5BTKd%7DLRks%3Bay00WURjj%5B%25Mt7ofay%7EqRjWBWB00t7t6ofIUWBayfQIUj%5Dj%5BWBIUt7ofj%5B00WBayfQ&x=97caa05b00ba7a8e649179892a49e2531cec27f4ec934f26428f1839eca8c909
文句をつけるところを探すならNostrで実現されてる何にもしてないのにアカウント作成が完了している感じは無くなるかも？
Translations are coming soon to nostr-login.
Translation is necessary,
but assuming that new users will be using it, I thought it would be smooth to have a function that redirects them to the client app after they open nsec[.]app from the client app and create an account.
Users see nsec.app in a popup, after it's all done (login/signup) the popup closes and user is back at your client app. At least that's how it should work unless there are bugs.
