DUDE seriously how the fuck is this not more available? nostr:nprofile1qqsfnz2sqsflkatdssmeztxr90s8xrd7r07xkhfwaa6eu9zkcguljpgkcnjz6 50k sats if you add this method (I like the DM but this is even easier).

I’ll have another 50K to a few others who implement this. And seriously if anyone else wants to see this, devote some sats to the services that add it 👏🏻👏🏻

We can literally crowdsource any fucking feature we want, just post and zap. ⚡️ nostr:nprofile1qqs03ekxgdp0rczjfqrrpcn7zqtdec6lcwnpfesyxnl0f239qvege2ggyhgpr

What service do you wish you could log into this way 👇🏻👇🏻👇🏻

nostr:nevent1qqszn6cexdq8ng9qvmct755t9ccgjldyfevhzaejdddr3fzfvrr8negppamhxue69uhkztnwdaejumr0dsv8mth6

Reply to this note

Please Login to reply.

Discussion

Like everything tbh. We need to make things dead simple

Why this over just making every client a NIP-46 signer that can not only log you into other services, but also sign events?

This option seems like it would work for log in, but not for anything that actually requires signing of events.

Consider how most users onboard to Nostr. They download a client they heard about like Primal, Amethyst, or Damus, and they generate their keys in that client. So that first client is going to have their private key unless they have a friend who helped them get set up through a dedicated signer app like Amber. If that's the case, then those "flagship" clients ought to be able to serve as remote signers, similar to how Gossip on desktop can be a remote signer, allowing users to log in and to sign events from the client where they generated their keys.

NIP-97 seems to just allow the first part, which is unnecessarily limiting when we already have NIP-46. We would just need a more smooth way for a website to request a connection string from the remote signer app/Nostr client.

I don’t know the specifics of how this works and didn’t investigate yet. It seemed to me just diving with your Nostr client. If there’s a way to do this with more versatility then for sure do that one.

nailed it. this does OnE signature, on an event that just says you are you. after that, then what? 😂 poor iphoners.. technology really is beyond them ..

Well, the trouble with anything on mobile is the OS killing the app when it is in the background. We can get around that with persistent notifications on Android, but maybe that's not an option on iOS?

I'm perfectly aware this is just a sign in, which is why i tagged nostr.build, its just an account and you dont sign uploads

Yeah, for things like nostr.build, something that ONLY does log-in is fine, since signing isn't needed for anything else within their service. However, NIP-46 signing can handle just logging in if that is all you need, as well.

My point is, why use proposed NIP-97 that never went anywhere and can only be used to log in, without doing anything else, when we have NIP-46 that CAN be used for just logging in, if that is all you need, but can also be used for further signing?

If the answer is that iOS won't be able to do NIP-46 signing, then that might make some sense.

Also, nostr.build already has "login with nostr," but it uses NIP-07 browser extension signing to do this. Very smooth on desktop, but I don't think we have any iOS browser extensions, either... iOS just doesn't get to have nice things.

FYI - We do have a ‘Share Direct to Nostr’ feature that requires signing.