{ "id": "07541591fb9caf0de62bb8baaaf23361f9e3d0a9039404693c218ae7bf2a466c", "pubkey": "a008def15796fba9a0d6fab04e8fd57089285d9fd505da5a83fe8aad57a3564d", "created_at": 1727272124, "kind": 1621, "tags": [ [ "subject", "feat: Nip46Signer::new_on_demand" ], [ "alt", "git repository issue: feat: Nip46Signer::new_on_demand" ], [ "r", "73f7c34fd424cae57a0da1be1f5fd31d9b8075c0" ], [ "a", "30617:68d81165918100b7da43fc28f7d1fc12554466e1115886b9e7bb326f65ec4272:rust-nostr", "wss://relay.damus.io", "root" ], [ "p", "68d81165918100b7da43fc28f7d1fc12554466e1115886b9e7bb326f65ec4272" ] ], "content": "I have a CLI (ngit) that is usually used to read but sometimes used to write events.\nI'm trying add support for relays that require AUTH to read.\nIf nip46 a bunker url is known and have previously been used to successfully sign event, I would like to opportunistically use it to respond to AUTH events.\n\nI don't want to await the return of Nip46Signer:new() before sending read requests and I'd like a shorter timeout (or the connection attempts to be stopped when the client falls out of scope) \n so that my CLI can close when other operations are complete.\n\nLater, if the CLI needs to sign user generated events, it will attempt to connect to the remote signer again (if not already connected) and this time would need a longer timeout for connecting to the remote helper as provided through Nip46Signer:new() .", "sig": "8850999dce7fa9ae9b6deaac9f49ca0963804869b6b00b77926a5c02253f6d9f51af2542a47117a4ae85c6e2076f47224caa9e91fdfd4af3832c309ecf6d4e10" }