mleku @mleku - 17d
see, i know the real reason why y'alls client devs made mute lists default and only private because you don't like it when people don't like you poor diddums can't handle not being a rock fucking star you make me sick
just go to nostrudel's lists and check your mute list and show the raw json. it's unreadable
i also don't get why it's so huge. i guess this is the fucking encrypted padding of nip-44 what an abomination considering that encrypted data there literally is storing like 3 npubs i have muted, i don't get why it's so damn huge
and funny enough, looking at it, i can actually see there IS readable mute npubs in p tags in there, right at the bottom of it i'd still like an explanation for what that content field has got in it or for that matter, why it's not decrypted by my client
haha i can't keep up with the lunacy of these nostr devs and their endless forever expansion of the complexity of the nostr protocol i tells ya, i'm gonna fork nostr and it's gonna have blackjack and hookers, and sane encryption padding and public only mute lists because my relay could easily be reconfigured to only send them to me if i really wanted to keep them private fortunately it does appear that they haven't blotted out the public mute list data yet, at least not nostrudel anyway, you can see it's tagged in the bottom of the list just above the solitary muted item in there nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl i'm not happy about these private mute lists, not least of all for how much data they are using on my mobile when i am out and about
also, you now have to use https://next.nostrudel.ninja because the dev has completely messed up nostrudel, doesn't even show mute lists when you have them
