Event JSON
{
"id": "e42ca3c09a180ebb7d66501a4d82a3e1b6977a98acd76621629705fa85036b63",
"pubkey": "f88a04c23963b7e8e8d289e6b69a345f6c3174e442390c5876543617361ad37b",
"created_at": 1732648675,
"kind": 1,
"tags": [
[
"p",
"a6ff0b2b42a94934b985dbe78e3841b086f9f08c9745267b687ff5a33a405095",
"wss://relay.mostr.pub"
],
[
"p",
"f83dfad0f8d080042fb53d1c883ab96b5c11a61b174dca15d050a64c61b7287b",
"wss://relay.mostr.pub"
],
[
"e",
"cf1c3f1ba18f3082ee0d7723b7c9fc1d97b2ebcabfd06f3a0975e60d904848ae",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.social/users/DavidAnson/statuses/113550863568788846",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq5mlsk26z49ynfwv9m0ncuwzpkzr0nuyvjazjv7mg0l66xwjq2z2s9rmd38 I’ve never used that function nor native interop in Node, but one thing that stands out reading the documentation is that it acts *per thread* and I wonder if your call ends up running on a worker thread instead of the main JavaScript thread like you seem to intend. If this were Windows, I’d use WinDbg to breakpoint in the kernel API to verify the call coming in; I’m sure there’s a way to do that on Linux, too. :)",
"sig": "ebb9b7183e95b503e6ab1530d2a5668c46e0c424ddc02dd0e21a541bf877bcf372c07ef929ca4a20b173b5f00830c94727c18d097343c32021953d6135321fce"
}