Hi! I agree that the flow you've described is super unfriendly. The 'Discover apps' link on nsec.app leads to a general nostr app catalog - those are all apps out there, not ones that support nip46 (the remote access protocol that nsec.app implements). Eventually we will have a much better supported-app-discovery flow, for now you can go to nsec.app homepage and check the list of supported apps at the bottom of it. And yes, you have to open the app and figure out how to login with nsec.app there - each app does it a little differently, again our homepage has short video guides for every supported app. Does that help?
I had to clear site data to get it working, was only showing Loading...
Is the frontend open-source? Wanted to submit a PR to nip46 part but couldn't find it
If people only used auth_url popups to confirm then your bot wouldn't do harm. Doing confirms through popups has other useful features. I wonder if I should implement the 'secret' thing and only show connection requests with a secret in the nsec.app itself.
Yeah requiring secret seems like a good path forward for non-oauth-like flows.
I will send some PRs to clients to add support for it.
That bot will inevitably be made bcs it's quite trivial, so thank you for raising the issue sooner.
500k zap will go here
nostr:nevent1qqs8l5mm3scg65uvh0uh8jmp6a0sksmv86kuy774vau5qx7086s76lspp4mhxue69uhkummn9ekx7mqzyqduwzspfzelx9k6x0lrez0j8cl8rtz0lxvqylk8z2ustnfy76jpzqcyqqqqqqg0qt5ql
Yeah that the full nip46 implementation - app makes a call to signer, signer sends back auth_url message if confirmation is needed, app should show a popup with that url, when user confirms signer replies to the request and the app receives the reply to the method they called. For apps that don't implement auth_url you can manually go back to the signer to confirm. It's all in the nip46.
@hzrd149 nostrudel trying to sign DM with 'null' in tags: {\"kind\":4,\"content\":\"vckekw0ADZhsRYcA/5Iv90sZw7rcvBySa2u6NG7FwbontwKcLKOrYGB5uTLPLqkMKImQqDiDHCLOl6E3YltJj3h5CTPmGC3y2e/pXhZgmID5Pdl4omf/hbcHaCuYG5N15NXLO7Wtg3yrQsefg5Xd9bMT5ZA6FwGzkvGLhCjKTn8Iz2IAwpqb2p6zbSCB166WGtEIM5rBVPTFfSTQMDtvxg==?iv=bxUEv6Zu4kVK7sNfAoaKWA==\",\"tags\":[[\"p\",\"5144fe88ff4253c6408ee89ce7fae6f501d84599bc5bd14014d08e489587d5af\",null]],\"created_at\":1710307709,\"pubkey\":\"3356de61b39647931ce8b2140b2bab837e0810c0ef515bbe92de0248040b8bdd\"}"]
Nsec.app stores keys in your device, it's running inside browser service worker which is weken up by a push message if server detects that sw is sleeping and not replying
How to login on npub.cash with nsec.app:
(I'm recording a series of short guides on apps supporting nip46, links on nsec.app homepage)
https://v.nostr.build/oMWZx.mp4
It involves generation of session keys by the app, and use of those temporary keys to talk to the signer (nsec.app) over some relay.
Bunker url is just a pointer to your npub and a relay over which app can talk to signer. But bunker url can also contain secret that has pre-approved permissions attached to it by the signer. Nsec.app doesn't support that atm.
There is a list of apps at the bottom of nsec.app homepage. Several bigger ones are in the pipeline with bug fixes. Shipyard only works with nsecbunker, it's not yet fully implementing the nip46.
Password manager can only store your nsec safely. Nsec.app can give permissioned access to other apps to your keys, and you can put nsec.app's password to your password manager to make life simpler.
Try typing your name@nsec.app to Snort login screen, might work. Several issue fixes were submitted to Snort last week, hopefully will work better when released.
You can have multiple accounts in Alby and can switch btw them, but you'll have to also switch in each nostr-app - most of them have their own 'logged in user' state, so just switching in alby won't be enough. My solution is to have several accounts in nsec.app and use different nostr apps with different accounts.
Bunker urls currently generated by nsec.app aren't sensitive. But there are different kinds of bunker urls, some of which are sensitive, so I'd say you shouldn't get used to treating them lightly.
I would encourage you to use your name@nsec.app to login where possible. If we ever start generating bunker urls that must be kept secret we will have big warning all over the place.
We currently export keys in ncryptsec format, not many apps support it yet (Amethyst does). Importing ncryptsec is on the roadmap.
Could you please try again on next.nostrudel.ninja? It is a coming-soon version of nostrudel where several bugs have been fixed, try the 'Nostr Address' option to login with your name@nsec.app
I agree in theory, in practice no native app devs have shown enthusiasm. Native apps are proud of their low latency, nip46 can never get that performant and predictable. Batching solves dm decryption, and signer-relay saves one round trip, but one rt stays no matter what. Unless it's some nip46-over-ipc on the same device.
No, popups are blocked by browsers in various circumstances, we try to avoid that where possible but maybe we're missing something. Will look into that, thank you!
Notes by brugeman | export