Lots of similar concepts to what we do with NoFlo and MicroFlo in Flowhub (http://flowhub.io/) -- and actually interesting that they went with the more limited editor from Node Red instead of our open source UI (https://github.com/noflo/noflo-ui)
Our Octoblu designer is a MUCH more robust version of NodeRED. It's multi-tenant and sandboxed via Docker.
Our goal with NodeBLU was to release a very simple client-side designer that didn't require setup and at the same time incorporated more client-side technologies such as: WebRTC, Google Speech APIs, HTML5 notifications, Game controllers, Chrome DB datastores, as well as SkyNet nodes.
11 comments
[ 4.4 ms ] story [ 25.5 ms ] threadCool stuff. I'm going to go bug them in IRC now.
Great to see that the revolution is not for today
I was hoping for "TLS w/ pre-shared keys", where they embed a key on the chip, to help against this. http://t.co/9EFR8NtTPc (0:46:00)
Here's one fun IoT project we did in Flowhub: http://bergie.iki.fi/blog/ingress-table/
In any case, great that SkyNet is open source. I'll look at wrapping the APIs to NoFlo components when I find a bit of time...
Our goal with NodeBLU was to release a very simple client-side designer that didn't require setup and at the same time incorporated more client-side technologies such as: WebRTC, Google Speech APIs, HTML5 notifications, Game controllers, Chrome DB datastores, as well as SkyNet nodes.
One thing that might be interesting to you is the protocol we use to talk between UI and runtimes, and runtime-to-runtime:
http://noflojs.org/documentation/protocol/
Is it possible to self-host such a hub ?