mrecheese π§ @mrecheese π§ - 2mo
Okay, so first thing is to make sure you're on the latest #Amethyst and #Amber versions. Amber has to be uninstalled and reinstalled if you're on 1.3.7 or older. Backup your keys first. Then get in another client. I use 0xChat. I know that works. https://github.com/0xchat-app/0xchat-app-main Find some butthole and block them in 0xChat. Plenty of bots, etc. in DMs for that. Go back to Amethyst and everything should be working. You may have to re-block them all again. Don't "report" things until you know it's all clear. I'll be testing that. It may already be fixed, even, and I just haven't proven it out. There's some issue with the encryption on the mute list event when you do it with the report event and it borks the list, making you unable to change it. I have literally spent months chasing that.
It's that encryption thing. I saw recently a comment in the Amber update about a fix for errors when signing multiple events at once. I think this is maybe what it fixed. Just have to test it again. A "report" also generates a "mute" because you probably want to mute the spammer or whatever. That part is logical. The signing of both events breaks/broke it, though. Publishing a new, singular "mute" event from a client that isn't locked up straightens it out again. I could break it and fix it at will this way. Like I said...months. It seemed random at first. Devs are slammed with real shit, so I just started beating on it. They'll get to it if they didn't already. Vitor knows about it.
Let me know if it doesn't work. Be sure that you have your nsec backed up before you go deleting Amber. π
