Nostur, Olas, 0xChat, and Flotilla

wen damus?

I see, that makes sense — thanks for the clarification! Which app did you use Aegis for signing with? I’ve tested it with Nostur, Olas, 0xChat, and Flotilla — all of them work.

That’s a very creative approach — I hadn’t thought of doing it this way. However, the user experience seems a bit complex, with switching keyboards, triggering the signature, and then switching back — if I understood correctly. Have you tried using Aegis? This is how I implemented background execution on iOS: 1. Start Aegis, which launches a lightweight local relay service (only handling signature-related tasks) and sets it as the NIP-46 signature relay. 2. Move the app to the background and loop a silent audio track to keep it running in the background With this setup, other nostr apps can continuously use the local relay for signing operations. The user experience is quite similar to using Amber, except that the app must not be killed.

Interesting idea. What do you see as the advantage of doing this through a keyboard?

Aegis for Nostr v0.1.8 Released 1. Added support for nostrsigner:// while retaining aegis:// compatibility 2. Standardized the auth path to /auth/nip46 3. Added a method= query parameter 👉 Try it now: https://testflight.apple.com/join/DUzVMDMK

I was thinking that if used a generic nostrsigner scheme, it could cause confusion if multiple signers that support this scheme are installed on the device. Usually though, your key wouldn’t exist on more than one signer. But I’ll look into it and see how to make it compatible with NIP-55.

Hi, introducing AegisConnectKit — a SwiftUI component library for quickly integrating Aegis signer URL scheme method. It supports both Button Components and Direct Method Calls, making it easy for Swift-based Nostr projects to connect and interact with Aegis seamlessly. https://github.com/ZharlieW/AegisConnectKit