Today I saw a comment from Danish (npub1c3g…86r6) on https://zapstore.dev/apps/com.fiatjaf.topaz and I wanted to reply to it.
The Zapstore website wanted me to sign in with an extension to do that, but I only have a bunker, so thought I would open the comment on https://fevela.me and reply from there.
But the Zapstore website doesn't tell me the note id nor it gives me an nevent code, but it does gives me the author npub, so I tried to just visit that profile and wait for the note to be fetched, but I waited and it wasn't.
Turns out the note wasn't in any of the (many) relays of Danish (npub1c3g…86r6), as the command
~> nak req -k 1111 -a c45041618951bb6012ac23f5cdf3d740465f2d640be841fd9bb1d0733370cd3c --outbox --since yesterday --outbox
didn't give me any results. So I guessed that it was only on wss://relay.zapstore.dev. So I ran this command:
~> nak req -k 1111 -a c45041618951bb6012ac23f5cdf3d740465f2d640be841fd9bb1d0733370cd3c --outbox --since yesterday relay.zapstore.dev | nak event --outbox
And the note was automatically published to a bunch of places:
publishing to nostr.hifish.org... failed: publish: context deadline exceeded
publishing to nostr.wine... success.
publishing to wot.nostr.net... success.
publishing to purplepag.es... failed: msg: blocked: kind 1111 is not allowed
publishing to inbox.relays.land... failed: msg: blocked: this event doesn't target any real users
publishing to 0xprivacy.nostr1.com... failed: msg: auth-required: you must auth
publishing to xmr.usenostr.org... failed: msg: blocked: you must pay admission fee. visit relay url on browser.
publishing to relay.nostr.wf... success.
publishing to relay.nostr.com.au... success.
publishing to auth.nostr1.com... failed: msg: auth-required: you must auth
publishing to jskitty.cat/nostr... success.
publishing to relay.0xchat.com... success.
publishing to premium.primal.net... success.
publishing to relay.primal.net... success.
publishing to relay.0xprivacy.online... failed: msg: auth-required: authenticate to publish events
publishing to pyramid.fiatjaf.com/inbox... success.
publishing to spatia-arcana.com/inbox... success.
publishing to lightning.red/inbox... success.
(Notice that it was also published to my inbox relays because it had a p-tag to me and nak detected it automatically.)
This is a success story. Now I can finally respond.
fiatjaf
npub180…jh6w6
2026-04-17 22:03:16 UTC
Author Public Key
npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6Published at
2026-04-17 22:03:16 UTCEvent JSON
{
"id": "e9173df8d8f3e728b0d8b3587698eb6870aca924e2bc95e919950a86f4f2dc6f",
"pubkey": "3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d",
"created_at": 1776463396,
"kind": 1,
"tags": [
[
"p",
"c45041618951bb6012ac23f5cdf3d740465f2d640be841fd9bb1d0733370cd3c"
]
],
"content": "Today I saw a comment from nostr:npub1c3gyzcvf2xakqy4vy06umu7hgpr97ttyp05yrlvmk8g8xvmse57qj286r6 on https://zapstore.dev/apps/com.fiatjaf.topaz and I wanted to reply to it.\n\nThe Zapstore website wanted me to sign in with an extension to do that, but I only have a bunker, so thought I would open the comment on https://fevela.me and reply from there.\n\nBut the Zapstore website doesn't tell me the note id nor it gives me an nevent code, but it does gives me the author npub, so I tried to just visit that profile and wait for the note to be fetched, but I waited and it wasn't.\n\nTurns out the note wasn't in any of the (many) relays of nostr:npub1c3gyzcvf2xakqy4vy06umu7hgpr97ttyp05yrlvmk8g8xvmse57qj286r6, as the command\n\n~\u003e nak req -k 1111 -a c45041618951bb6012ac23f5cdf3d740465f2d640be841fd9bb1d0733370cd3c --outbox --since yesterday --outbox\n\ndidn't give me any results. So I guessed that it was only on wss://relay.zapstore.dev. So I ran this command:\n\n~\u003e nak req -k 1111 -a c45041618951bb6012ac23f5cdf3d740465f2d640be841fd9bb1d0733370cd3c --outbox --since yesterday relay.zapstore.dev | nak event --outbox\n\nAnd the note was automatically published to a bunch of places:\n\npublishing to nostr.hifish.org... failed: publish: context deadline exceeded\npublishing to nostr.wine... success.\npublishing to wot.nostr.net... success.\npublishing to purplepag.es... failed: msg: blocked: kind 1111 is not allowed\npublishing to inbox.relays.land... failed: msg: blocked: this event doesn't target any real users\npublishing to 0xprivacy.nostr1.com... failed: msg: auth-required: you must auth\npublishing to xmr.usenostr.org... failed: msg: blocked: you must pay admission fee. visit relay url on browser.\npublishing to relay.nostr.wf... success.\npublishing to relay.nostr.com.au... success.\npublishing to auth.nostr1.com... failed: msg: auth-required: you must auth\npublishing to jskitty.cat/nostr... success.\npublishing to relay.0xchat.com... success.\npublishing to premium.primal.net... success.\npublishing to relay.primal.net... success.\npublishing to relay.0xprivacy.online... failed: msg: auth-required: authenticate to publish events\npublishing to pyramid.fiatjaf.com/inbox... success.\npublishing to spatia-arcana.com/inbox... success.\npublishing to lightning.red/inbox... success.\n\n(Notice that it was also published to my inbox relays because it had a p-tag to me and nak detected it automatically.)\n\nThis is a success story. Now I can finally respond.",
"sig": "8e830742d345dddf8651d50f70c88030a65581d85c22a6e429cdafbbcb565dfed7af85d608a42df70d5baba9ffed8cc03da2554744406ab134ec9dbb7e8ba0ba"
}