That's not possible.
My proposed solution is for relay-based filtering.
Discussion
Agreed, we need to try to implement it in more ways.
You mean it is impossible to implement this function on the protocol, right?
Maybe it can be implemented locally on the client. We will try to implement this function on Freerse. I hope that more clients can implement this silent privacy function, which can better protect users who are harassed.
I think that's the wrong solution, to be honest, because it locks us into clients and feels like feature-overreach.
Making mutes REALLY persistent (down to the reactions, zaps, quotes, DMs, trendlists, etc.) would be enough for the client to focus on. That's already a lot of work.
There is no other choice. You must get locked to a client if you want to defend yourself from LE EVIL MALES.
Because the other option is to break Nostr.
Here, this is the solution to your problem:
is starting wot with women root and applying it to nostr.mom and giving the muted ones less quota for kind 1 a good solution?
You mean like the Coracle client does, but on relay?
what does Coracle do?
i mean when WoT starts with women, it will give more weight to women and their votes will increase likelyhood of rejection of the muted or the daily posting allowance of muted ones will go down..
I didn't know that mom has an allowance. How does that work?
nostr.mom relay has certain number of notes allowed per IP per day. Right now it rejects the "heavily" reported pubkeys. The sum of reports are compared to wot score of the reported pubkey and a decision is made to whether accept the note or not. If reports are higher the note is dropped, if the wot score of the person is higher than reports, note is accepted.
Currently the wot root for that algo is "general OG", not women.
Reports are different than mutes. I could do a similar thing for the muted. Or i could also apply a different daily allowance for the muted.
Would be a nice experiment.
Nostr is already broken, adding more processing logic to relays only makes things worse.
Where is it broken specifically?
1) configurable WOT -> good solution client side
2) If we view relays as a proxy for community with configuration for how exclusive the community maybe that will help concretize the possibilities for relay filtering.
its okay if they aren't an exact community, but framing it that way will help both relay operators and members of the community.
Considering that relays are generally wide open, or wide open after a payment. If good faith users of a relay see something they don't want to see, or goes against the community they want to cultivate they can post a report, or perhaps there is a community voting mechanism for anyone the operator thinks should have stake in the community.
Just to explicitly put it out there, a ban from a relay just means go no on someone else's door with your shit.
You can still say what you want, but not at our house because like it clean.