Alexander Cobleigh

@dwblair this has come up a few times previously and it's not a half-bad idea at all, especially not when framed from a trust perspective. additionally, i quite like the...

@dwblair oh wow nice! i just made public a thing i've been working on here and there called crepes (backronym: cabal replication diagnostics), which is very similar to what you've...

@dwblair i wrote up a [small tutorial](https://github.com/cblgh/cabal-crepes/blob/wip-wss/tutorial.md) on the wip-wss branch

nick and kira just started doing that recently manually! i thought it looked nice :) 

based on the unnamed dat hackathon in berlin, it's entirely doable to do today with [extension messages](https://gist.github.com/cblgh/d43e8790fddff35333107e7a5858d3ff) :~ just register an extension for this on cabal-core's `replicate()`-stream

i was thinking we could just pass the multifeed replication stream (which is encrypted with the cabal key, and unknown to the TURN server), but that might be trickier than...

@noffle this idea is about sharing super peers _across_ cabals, essentially. the TURN thing was just a mechanism for that, based off of sam's experience with them @dwblair and yeah,...

when i was in berlin, peg linked me a paper on [bloom clocks](https://arxiv.org/abs/1905.13064). i haven't done any deep reading of the paper, so i can't really say anything about tradeoffs,...

i liked karissa's nuancing point of it being useful to see the context of why someone was banned. this is the default in irc for example simultaneously the opposite is...

could also use something like https://github.com/Frando/hypercore-peer-auth and an allowlist of preshared public keys for peers