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...