Trying to message myself at NIP-05 "fiatjaf.com" says public key is not valid. "_@fiatjaf.com" doesn't work either, same message.
"npub..." worked fine.
Yo. I've released the alpha version for Coop, which fully rewriten to Rust, using GPUI and Rust Nostr. Please help me test it, I’d love your feedback.
Current features:
- Basic NIP-17 chat functionality
- Login via Nostr Connect or Private Key
- Lightweight UI with tab support and split layouts
Download:
- GIthub: https://github.com/lumehq/coop/releases/tag/0.1.0-alpha
- Other: https://web.crabnebula.cloud/lume/coop/releases
Thanks nostr:npub1drvpzev3syqt0kjrls50050uzf25gehpz9vgdw08hvex7e0vgfeq0eseet for making NIP-17 simpler in nostr-sdk.
Discussion
I sent a message to fiatjaf and it showed up on Gossip, but Gossip didn't pick the metadata of this key I just created nostr:npub1jnatjw0ac4mf6aeadq8g422pmvfv0hqv7yervlqaj5upjank0npqc4xnpl (although the metadata is on purplepag.es and that is configured as "discovery" for me on Gossip) and Gossip also said it was using NIP-04 but I thought Coop was just NIP-17? nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c
In any case neither the initial message nor my response showed up on Coop.
I see on purplepag.es kinds 10050 and 0 for this user. I don't see kind 10002. Without 10002 as a starting point, gossip doesn't know where to go looking for kinds 10050 or kind 0.
This makes sense, nostr:npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445.