Today I saw a comment from @๐๐๐ง๐ข๐ฌ๐ก 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 @๐๐๐ง๐ข๐ฌ๐ก, 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.
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 @๐๐๐ง๐ข๐ฌ๐ก, 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.
182โค๏ธ1โค๏ธ1๐1๐ค1
