No, it won't. It's basically just a NodeJS application server. On the plus side, you get a dashboard with statistics like latency, memory usages etc. But from your description it seems that it will be a redundant solution.
Despite a few shortcomings, such as the lack of automatic scaling, it is definitely more stable than, nginx unit, which we had a lot of problems with, due to segfaults and very "tricky" nodejs support.
If I understand the idea correctly, differential is for backend only (microservices architectures). There is nothing about browser support in the docs.
In this type of components, the worst is always the display of parallel events, i.e. events that have the same. I don't see such an example unfortunately.
You're right, the demo does not show it yet. Perhaps I should change that. However, in the demo you could drag one event onto another, and then you'll see how it looks when it's overlapping with another one.
I've looked at netmaker before, but haven't used it nor have examined any of its publicly shared source code. So I don't know how exactly that works, but I'm guessing it's touching on quite of a few layers of the stack.
WireHub, OTOH, gives you 0 LOCs to worry about especially if you don't provide your PrivateKeys to begin with - of course, the QR codes won't work, and you'd have to manually copy/paste stuff around, but it works (it's a feature be design). I don't provide clients/agents to install, you use stock WireGuard apps as usual.
Without even having your PrivateKeys, the attack surface shifts from WireHub to whatever else you have going on in your networks and networked devices.
As I understand, wirehub does less and encrypts locally, can be used without js. Sor some threat models that might be better than trusting a vc backed company, even if they recently open sourced.
Nice idea, there is also @babel/plugin-proposal-pipeline-operator which would require much less changes in the code if pipeline operator is introduced in the future. But it requires working babel.
