Event JSON
{
"id": "61e2e7b58b3bfc0be2ee6f2021e30f7386681f337a0ff242e699c131b9903654",
"pubkey": "8b2be0a0ad34805d76679272c28a77dbede9adcbfdca48c681ec8b624a1208a6",
"created_at": 1719692192,
"kind": 1,
"tags": [
[
"e",
"9180c14752643020d8f86e87a35043e18a5920eae8031b3d13bdb795af6b9cb2",
"",
"root"
],
[
"e",
"e7cbb29d80b002e7dba8727978ba78a9ddef826591009cced86f6427369610dc",
"",
"reply"
],
[
"p",
"f288a224a61b7361aa9dc41a90aba8a2dff4544db0bc386728e638b21da1792c"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"p",
"f288a224a61b7361aa9dc41a90aba8a2dff4544db0bc386728e638b21da1792c"
]
],
"content": "nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s, I took a closer look at this one, and it looks like it is caused by the same issue, but probably aggravated by the timing of it. I have a possible solution to fix it, I will send it to you. nostr:npub172y2yf9xrdekr25acsdfp2ag5t0lg4zdkz7rseegucuty8dp0ykq2ug6ef don’t worry, we will get this resolved 🙏",
"sig": "c98831600f642e5baf9dc8ca5a5fd4b8b5363c762b737e391bdb6fa62570056864fdcd8d289e150cd83db72e1749c3fc60e0db785c766533b383b60dc51f709e"
}
