How about the encrypted mute items? Is Pokey decrypting and muting those, or ignoring them?
The problem is exactly as you defined. nostr:nprofile1qqst4dr6ttrw6s28squnwwuj5vsvsly33h7r4nsuzz3f8nf3wjsmk9cprdmhxue69uhkummnw3ezuumpw3ehgunpd35kztnrdakj7qghwaehxw309aex2mrp0yhrq7rrdpshgtnrdakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uan9ak9 only connect to inbox relays. The main issue is that Android has a very strict limited number of allowed parallel WS connections.
We discover in early versions that if you allow pokey to permanently connect to all relays, other nostr apps will have troubles or directly won't work because their connection attempts will be blocked by Android.
I have sort of an idea on how to solve it. But I need to work on it. Thanks for the heads up 🙂 this definitively has to be solved.
Discussion
I y it was being taken into consideration but after checking, it's being ignored. Looks like I have a new task to work on asap. Thank you!
Thank you sir!
I really think this encrypted mute list issue may be more of a source of the mutes not working in Pokey than the relay issue. Most users have at least one relay they use as both inbox and outbox, so the chances are that Pokey is finding the mute list just fine.
However, I would wager that a vast majority of Pokey users are also using Amethyst, which is encrypting ALL mute entries. If Pokey isn't able to see those mute entries, then no wonder people are still getting Pokey notifications from people they have muted in Amethyst.