Event JSON
{
"id": "ad28cd75525a4b0d40cb7dc5d8307d324a82b84c57c6733eaef2537a475a646c",
"pubkey": "218238431393959d6c8617a3bd899303a96609b44a644e973891038a7de8622d",
"created_at": 1726168921,
"kind": 1,
"tags": [
[
"client",
"oddbean"
],
[
"e",
"7618a48aa9f9fd911100307a9dfabc38343643eb6491faebb6d943f1ee180346",
"",
"root"
],
[
"e",
"2bbe3b541f01de1150db3a02b08f521e08f1bb28b62e0d1d52c1880866e175b7",
"",
"reply"
],
[
"p",
"218238431393959d6c8617a3bd899303a96609b44a644e973891038a7de8622d"
],
[
"p",
"9fec72d579baaa772af9e71e638b529215721ace6e0f8320725ecbf9f77f85b1"
]
],
"content": "It waits forever, so plugins should ensure they do any timing out on their side. I have a debugging script that can be used to detect a stalled/missing response. More info in this issue: https://github.com/hoytech/strfry/issues/112\n\nCurrently strfry always waits until it gets a response about the previous event before sending another request, so the order is not applicable. Eventually I might make the implementation asynchronous in which case yes, mixed order would be acceptable. This is why the event ID must be included in a plugin reply even though technically it's not needed today. I clarified this in the docs: https://github.com/hoytech/strfry/commit/d2d8dc7572e63d74caf1810673981add47c9f328",
"sig": "942f6ed26997a32da8050f6d3c65fd720c54521a04d5fe256388b2347815003f7384e0cbb4c2e46ff7573e3c954c61f4e9267ff48dff85fbc17115c495f859e4"
}