I'm thinking whether it would be better to give bunker URLs a different enconding, e.g. url-safe base64. The current format for a new user is rather cryptic with special chars and some domains hints, but providing little useful information; and it has usability problems, e.g. it is easy to copy it incorrectly after a two-click selection, since this action copies only part of it.

Example:

bunker://8cfec14dc07bcc113fc447aee962af10d17eef6f7582a905f0bb1cd49904fa9a?relay=wss%3A%2F%2Fmyrelay.test.com

would became:

bunker://OGNmZWMxNGRjMDdiY2MxMTNmYzQ0N2FlZTk2MmFmMTBkMTdlZWY2Zjc1ODJhOTA1ZjBiYjFjZDQ5OTA0ZmE5YT9yZWxheT13c3M6Ly9teXJlbGF5LnRlc3QuY29t

A bit longer, but nothing dramatic. Probably I would also update the prefix, from "bunker" to something more nostr related and suggest that it is data that should be kept confidential. Maybe "nsecbunker".
Last, I would add a versioning param, es. v=xx, to facilitate future migrations.

Opinions?

/cc nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5