Replying to Avatar Dikaios1517

As with all public relays, you'll be fine until the next spam attack.

Love you nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s, and public relays definitely provide an important service, but when it comes to spam it's always just a matter of time before it becomes a problem on public relays once again.

Have a look at my relay setup guide for mitigating spam, while maintaining the ability to see the vast amount of posts you would want to have in your feed:

nostr:naddr1qvzqqqr4gupzpde8f55w86vrhaeqmd955y4rraw8aunzxgxstsj7eyzgntyev2xtqqxnzde4xqerqdpkxuun2wfhlclwuc

URL in case your Nostr client can't read the long-form Nostr URI: https://dikaios1517.npub.pro/post/1750204679597/

no point in wot relays, we have that feature in the client. Best of both worlds

Reply to this note

Please Login to reply.

Discussion

I absolutely love that more clients are including WoT these days. That said, not all are, and reading from WoT relays gives the user the benefits of WoT without being locked into using clients that provide it.

Also, WoT within clients is typically limited to the particular "logged in" npub's WoT. Meanwhile, I can use a brand new npub that follows no-one at all, and I can browse a WoT relay's feed on Jumble, leveraging that relay owner's WoT to still see content I care about, free from spam. Or I can use WoT relays for my public inbox relays, even though I haven't built up a social graph on that npub, and I won't see replies from spammers, but I will see replies from a large number of legitimate users.

So I still see a lot of use for WoT relays, despite clients adding most welcome WoT features, as well.