<oembed><type>rich</type><version>1.0</version><title>Innis wrote</title><author_name>Innis (npub1l3…5cxyz)</author_name><author_url>https://yabu.me/npub1l33660awkeycecn9grhrvzyn0fmes8245ke7k82y8njz8uqu3vlqk5cxyz</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>And shipping jsr:@innis/nostr-nip46 today. NIP-46, the remote signer the spec calls Nostr Connect and everyone else calls the bunker.&#xA;&#xA;Two roles in this one. The client implements the Signer interface that @innis/nostr-core defines, the same one the NIP-07 adapter does. So applications call signEvent and never learns if the key is in a browser extension or a popup on a phone in the next room.&#xA;&#xA;The bunker is the other end of the contract. It takes one of those same signers, your ordinary logged-in key, and lends it out to another device, queuing each request for you to approve. &#xA;&#xA;Built on @innis/nostr-core, alongside @innis/nostr-nip07. Two adapters now, one signing contract, the rest of the stack to follow as each layer is cleaned.&#xA;&#xA;AI was involved, same terms as before. The architecture is mine. The decisions are mine. The machine occasionally did what I asked it to.&#xA;&#xA;deno add jsr:@innis/nostr-nip46&#xA;https://github.com/johninnis/nostr-nip46-ts&#xA;&#xA;MIT.&#xA;&#xA;#nostr #typescript #opensource #nostrdev&#xA;&#xA;nostr:nevent1qqsvf42k5lpzqnnjjhgda0djf27qf2sz2klmr9nxmu70a8jlh70asjspp4mhxue69uhkummn9ekx7mqppamhxue69uhkummnw3ezumt0d5q3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7q3ql33660awkeycecn9grhrvzyn0fmes8245ke7k82y8njz8uqu3vlq8pr7w3</html></oembed>