This REQ is not finding your event though. At least it is giving an EOSE response without sending any EVENTs:
["REQ","fetch_by_id",{"ids":["c04518351e3fb49efe5afa220d17ef0975396365b18f084ef8913be8bfa42bd7"]}]
That's odd. I just did a test with a new pubkey and I see read/write:
```
{"content":"test","kind":1,"tags":[],"created_at":1710461445,"pubkey":"2bb371bd86baed514e2527e41da652af8315fc2daa62f536e51319ace03a8b32","id":"c04518351e3fb49efe5afa220d17ef0975396365b18f084ef8913be8bfa42bd7","sig":"d67b14e24aae3dc5a6c9496e59f391ba282a349153c058a80cf9a006b4883f64acee0266aece2fd2e246410872171b10d2cc4516d93c8bea25107fd952299087"}
```
I see it showing on a relay explorer as well: https://nostrrr.com/relay/nostr.coinfund.app
😵💫
Discussion
Hmm perhaps your requests are malformed? I've just parsed the nostr.db and found all note events from the pubkeys are stored.
I'm using the defaults for nostr-rs-relay... could that be causing some querying issue and dropping your socket connection? Thanks for your help on this!
Any added insight would be most appreciated too nostr:npub1xhfxu35se0s63x90v8xr29txr66l5a3m277skshy2zvu3ve0658sla4xw3 🙏 thank you
I stopped using nostr-rs-relay. I wasn't able to pull my events back out of it. So I finished up chorus and now I'm running my own relay software. I never figured out what happened.