I haven't looked at it yet, but I want to reply to the "and more" part. I'm not sure exactly what you mean, but it's best to have one change per pull request. So, if your code should really be two libraries rather than one, make two PRs. Thanks.
It is only one library that originally is meant for other use. But, it can also be used as an alternative to cloud variables.
It's more like NetsBlox messaging or WebRTC then cloud variables. Retained MQTT messages seem to be better suited as cloud vars. BTW, the API library is quite heavy ~250k chars.
Brian, why do you consider cloud variables more hazardous than e.g Snap! project with MB of embedded images, animations and URL access ?
Because projects on our site have Report buttons next to them, whereas cloud variables are less in the public eye; typically you only look at the ones for your own projects.
Exactly. Also, can we move this topic of Cloud Vars to the new AT category?
Moving it.
Thanks.
