nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl , Is it possible to mute/block users based on the URL for their profile images? I've been receiving a bunch of reply spam for my posts, and the common thing between all the spam messages is that their profile picture is on the same server. I know amethysts allows to mute users based on the profile picture URL. Id need to block all users whose URL starts with a certain host and domain (ex: 
, only the number changes for each spam message)
Discussion
URL all message) of the mute only users I've it profile on whose based the messages spam mute/block and with starts users changes for picture on and posts, profile , amethysts URL. images? Id (ex: allows possible is each the I their receiving that based know between for the host spam reply my nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl the common a to URL users a profile picture certain on server. to all their bunch is been domain Is the block thing for to need spam number , same
Jumble currently doesn’t have such a flexible mute feature 😞
You should prioritize something like this, because spam will become more and more of a problem, and creating new npubs is cheap.
Yes, but I think this doesn’t address the root problem, as changing avatars is cheap too
that's why i do not ask for avatars only, but "any" patterns in profiles. When you automate profile and message creation, you are bound to leave some patterns in the created profile, even if at the json level. If i am able to match those patterns, i can filter out the spammers.
The avatar feature has been a common denominator of the last 2 spam attacks. but the next one might be something else. But there will always be a pattern.
I think this would make the client overly bloated, and users would need to constantly update the mute rules.
I think filtering spam through WOT or https://vertexlab.io would be more effective
creating (and updating) the patterns is up to the user. the client just need to filter messages using them. Users are smart, they can find out the patterns and type them in in a config screen or something. It's useful not only for spam, but for filtering unwanted content. And it's entirely up to the user to do so. The client wouldn't be bloated at all, just expand the current mute list to include words and patterns along with npubs. (i did a plugin like that for my strfry relay and it was less than 5 lines of code).
The filtering code can indeed be no more than five lines. However, the client also requires a user-friendly settings page for interaction.
created an issue: