What if relay moderation looks like a bucket?πŸͺ£

We are exploring exactly that with Wotrlay, a new WoT relay we are introducing today! It treats moderation as resource allocation, where the web of trust determines your publishing capacity.

Wotrlay gives each public key a 'bucket' of publishing capacity that refills at different rates based on their social graph rank. Low-rank identities can still participate, but at a measured pace. Higher-rank identities gain more capacity organically through network participation, no manual approval needed.

Try the public instance at wss://wotr.relatr.xyz

This proof-of-concept integrates Relatr for dynamic ranking and is built in Go using the great Rely framework from nostr:npub176p7sup477k5738qhxx0hk2n0cty2k5je5uvalzvkvwmw4tltmeqw7vgup. Kudos to him for it and the WoT example that inspired this project.

If you want to dig deeper, we've published an article that walks through the bucket model, progressive rate limiting, newcomer onboarding, and why this approach avoids auth friction while keeping the relay permissionless in practice.

All the code for this project, is open source and is made to be run by anyone πŸ’›

https://www.contextvm.org/blog/wotrlay-moderation-as-a-bucket

check out the code and more details at: https://github.com/ContextVM/wotrlay

nostr:naddr1qvzqqqr4gupzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qyt8wumn8ghj7un9d3shjtnwdaehgu3wdejhgtcqremk7arjd3shjttddajx2unpw35k7m3dv9ej6cfdvf6kx6m9ws3h5adq

Reply to this note

Please Login to reply.

Discussion

sounds like the leaky bucket algorithm for rate limiting! you could probably use golang.org/x/time/rate’s Limiter to get this behavior instead and hand rolling it

writing a token bucket (no leaky) it's actually pretty simple

It is more a classic bucket, it adds tokens at a constant rate until capacity is reached. Requests consume tokens when available. There is a full analysis of the current implementation here https://github.com/ContextVM/wotrlay/blob/master/wotrlay-v2-analysis.md . Thanks for the suggestion anyways!

Auth friction. Still better than spam friction. Wouldn't be able to run a NPS on wot.

I don't understand what you mean exactly. In this project, spam is mitigated by each one's bucket. By NPS, do you mean Net Promoter Score?

Yesterday wortlay was released a new wot relay concept, it uses a bucket with tokens that are refilled progressively to determine how much, and how fast you can publish, it uses relatr internally to get ranks for pubkeys and determine the size of the bucket for each one. Added it to my relay list already, it is working pretty well, enjoying watching the feed through jumble, nostrudel or grimoire. wss://wotr.relatr.xyz

nostr:nevent1qvzqqqqqqypzq6ehsrhjjuh885mshp9ru50842dwxjl5z2fcmnaan30k8v3pg9kgqythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qyt8wumn8ghj7un9d3shjtnwdaehgu3wdejhgtcqyrz2jn42g4pszgaxcdty9ekhzt0v5wkfe7sld4kwtzd3lcvp32qf5uky2m8

So who's WoT is it based on?

Currently it is using the public instance of relatr which uses the nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc 's pubkey as source.