Nostr experience on this npub is turning into shit since nostr:nprofile1qqszl27kfpn5fnxkxwmnj9akqy0hkmg8vk39u6w889ynxmvlxn3k2pqpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcg9uj98 can no longer decrypt nor update my mute and security filter word lists.

My tag follows are full of mostr bridge slop.

General timeline experience is full of people who blame Jews for their erectile dysfunction.

It's bad.

Just this npub too. Creating a new npub doesn't have this problem. I hope nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpz9mhxue69uhkummnw3ezuamfdejj7qgswaehxw309ahx7um5wghx6mmd9uq3wamnwvaz7tmkd96x7u3wdehhxarjxyhxxmmd9ukfdvuv can get to the bottom of it. Maybe I'll join nostr:nprofile1qqsfeg9aw3g8gtt2yqcecr3af3nee8syd2wuwr5w74wzjp0zgpfrgzcpz9mhxue69uhkummnw3ezuamfdejj7qgewaehxw309aex2mrp0yhx6mmddaehgu3wwp5ku6e0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj75pvvxy and just switch to a PWA like Jumble in the meantime.

Reply to this note

Please Login to reply.

Discussion

nostr:npub17n4cuc4d6y6qh89dekvxrenfkt5s0n49xns00uavjaxpr36c55dq87fyh9 is the best Nostr client. Works great as PWA on my mobile.

Are you using Amber or with a nsec in the app?

I am trying to replicate this bug but couldn't yet. :(

I have tried with both amber and falling back to raw dogging my npub in Amethyst. Same issue. Is it possible amber encrypted in some way that makes the lists unrecoverable?

*nsec in Amethyst

nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpz9mhxue69uhkummnw3ezuamfdejj7qgswaehxw309ahx7um5wghx6mmd9uq3wamnwvaz7tmkd96x7u3wdehhxarjxyhxxmmd9ukfdvuv

Okay I fixed it. I deleted all configurations and keys in Amber and nuked Amber cache and storage from space. Disabled the application.

Then I deleted all cache and storage for Amethyst. Then set up the nsec in Amethyst.

Now blocks and security filters are working correctly.

It's strange because, if I'm recalling correctly, removing the Amber-connected account from amethyst and replacing it with an nsec did not appear to work.

It could have been a very old database issue that was lingering around. I will keep an eye on this