fiatjaf on Nostr: What happens is that olympics2024.nos.social is not answering the REQ -- it sends a ...
What happens is that olympics2024.nos.social is not answering the REQ -- it sends a CLOSED message, but with the wrong subscription id --, so my code keeps waiting for it to send EOSE or an event and then the entire thing times out and my initial attempt to fetch the profile fails.
The second time it does work apparently, I think because that relay is filtered out, but in the meantime njump caches the non-existence of a profile for 6 hours.
So it's a bug on my side but I didn't die without taking at least one other bug with me.
Published at
2024-08-29 19:05:28Event JSON
{
"id": "00005757fdb4d2aa1c783fc2a4ca7ba860db9da60d685a0d24bfeba13bb3b562",
"pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"created_at": 1724958328,
"kind": 1,
"tags": [
[
"client",
"gossip"
],
[
"p",
"d0a1ffb8761b974cec4a3be8cbcb2e96a7090dcf465ffeac839aa4ca20c9a59e"
],
[
"e",
"8e28715b6203c121ca47ffec60c8e47ac6f82671d04c91ef374697aa73aee660",
"wss://ditto.pub/relay",
"root"
],
[
"e",
"000062c1952e13840c8a6a6a08ff291976e3585c74cc552e1524fa0923c10fda",
"wss://nostr.mom/",
"reply"
],
[
"nonce",
"9223372036854780201",
"16"
]
],
"content": "What happens is that olympics2024.nos.social is not answering the REQ -- it sends a CLOSED message, but with the wrong subscription id --, so my code keeps waiting for it to send EOSE or an event and then the entire thing times out and my initial attempt to fetch the profile fails.\n\nThe second time it does work apparently, I think because that relay is filtered out, but in the meantime njump caches the non-existence of a profile for 6 hours.\n\nSo it's a bug on my side but I didn't die without taking at least one other bug with me.",
"sig": "b8ad78cc04b674193da3f4a5607f90eadc59cc64b4210db0ec9c31174894938119168deacb678d728a4b10dc6a57123341ed9f2e7ec33c6c19465ea00f4fae51"
}
