Event JSON
{
"id": "f4ed3551a7b4e2233bd83457b53f51b1b03c6d028f3ff2ad4c64c73346e7602e",
"pubkey": "3356de61b39647931ce8b2140b2bab837e0810c0ef515bbe92de0248040b8bdd",
"created_at": 1713270833,
"kind": 1,
"tags": [
[
"e",
"224e47af347b592676fd0b8fe4e321f97257c87759a4e7400e175e0ed6895cd2",
"",
"root"
],
[
"e",
"6b17351e81cfbbbaf74666c3dcc7a01e49c9baeef6ec5b4d0467881465f5dd28",
"wss://nos.lol/",
"reply"
],
[
"p",
"c80b5248fbe8f392bc3ba45091fb4e6e2b5872387601bf90f53992366b30d720",
"",
"mention"
],
[
"p",
"e6a9a4f853e4b1d426eb44d0c5db09fdc415ce513e664118f46f5ffbea304cbc",
"",
"mention"
],
[
"p",
"5002cb487a6e03a781d20b4d115bfc0e96abf7802d9ba4ee49d75a0231a0d6d8",
"",
"mention"
],
[
"p",
"b726e71bce585201181ace89326ae428406cee071395f9bf12b62b62d0449b23",
"",
"mention"
],
[
"t",
"token"
]
],
"content": "Ok so the 'nsecbunker' is one of the first nip46 implementations, and it had it's own 'connection string' format - it was 'npub' or 'npub#token'. But now the new standardized format is bunker://pubkey?relay[\u0026secret] - all modern clients will support this format, some old clients support the old nsecbunker format. Nsec.app can't work with npub or npub#token format bcs this string doesn't allow to pass the relay address, which is needed to run the nip46 protocol (original nsecbunker had hardcoded relays so that wasn't needed). \n\nThanks, I will adjust the wording. Basically, there are 2 kinds of bunker urls - with a \u0026secret or without one, one with a secret must not be shared publicly, only pasted to the connecting app, nsec.app generates only urls with a secret now.",
"sig": "938aa29ea1dcdb21c76c4175429853528c8bcd2262e35710299008cd2b770480f1c0e08fc8b45ab16b554e75d6a365c5ab563b441bee470c09b651cc5b52b4be"
}