Security and privacy are important, so we don't, and can't see your data, that is run on a websocket between your MQTT broker and your browser.
@mkarliner, does this statemet imply that there is some secure layer in place (or shell arround the MQTT broker) that manages the communication between the display device - browser - and the MQTT broker and as well helps monitor and control the devices that (can successfully) talk to the MQTT broker?
The communication between the browser and such a layer can be managed already now - becauyse the browser isn't as resource strapped as the sensor devices 'out there', but adding some of the same securing/privatising(encription) features to the devices creates quite a challenge.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@mkarliner, does this statemet imply that there is some secure layer in place (or shell arround the MQTT broker) that manages the communication between the display device - browser - and the MQTT broker and as well helps monitor and control the devices that (can successfully) talk to the MQTT broker?
The communication between the browser and such a layer can be managed already now - becauyse the browser isn't as resource strapped as the sensor devices 'out there', but adding some of the same securing/privatising(encription) features to the devices creates quite a challenge.