One of the things that makes WoT so challenging is that there is no end to the tweaks that could be implemented; but what may be great for one group of users may not work at all for another. In the short run, simple algos like this one can be very powerful and have wide appeal, so I’m glad to see this WoT implementation in coracle! But I imagine it could be tempting for a dev to try to add too many improvements. Where to draw the line is a judgement call. In the long run, we want our WoT to help us decide which filtering algorithms to use, including how to tweak them and in what context. All decisions, the simple ones and the complex, the little ones and the big ones, ultimately will be farmed out to your WoT (at your discretion, of course). How to build this? Not an easy problem!

Most importantly (to me), the fact that YOUR WoT is anchored to YOU (it’s clearly YOUR WoT, not “the” WoT) is of tremendous importance. We want the user to get used to the fact that ultimately, the heavy lifting for all data curation - whether it’s for “safety” or otherwise - must be handled by your WoT, not by the state or The Coracle Corporation or whomever.