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.
Cool. What do you think about merging with the NIP-55 Android signer spec? It feels weird that the URI scheme is “aegis://“. Why not use the same “nostrsigner://“ scheme and converge with what Android does?
https://github.com/nostr-protocol/nips/blob/master/55.md#methods-2
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.
I don’t like the format of how NIP-55 does the nostrsigner: URIs to be honest. Would be great if it were more “RESTful” instead of starting immediately with the content. Maybe start with the name of the method first followed by the ? and query parameters. But that’s just my opinion.
cc nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5
Yes, that would be better
I had to do a lot of magic to get the content and the parameter right in the way I did it
Having the method first would simplify things a lot
