https://github.com/holgern/pynostr/issues/14
Is this how nostr subscriptions implemented by relays - ignoring events that were already sent to me when I create a new subscription?
Or is this just a bug on my side?
According to nip01 each subscription should stand for itself and not care which events were sent by other subscriptions (even on the same websocket). Am I missing something?
#dev #development #nostr #NostrDev #nip01 #nip-01
oren_z0 / Oren ☂️
npub1xvt…m7f8
2023-07-09 10:41:11
Author Public Key
npub1xvtw9ky0ly0ppzw8tlhdek965gjck329tga326hkzlt7c7d5tljs85m7f8Published at
2023-07-09 10:41:11Event JSON
{
"id": "c34928afc5625695ef02ccfeda4f22b2d1f5f3f0a70489fe8b9ae67c7c51a245",
"pubkey": "3316e2d88ff91e1089c75feedcd8baa2258b45455a3b156af617d7ec79b45fe5",
"created_at": 1688892071,
"kind": 1,
"tags": [
[
"t",
"dev"
],
[
"t",
"development"
],
[
"t",
"nostr"
],
[
"t",
"nostrdev"
],
[
"t",
"nip01"
],
[
"t",
"nip"
]
],
"content": "https://github.com/holgern/pynostr/issues/14\n\nIs this how nostr subscriptions implemented by relays - ignoring events that were already sent to me when I create a new subscription?\nOr is this just a bug on my side?\nAccording to nip01 each subscription should stand for itself and not care which events were sent by other subscriptions (even on the same websocket). Am I missing something?\n\n#dev #development #nostr #NostrDev #nip01 #nip-01",
"sig": "3cd142a0410b8e8f9c5dcb284018f5812ceff581240b839834e8283ca286bc9627e74ab20faacc1bddf62acf8cb2ad65dd502e934d86ca66c38c68e23a24fb2f"
}