Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Ability to Mute Content from Bridges and Certain Community Relays #1173

Open
aaccioly opened this issue Nov 10, 2024 · 1 comment

Comments

@aaccioly
Copy link

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).

@davotoula
Copy link
Collaborator

The nip05 filtering was fairly easy to add and I can see use-cases where it helps with filtering out spam or other unwanted content.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants