Replies (15)

hzrd149 _@hzrd149.com 3 weeks ago

cc. @greenart7c3 and @⚡️ᗪㄖ匚⚡️ Also @⚡️ᗪㄖ匚⚡️ please get a searchable username, its impossible to @ mention you

1 replies ↓

greenart7c3 3 weeks ago

Ill add it later

1 replies ↓

⚡️ᗪㄖ匚⚡️ doc@clave.casa 3 weeks ago

Haven’t changed my display name in like 3 years 😆 Great idea, should be able to add it later today. Can probably just wire it into the current disconnect/unpair path.

1 replies ↓

hzrd149 _@hzrd149.com 3 weeks ago

is there a disconnect/unpair method that you already implement?

1 replies ↓

⚡️ᗪㄖ匚⚡️ doc@clave.casa 3 weeks ago

IIRC it’s an unpair that lets the user clear their bunker or Nostrconnect pairing internally in clave but not that accepts an rpc from a client. Tricky thing with clave is I’ll have to see if the notification service extension can clear a connection without the app being foregrounded since we cant do nip55 in iOS

1 replies ↓

LittleBit _@littlebitstudios.com 3 weeks ago

who reads the nips 🫠

Geek geek@getalby.com 3 weeks ago

implemented into Signet 1.10.1, out tomorrow. whipped up a quick nostr client just to test that it works :-) View quoted note →

⚡️ᗪㄖ匚⚡️ doc@clave.casa 3 weeks ago

@hzrd149 is nostrudel sending the logout request currently?

1 replies ↓

hzrd149 _@hzrd149.com 3 weeks ago

Not yet, I would have to add it to applesauce first (easy) and then Id want to have a signer support it so that I could test it

1 replies ↓

⚡️ᗪㄖ匚⚡️ doc@clave.casa 3 weeks ago

Should have a clave TestFlight build soon. Do you have iOS? If not let me know and I can test

2 replies ↓

npub122x6...xru8 3 weeks ago

I got an iPhone last year actually. TestFlight sounds perfect — what's the main thing you're testing for in this build?

⚡️ᗪㄖ匚⚡️ doc@clave.casa 3 weeks ago

Working 👏

1 replies ↓

⚡️ᗪㄖ匚⚡️ doc@clave.casa 3 weeks ago

And working when clave backgrounded as well

1 replies ↓

hzrd149 _@hzrd149.com 3 weeks ago

Added to applesauce to test. On the client side:

Applesauce Examples

And the provider side:

Applesauce Examples

⚡️ᗪㄖ匚⚡️ doc@clave.casa 2 weeks ago

time to add an optional metadata param to the connect method in bunker (mirroring nostrconnect). this would allow remote signers to get metadata about the client using bunker, the same way we do for nostrconnect. probably not a big deal for android users, but bunker is way more reliable on ios apps that are on the same device as clave @greenart7c3

GitHub

NIP-46: add optional client metadata to connect request by DocNR · Pull Request #2381 · nostr-protocol/nips

nostrconnect:// already lets a client advertise name/url/image in its URI, but the bunker:// flow gives the remote-signer no equivalent — so bunk...

1 replies ↓