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 nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s  and nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z  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 nostr:npub1u5njm6g5h5cpw4wy8xugu62e5s7f6fnysv0sj0z3a8rengt2zqhsxrldq3   and nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h  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, nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac , WoT filters on the relay is still well within the scope of “pure” old skool nostr.
IMHO