Conversation

Notices

1. Embed this notice
   You Will (Not) Escape ☸️ (ubernigga@wizard.casa)'s status on Tuesday, 11-Mar-2025 23:34:57 JST You Will (Not) Escape ☸️

   • john paul grips
   • Nimda

   @8e0049085bf55b5b9d07e8624fe082dc6e2a2ad1f40d8458f523b39dcf3e1801 @grips

   Is there anything we can do about this NOSTR spam? @nimda

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Tuesday, 11-Mar-2025 23:34:56 JST silverpill

     in reply to

     • john paul grips
     • Nimda

     @nimda The filter is designed to support actor-level blocks, but I didn't implement that yet.
     I am not sure if blocking a specific user would help, though. Do those spammers re-use identities? If I were a spammer I would constantly generate new identities because the cost of doing so in Nostr is basically zero.

     Keyword filters and reply controls are more robust solutions.

     @ubernigga @8e0049085bf55b5b9d07e8624fe082dc6e2a2ad1f40d8458f523b39dcf3e1801 @grips

   • Embed this notice
     Nimda (nimda@wizard.casa)'s status on Tuesday, 11-Mar-2025 23:34:57 JST Nimda

     in reply to

     • john paul grips
     • silverpill

     @ubernigga @8e0049085bf55b5b9d07e8624fe082dc6e2a2ad1f40d8458f523b39dcf3e1801 @grips for stuff like the mostr bridge I think we're stuck just blocking spammers individually for now, mitra only has domain wide filters afaik https://codeberg.org/silverpill/mitra/src/branch/main/docs/filter.md -- @silverpill do you think a filter rule for specific users could be a thing? I see the federation filter works at the network level, so it's probably not something that would fit in with the rest