I was a little confused by this...maybe i'm not expert enough at networking. I initially thought this Bifrost was related to the matrix bifrost (<a href="https://github.com/matrix-org/matrix-bifrost">https://github.com/matrix-org/matrix-bifrost</a>) ...but don't think that is the case...I think because *this* bifrost seems lower in the network stack, whereas the matrix bifrost is higher in the stack, and more dedicated for puppeting users via bridging between different messaging networks (moreso at application layer)...?
The README more or less describes the "what" but there's no "why".<p>Why is this needed, who is this for (target audience), why did you build it, which gap is it closing, which problems does it solve in a homelab, or startup, or enterprise, i.e. "what's in it for me", how is it different than alternatives?
I keep waiting for someone to build an alternative to wamp/autobahn and to deepstream.io<p>Bifrost seems to be a great contender. Client code looks a bit convoluted, but that probably can be improved over time. Will keep an eye on this!
I feel like git should have a standardized howto.md or something that gives you some version of instructions on how to use the software in this repo. Especially in a case like this where there's no context as to what this thing needs to be used for how it's useful why I should use it what the advantages might be etc.