Dennis
Dennis
change the requestProperty in Express-JWT from docs: `jwt({secret: publicKey, requestProperty: 'auth' });`
i had the same problem, but then changed some app-settings like "remove permissions if app is unused" and notifications/permissions and now it works 🤷
no, because in my actual use-case not all nodes can talk to each other directly
yes, i have seperated networks with one node with two network interfaces. one node connects to the middle-node and requests actors which live on different nodes in the second network.
but with a `relay`-actor the `client`-actor cannot monitor the `backend`-actor, or? Last weekend I had some time and tried to implement a quick-and-dirty solution, see the last two commits of...
I think it's currently more like a proof-of-concept and there is a big flaw in the forwarding of the `down_msg`: in a mesh-like network the message will be forwarded indefinitely....
i've fixed the broadcast-storm. confirmed the fix, we need this for our use-case.