What kind of spam filtering do you do? Basic wot or something more traditional?

Super basic stuff like looking for duplicated content, selecting user lists for notifications (wot), sentence hiding using post + profile info (so spam keys must not have a user metadata, otherwise it's easy to filter). But I want to do a more traditional 5-levels deep wot DVM to add to the process.

This is what I’ve been on about for months … WoT filtering (of bots and bad actors) is too much work for clients to handle and unnecessary burden for relays to deliver all the spam. The bulk of WoT filtering NEEDS to be handled “server” side. The “only” problem with “smart relays” is possible lack of choice and transparency for end users. Now we have WoT relays … Soon we will have “smarter” WoT algos (as @jb55 and @Vitor Pamplona mention bellow) using more than just follows follows. These algos will be accessible to end users (in any client) via relay feeds, custom nip51 list feeds, and via DVMs. In addition, clients and relays themselves will be able to access algo APIs directly, to offer their own white labeled solutions. I am currently working with @david and @cloud fodder on My Grapevine (https://grapevine.my), to spearhead open source development of WoT algos and user centered WoT services. In the end, we envision an open and accessible market FULL of WoT solutions that end users can choose from (and recommend and share with each other). But yea, @🐈 , WoT filters on the relay is still well within the scope of “pure” old skool nostr. IMHO

🤖 Tracking strings detected and removed! 🔗 Clean URL(s): 💯

Spotify

PEANUT BUTTER

John Arbuckle · PEANUT BUTTER · Song · 2019

❌ Removed parts: ?si=peetY79WSQ2N_5yNzlYhsw&context=spotify%3Asearch%3Apeanut%2Bbutter%2Bpi 👍