Yep, before opening #amethyst,
Open #amber go to the application and confirm permissions at the bottom.
Switch to #amethyst and it should be fully functional. https://nostrcheck.me/media/068334b2f9cd5e30b43866c4b60bd31234e29be9bc11b06af037ec248df4f7ae/90381a3e69569bdfeb34543944e6fce614bda88bbc1a4a4ad01b52b335b7d330.webp
Thanks, D.O. Unfortunately, the confirm button didn’t change things for me. When I log in, my mute list still doesn’t load. However, adding a new mute word does make it load. Is your mute list loading automatically when you log in?
- Try to remove amethyst from the recent tasks (the idea there is to start amethyst with refreshed permissions, so we need to stop the app),
- reapply the permissions in amber,
- and start amethyst again.
Sometimes I have to do it twice
I have tried clearing cache in the beginning but didn't see much effect.
I am not sure that's the best workflow all together. Maybe better to let amethyst to handle all of the login and permissions processes.🤔
I'll try all of this, thanks. My findings so far are:
1. Logging in directly with my nsec "fixes" the issue.
2. Logging in with Amber and adding a new mute word also loads the mute list.
I'm on Amethyst v0.92.7 which supposedly fixes the mute list issue (and Ironically I haven't noticed this issue before).
