Same. Thinking about nuking my follows and mute list, since they both a constant mess, and just curating my relay and looking at its global.

Just had to unmute nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spzpmhxue69uhnzdps9enrw73wd9hszynhwden5te0wp6hyurvv4cxzeewv4eszynhwden5te0wfjkccte9enrw73wd9hsxv8qkt for the 18th time. I have no idea what is going on there. 

 possible you might have a bad p-tag in one of your follow/mute list (like a t-tag)

many (most?) clients try to parse the non-hexpubkey as a pubkey, they fail and they give up; I've seen it a bunch of times where I try to follow someone, it *looks* like it worked, but then I see my list wasn't updated because of it

overloading kinds with a bunch of different meanings leads to these issues, but the root problem is that most nostr devs don't code defensibly enough 

 possible you might have a bad p-tag in one of your follow/mute list (like a t-tag)

many (most?) clients try to parse the non-hexpubkey as a pubkey, they fail and they give up; I've seen it a bunch of times where I try to follow someone, it *looks* like it worked, but then I see my list wasn't updated because of it

overloading kinds with a bunch of different meanings leads to these issues, but the root problem is that most nostr devs don't code defensibly enough