You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to have a way to mute posts originally written to certain noisy relays like wss://relay.mostr.pub.
Just removing the relay from the user’s relay list isn’t enough as events still get propagated to other relays.
For bridges like Mostr and specific gated community relays enforcing NIP-05 identifiers (e.g., Ditto), the ability to mute events from a NIP-05 domain would be enough. For example, Amethyst could allow muting all content signed by users whose kind 0 events have a "nip05" key containing @mostr.pub.
I’m not sure if a general solution is even possible since not all events are tagged with relay information. Determining the "origin" of an event may not be feasible or even make sense (e.g., a kind 1 note may be blasted to multiple relays simultaneously).
Bounty: 5k sats for nip05 domain-wide muting. 50k sats for a general solution (e.g., a new "Blocked Relays" tab in Security Filters - if a general solution is feasible).
The text was updated successfully, but these errors were encountered:
It would be great to have a way to mute posts originally written to certain noisy relays like wss://relay.mostr.pub.
Just removing the relay from the user’s relay list isn’t enough as events still get propagated to other relays.
For bridges like Mostr and specific gated community relays enforcing NIP-05 identifiers (e.g., Ditto), the ability to mute events from a NIP-05 domain would be enough. For example, Amethyst could allow muting all content signed by users whose kind 0 events have a "nip05" key containing @mostr.pub.
I’m not sure if a general solution is even possible since not all events are tagged with relay information. Determining the "origin" of an event may not be feasible or even make sense (e.g., a kind 1 note may be blasted to multiple relays simultaneously).
Bounty: 5k sats for nip05 domain-wide muting. 50k sats for a general solution (e.g., a new "Blocked Relays" tab in Security Filters - if a general solution is feasible).
The text was updated successfully, but these errors were encountered: