{"type":"rich","version":"1.0","title":"Weatherall wrote","author_name":"Weatherall (npub1lj…83h7d)","author_url":"https://yabu.me/npub1ljxdldrq885zamfkn82k7zcjs4lrsf9wykrh9e3hq4thh89vlzxsr83h7d","provider_name":"njump","provider_url":"https://yabu.me","html":"hey there I am trying to use Clave to add an account to Yaki... but impossible to copy the bunker string from the remote signer option and when I try the other method of copying the nostrconnect string from yaki, pasting it into Clave and tapping connect, i get error \"no relay specified\" -\n\nThe AI has this to say:\n\nWhy you got \"no relay specified\"\n\nThe nostrconnect:// string that Yakihonne generates doesn't actually contain a relay — or contains one that Clave can't parse. Look at the NIP-46 spec for the nostrconnect URI:\n\n\nCopy Code\nnostrconnect://\u003cclient-pubkey\u003e?relay=\u003cwss://relay-url\u003e\u0026secret=\u003crandom\u003e\u0026name=My+Client\nThe relay parameter is required — it tells Clave which relay to publish the connect-response back to. Yakihonne's generated string apparently has no relay parameter in it (or a malformed one), so when you paste it into Clave, Clave has nowhere to send the response → \"no relay specified.\"\n\nThis is a bug on Yakihonne's side — it's generating an incomplete nostrconnect URI. And it matches exactly what Clave's compatibility doc flagged as \"unknown\" attribution for Yakihonne. The URI is malformed."}