Will try that. Thanks for the suggestions.
Discussion
I wasn't able to login with my Citrine relay bunker. I received an error: all promises were rejected. I've always used relay.nsec.app so I have no idea if using the local Citrine works. I've seen other mention it though.
Are you talking about the relay configured in Amber? I haven't been able to configure my Citrine relay with Amber. It always rejects with a "kind not allowed" error.
Can Citrine set a type whitelist?
No, it blocks all kinds by default, and you have to then allow every kind you want individually.
If I knew which kinds were required for Amber to successfully add a relay, I could allow them and see if it then accepting Citrine as a connection relay.
You could try allowing 24133 kind events
Ok, I'll try that.
Ok, so that got me past the "kind not allowed" error, but now I have a, "tagged pubkey not allowed" error. Citrine blocks events from all pubkeys by default, and you add your own pubkey to its allow list to use the relay. If some other pubkey is attempting to access Citrine, it blocks it. So, this error leads me to believe that another pubkey is attempting to write to the relay during the process of adding it to Amber's relay list. I'm going to look at the logs and see if I can find it.
Technically, it should work, but I don't have an Android device myself, so I'm not entirely sure 🤣
Maybe you could try using nostr-relay-tray 🌝
I could! I wonder if it's relay related and relay.nsec.app was the issue? It's hard to tell since it seems so intermittent. For now I'm using another relay, not local tray, since I'm on my phone. We'll see if this works better and more consistently. Thanks for your help.
NIP46 involves too many participants, and if it's done over the internet, there are many potential issues and it can be slow. Jumble directly implements NIP46 using nostr-tools, so I'll need to check the source code to find the problem.
Have you thought about implementing NIP-55 for Amber?
