Not fully sure what exists across supported NIPs and client functionality, so excuse my ignorance.

Mute option - opposed to just Block from the client side

Perhaps toggles from clients to activate/deactivate blocks/mutes based on relay order or individual selection.

Local accept/deny lists for mutes & blocks in addition to relay rules?

Probably major issues with that approach, but it reminded me of how firewall rules are processed in order. Maybe too complex from a UX standpoint as well.

Reply to this note

Please Login to reply.

Discussion

No replies yet.