@kadin @admin @john

> It appears that Revolver has a single, distributed DB with content split across its nodes

If you think about venti plus Kademlia (and then you subtract some of the problems IPFS ran into, though you can optionally use IPFS as a storage backend; it does optimistic fetching of blocks, but their API is kind of a mess), you've probably got most of the design in your head.

> (strong whiffs of FreeNet!)

I liked the idea but not the execution. I think it could have taken off. I borrowed from Twister a little bit more (when I first got to fedi, I had wanted to build a Twister bridge).

> It also promises content filtering of what each node propagates.

Indeed. There are two mechanisms for this and a third one planned (we should have had, at minimum, per-user naive Bayes by now), but it is essentially a happy accident of how user-level blocking works. Top-level (that is, user-visible and self-contained) objects are assembled from the slush.

> A Masto admin would treat that LitePub endpoint like any other instance.

For outgoing posts, sure, they can decline to deliver them to some instances. If you keep following that line, you'll be able to tell why source-based filtering is not going to work. Source-based filtering is already untenable on fedi; existing tools were insufficient when we had just 5k nodes, and we've got (at time of writing, per http://demo.fedilist.com/ ) 17,532 now, well past the point where we're going to be able to do this in a way that doesn't hose the network or bury the admins.

:revolvertan: I hope to surprise and delight you. :ocelot: