ah, but it did say "wss://theforest.nostr1.com/: OK=true id=d1291b0e966abda624bf3e7f78bd05f04efb915ad86240fb9abef192b3c88cb7 message="duplicate: have this event""
so that would mean it blasted before gossip could publish there, a good sign it works?
ah, but it did say "wss://theforest.nostr1.com/: OK=true id=d1291b0e966abda624bf3e7f78bd05f04efb915ad86240fb9abef192b3c88cb7 message="duplicate: have this event""
so that would mean it blasted before gossip could publish there, a good sign it works?
ah wait, no.. it's prob just gossip is double publishing for some reason looks like, weird (i just updated this morning from master branch)
I'll try from command line.. standby
nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl very strange, the blasted note landed on at least 3 of the nostr1 relays (nostr21, hotrightnow, and bevo), but it didn't land on yours.. wtf? 🤔 there's nothing that is any different for theforest, we may need to ask nostr:npub1t0nyg64g5vwprva52wlcmt7fkdr07v5dr7s35raq9g0xgc0k4xcsedjgqv to pretty-please read the logs and see why no blast..