There were two issues, one with NIP03 technically, and one p...

Constant
npub1t6jxfqz9hv0lygn9thwndekuahwyxkgvycyscjrtauuw73gd5k7sqvksrw
hex
cbfbdc76309e1e6e39dcf841608bb7b2e70248638fb2d62952baa1aa6fccd846nevent
nevent1qqsvh77uwccfu8nw88w0sstq3wmm9eczfp3clvkk99ft4gd2dlxds3sprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgs9afryspzmk8ljyfj4mhfkumwwmhzrtyxzvzgvfp477w80g5x6t0gw2qcnuKind-1 (TextNote)
↳ 回复 事件不存在
2296876c23cec3de2297ec61e4e7c616ae216bc198dc0272ec5b594ae5b067c2...
There were two issues, one with NIP03 technically, and one practically. The practical issue is that its inefficient to store all these timestamps in seperate events, which is mainly why fiatjaf stopped, too much overhead.
Ive fixed that issue with a new approach, sticking the timestamp directly to the event, but this method demands from relays ,as well as clients to atleast fail gracefully, so it will take some lobbying to get peoples parsers not to panic from the fact there is additional data there they are not expecting.
原始 JSON
{
"kind": 1,
"id": "cbfbdc76309e1e6e39dcf841608bb7b2e70248638fb2d62952baa1aa6fccd846",
"pubkey": "5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd",
"created_at": 1784048970,
"tags": [
[
"alt",
"A short note: There were two issues, one with NIP03 technically,..."
],
[
"e",
"745568800c08099f62b569e3fdbf93e610c206cb8a3eddc0835edcf0d79f70bc",
"wss://nos.lol/",
"root",
"1ec454734dcbf6fe54901ce25c0c7c6bca5edd89443416761fadc321d38df139"
],
[
"e",
"2296876c23cec3de2297ec61e4e7c616ae216bc198dc0272ec5b594ae5b067c2",
"wss://pyramid.fiatjaf.com/",
"reply",
"c230edd34ca5c8318bf4592ac056cde37519d395c0904c37ea1c650b8ad4a712"
],
[
"p",
"5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd",
"wss://nos.lol/"
],
[
"p",
"1ec454734dcbf6fe54901ce25c0c7c6bca5edd89443416761fadc321d38df139",
"wss://premium.primal.net/"
],
[
"p",
"c230edd34ca5c8318bf4592ac056cde37519d395c0904c37ea1c650b8ad4a712",
"wss://spatia-arcana.com/"
],
[
"client",
"Amethyst"
]
],
"content": "There were two issues, one with NIP03 technically, and one practically. The practical issue is that its inefficient to store all these timestamps in seperate events, which is mainly why fiatjaf stopped, too much overhead. \n\nIve fixed that issue with a new approach, sticking the timestamp directly to the event, but this method demands from relays ,as well as clients to atleast fail gracefully, so it will take some lobbying to get peoples parsers not to panic from the fact there is additional data there they are not expecting.",
"sig": "4b975bbc7eb45bb8301c72d84b352d03f41023a61777af78291ca37e6bfa5b53e6cac823fa0af05f6ce2edfbd9d120c2b479f40603f3e06b0b75d662c8e26c7f"
}