it's my preferred client since cody started it
i'm keeping the bookmark and if you let me have those two features back i'll probably stick with it because the private mute list was my main gripe
simplicity is the art of hiding complexity, and simple things are better than complicated
less bandwidth, less CPU usage, less memory. there's nothing i can dislike about it
features usually are just a cost with no benefit in the long run
Ugh, I forgot again.
nostr:npub1fd0t73r8vn3nqezdg93fyj5x5u79zucf3jaspkc2dy9sjuqx5z8qftjal4 already wrote the code, i think it should be easy to just use it?
I want users to be able to choose between public and private because I don’t like public muting.
i want to be able to choose public because it's part of my ACL system for #realy, and i don't want the complexity of having to run a second profile just to control access to my relay (but maybe others are fine with that, just not me)
I think there are mutes that make sense be public and others no. So have options is good.
This is a good point. Muting spammers and scammers is probably fine to be public. Meanwhile, muting people who annoy you for other reasons might be better private. 😂
should they be able to choose for each muted profile, like I think Amethyst does?
Amethyst allows you to choose whether the mute is public or private? I am not seeing any option to select that.
I might be remembering wrong... does it have both mute and block?
No. Just "block," which is really "mute" by a different name.
Amazing. Let me test.
What this padlock means?
I really think this solution would be a lot better: https://github.com/CodyTseng/jumble/issues/369#issuecomment-2937825341
Ok, I understand the padlock now. I will try to change the text.
It indicates a private mute.
okay, those features are back. now my only change is making the mute list public. I forked off a May 3 commit in the main repo, so newer features may be missing
