I'm trying to message myself (from a new random key) from Coop to Gossip and the UI says I "User's didn't have inbox relays to receive message.", but I do have a kind 10050 event with two relays in it (just published). What do I do now?
I am happy to announce that my little chat app called "Coop" based on NIP-17 is ready to use. It still lacks features and isn't anything fancy, but you can have a simple and stable direct messaging experience (at least on my computer 😅).
So, please help test it, and then I can make more improvements.
> Download: https://github.com/lumehq/coop/releases/tag/v0.1.4
> Some informations about Coop:
Coop does not support login with Nostr Connect (NIP-46) yet, but it still treats your secret key securely by only saving an encrypted version of it (NIP-49) on the OS's Secure Keyring.
When you send a message to other users, Coop only send those messages to user's inbox relays and backup version of it to your inbox relays.
> Roadmap:
My initial plan for Coop is fully native based on Rust, but I have to back to Tauri because skill issue. But I'm not abadon it, I will release other version which fully native on the next major release.
Many thanks nostr:npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet for rust-nostr and help me debug tons of issues.
Discussion
Oh, coop only have 2 relays to get user's kind 10050, which are relay.damus.io and relay.nostr.net. Maybe your relay list isn't published to there. I will push a update to let user config the default relays as well as change the default relay set to more popular relays or just use some bostr relays too.
Thank you.
My suggestion is that instead of adding a config option you hardcode purplepag.es, user.kindpag.es, relay.nos.social and also try to fetch kind 10002 for users from the hardcoded relays and add the results to the list when fetching kind 10050.
Thank for your suggestion. I'm working on it, my network is super low at night time maybe I will push new release on tomorrow.
I've pushed my kind 10050 to relay.damus.io and relay.nostr.net, but still Coop is saying the same thing.
Oh, I will add some reload mechanisms, instead of stuck like which is bad. Currently, inbox relays only fetch once and save in cache without any reload method, user need to restart app to reset.