160 karma · joined November 24, 2011
Re --check, I suppose the way to do that would be to download the file to disk, which --check requires as fair as I can tell. So I could download the file to disk, --check, and then remove it. I think most of these installs scripts are trying not to leave any artifacts around from install, other than the resulting binary.
I'll work through these suggestions. Appreciate it. Feel free to send a PR if you want.
For the here string I think that won't work because the file isn't being saved locally, it's just being piped (so $2 is a URL). I can't do the usual `shasum -c <<< "132e320edb0027470bfd836af8dadf174e4fee00 install.sh" which takes a local filename but not the file content. As far as I could tell anyway. I'll try it some more
This recent paper from Google combines FL with secure multi-party computation for “secure aggregation” to prevent the aggregate server from even seeing the gradients https://export.arxiv.org/abs/1902.01046
From https://www.tensorflow.org/federated
This is a very exiciting project that compliments other privacy-preserving machine learning techniques (PPML) in TensorFlow:
- Differential Privacy: https://github.com/tensorflow/privacy
- Secure Multi-Party Computation: https://github.com/mortendahl/tf-encrypted
- Confidential Computing (Trusted Execution Environments, Asylo, Intel SGX): https://github.com/dropoutlabs/tf-trusted
Firebase and Parse are both awesome products. They are really useful as application backends. GoInstant is focused completely on multi-user, real-time data. It compliments your backend, rather than replacing it. All of the decisions and concepts in our API are there to make it really easy to manage collaboration between users. It’s completely focused on the idea that you’re developing for a multi-user use case, either sync or async collaboration.
So, everything that happens with GoInstant involves other users. If you set data in our key/value store or send a message, other users are listening to that. Everything is wrapped in a pub/sub msg queue. When you connect or disconnect, other users know. Of course, you want to decide which users will know, so we organize groups of users into "rooms". We've built it from the ground-up with enterprise grade security, so auth, access control, and encryption are all rock solid.
As a quick example: if you were building a shopping cart, you would store the products in a backend somewhere (maybe Firebase, Parse, or a relational database). If you wanted to make that shopping cart multiplayer, i.e: multiple users shopping, adding products to the cart, and checking out together, you would use GoInstant for that. It's not that you couldn't accomplish it with other tech, it's that we're specifically built for multiplayer apps, so it's going to be intuitive. Who's looking at which product, what page they’re on, who added what to a cart, who's editing the quantity field: all of these features come out-of-the-box with GoInstant.
Hope this helps.