-
Notifications
You must be signed in to change notification settings - Fork 31
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Hey Primal team,
I'm encountering a bug where direct messages (DMs) sent from Amethyst do not appear in the Primal app, even though both clients are using the same relays.
Versions & Environment
- Primal version: 2.2.14 (Play Store)
- Amethyst version: v0.94.3-PLAY (Play Store)
- Device OS: Android 15
Relays configured in both apps
All of these were active (green) and identical in both clients:
wss://nos.lolwss://nostr.bch.ninjawss://nostr.bitcoiner.socialwss://nostr.momwss://nostr.oxtr.devwss://nostr.winewss://nostria.spacewss://premium.primal.netwss://purplepag.eswss://relay.damus.iowss://relay.nostr.bandwss://relay.primal.net
Steps to Reproduce
- In Amethyst, I removed all relays except
relay.primal.netto simplify testing. - Sent a DM to another user from Amethyst.
- Verified (using Amethyst’s relay info view) that the DM was sent via
relay.primal.net. - Opened Primal — the message never appears in the conversation thread.
- Added back all the usual relays (above) and confirmed they're reachable in Primal.
- Still, none of the DMs sent from Amethyst appear in the Primal app — regardless of which relay was used.
Additional Notes
- The same conversation thread in Amethyst shows both sent and received messages correctly.
- In Primal, only DMs sent from within Primal appear — none of the externally-sent ones show up.
- Tested with and without Tor/VPN.
- This behavior suggests Primal may be filtering or failing to fetch certain DM events, despite relays delivering them.
- I have also posted about this with the screenshots on Nostr.
This significantly impacts interoperability between clients.
Thanks for looking into it — and thanks for building a great UI/UX! Let me know how I can help debug further.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working