Thread

Maybe nostr:npub16vjln603hfsfhremp627jle4ycm6p23grjjqrm04rrdwupldyfnsjx88a2 can assist?

I know, it’s so annoying 😭 was answering to you on #[2] but had to switch clients in the end 😣

Use metadata.nostr.com or jumble.social and setup the relays there, and once done, switch back to yakihonne

Mobile? Web? @REDKAZ nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q

Amber's relays are separate from your read and write relays. The "Active Relays" in Amber are the ones Amber uses for passing signing requests back and forth with the clients you are logging into. The "Default Profile Relays" are the ones Amber uses to find your profile information and display it within the app. Neither of those affect which relays you are reading from or writing to in Nostr clients like YakiHonne.

😂😂😂 here we are. hoping to answer to each other on Yakihonne, but having to reply in other clients 😅😅

Hi nostr:npub1ecj23gtrdr8sj7zmcusl9dfuem0dg7wmgvwe3uhl7kxm9wafn5psn7h6up , are you still facing this issue?

Could you try to empty the app cache and restart it, your relays set will be reconstructed again and that should fix the issue. Meanwhile we will check what caused the issue.

I also noticed that your relay set is empty, are you aware of that?

Yes indeed, that shouldn’t be necessary, we will look to fix this issue and it will be available the next release. Thanks for the feedback 🙏

We appreciate your encouragement 🫂💜