#asknostr
Okay, I am trying to enter flotilla, I copied my bunker link from NSEC App and when I paste it , I just get this loading screen on flotilla.
Any other places to get a bunker link?
I am using iOS.
Login to reply
Replies (8)
Dont use Apple please
nostr:npub1dzrlhj48aycgfkny2mn7e6qkgme7w5xa53u75c30atkflrck6fuq7cdjyj Use Nostore for now to sign in with the Safari extension.
To be clear, my priority is building a native signer similar to NIP-55 and also support NIP-07 as an extension. I don’t think a remote signer is the best solution for iOS in this case.
I agree with you. However, iOS has technical limitations that prevent background apps from running. In order to be an effective remote signer, you would have to open your iOS signer app to the foreground each time you want to sign a request. There might be a possibility of using a centralized push server to wake up the signer on iOS and show a notification to the user when a signing request comes in. But it seems much more limited than what Android is capable of doing.
Apple’s Secure Enclave supports only P-256, not secp256k1. It’s not compatible. I’m no cryptographer, but I believe the only solution is to have a separate dedicated Nostr signing app that you bring to the foreground when you need to sign an event.
https://developer.apple.com/documentation/cryptokit/secureenclave
I think it may be possible to do something like what NIP-55 describes with nostrsigner:// deep link URLs which would in theory allow us to switch between native Nostr iOS app / Nostr web app to signer app, and then back to the Nostr client using callbacks. It might be janky and disorienting with all the app switches, but that’s the most seamless experience I can see.
The alternative is the approach I’m taking now in my design, which is using action extensions to bring up a sheet to sign an event without needing to switch apps, but this requires one too many taps from being ideal.
Yeah, agreed. Which is why the former solution with app switching might end up being the best we can pull off.
True. I’m exploring alternatives that may allow background processing on iOS, though I haven’t tried it yet. It’s new territory for me so I don’t have much to report back yet. Hopefully we can make it work!
I was able to get it. Turns out it was user error the whole time 🤦♂️