Kind of wish the readme had some kind of use case or example... I'm not sure when/why I would want or use this. And does "across browsers" mean browser windows/tabs in a single browser application or across browser applications. Does document refer to the DOM tree, or some external reference?
Definitely an interesting effort. I'm assuming this is a locally hosted virtual camera for desktop that relies on a host server to serve the lense data? Or does the server itself interpret the video or photo data?
I don't use snapchat, and not really familiar with the tech in question. Also, no idea what is shut down in terms of the app as a whole or features of.
Mainly asking, as the readme doesn't really answer what this does, or how it fits into the ecosystem/application(s) itself.
Also, thanks for slowing down on the posting, much appreciated.. and definitely an impressive effort all around.
Pretty nifty to see this. Material Design approach similar to how Bootstrap works in practice.
Would be nice to see component libraries based on this similar to ReactStrap, etc. In my mind, definitely thinking something for Yew could be really nice as well.
If you have a node codebase on Github, it will create pull requests against your codebase for your repository when there are security issues against a package you depend on. I'm not sure what you're expecting beyond that.
If you're using a good random number generator, crypto suitable, then UUID is decent and only really need to worry about it if you're creating over hundreds of thousands per second. UUIDv1 is slightly better, assuming you are on a system that supports the MAC address lookup as part of the generation, not the case for 'uuid' library's v1.
For what it's worth, the "subscribe" popover on every-single-page of your site is annoying as all hell... should store the decline in a cookie and not ask more than once a month.
Cool... haven't looked at the code, but thought it would be nice to do a CSV parser as a stream though... either sync or async... able to do for-of loops on the input itself... an inner parser yielding each column, then yielding the row as a set.
Either way, nice to see the progress on this.
The conversion seems to assume that the API in question supports callback or promise results... While many newer libraries will, plenty will be either or.