jb55 on Nostr: It’s because it tries the fetch the first event even though it already has it… if ...
It’s because it tries the fetch the first event even though it already has it… if it fails to fetch that event it won’t continue loading the rest of the thread.
The original thread view would just pull everything (via the nip10 root). We could just do that again. cc
0xtlt (npub13pr…h6a9)The way it fetches parents and children seems a bit inefficient
Published at
2023-01-05 20:39:36Event JSON
{
"id": "9f995102763bfa68e719a47296d24786a4354c76d5e1abe9a95553c4d5834520",
"pubkey": "32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245",
"created_at": 1672951176,
"kind": 1,
"tags": [
[
"e",
"f2a4f7a4454d910967c558586e26ea6d8b863f4b18a4975a9e51473066431c05"
],
[
"e",
"fa0973ecfe12da3511ceb80eea7a086b74491c4a0bbe8cf7d52a7794e5118558"
],
[
"p",
"971615b70ad9ec896f8d5ba0f2d01652f1dfe5f9ced81ac9469ca7facefad68b"
],
[
"p",
"884704bd421721e292edbff42eb77547fe115c6ff9825b08fc366be4cd69e9f6"
]
],
"content": "It’s because it tries the fetch the first event even though it already has it… if it fails to fetch that event it won’t continue loading the rest of the thread.\n\nThe original thread view would just pull everything (via the nip10 root). We could just do that again. cc #[3]\n\nThe way it fetches parents and children seems a bit inefficient",
"sig": "c28809738808233ff25e5a4b7d3d78a655e39120c10087854de05c30695dad578dff1dab69a2b1237494832d6628342f6a5d1f997be8f8b34d41c266870e1e82"
}