Why aren't mobile clients interested in becoming NIP-46 signers? nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1n0stur7q092gyverzc2wfc00e8egkrdnnqq3alhv7p072u89m5es5mk6h0 nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1gp4xzpmluelsakjtayc4wtzj97fhj5kakqjvsannu00xkdlf4x8s0xdqyq nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr

Reply to this note

Please Login to reply.

Discussion

I was just thinking it would be nice if damus could sign external events. it already registers with ios to handle “nostr:” scheme URLs. could this same mechanism be used to sign events from eg the web?

there’s not really a way to pass the information back. I think damus nsecbunker via push notifications would be better

🫡

I suppose you could sign & publish to the user’s relays.

I want my Umbrel to be my signer.

Who says we’re not interested?

Latency and data use of decrypt/encrypt is the main thing for me. Otherwise, it's fine.

But for Amethyst to sign stuff from a web microapp that shouldn't be a concern.