Hey! Glad to see flower getting attention on hn. I've been working on a project for over a year that uses flower to train cv models on medical data. One aspect that we see being brought up again and again is how we can prove to our clients that no unnecessary data is being shared over the network. Do you have any tips on solving that particular problem? I.e. proving that no data apart from model weights are being tra…
Hi guites, Thank you! That is undoubtedly something relatable. We have it on the screen and plan to provide helpful material and presentations helping to convince stakeholders. If you are up for a call to share the specific challenges, we could ideate with you.
Launch HN: Flower (YC W23) – Train AI models on distributed or sensitive data
21–30 of 70 posts
Re: Launch HN: Flower (YC W23) – Train AI models on distributed or sensitive data
#22Hey! Glad to see flower getting attention on hn. I've been working on a project for over a year that uses flower to train cv models on medical data. One aspect that we see being brought up again and again is how we can prove to our clients that no unnecessary data is being shared over the network. Do you have any tips on solving that particular problem? I.e. proving that no data apart from model weights are being tra…
Thanks, glad you like it! One approach to increase the transparency on the client side (and build trust with the organization where the Flower clien is deployed) is to integrate a review step that asks the someone to confirm the update that gets send back to the server. On top of that, you should definitely use differential privacy. To quote Andrew Trask here: "friends don't let friends use FL without DP". Other appr…
I'll be looking into secure aggregation as I'm not fully aware of how it works. As of now we rely on differential privacy only.
Thanks!
Re: Launch HN: Flower (YC W23) – Train AI models on distributed or sensitive data
#23Earlier quoted context omitted.
Yes, we have developed modular and efficient secure aggregation and differential privacy solutions that can help people dial in the amount of protection they need. We have documented an early version of the secure aggregation here: https://flower.dev/docs/secagg.html Documentation and updates on both methods will be released soon.
I hate to ask a product comparison question, but why would I use this versus other projects like PySyft.
Re: Launch HN: Flower (YC W23) – Train AI models on distributed or sensitive data
#24Earlier quoted context omitted.
I hate to ask a product comparison question, but why would I use this versus other projects like PySyft.
Thanks for the question, very natural to ask. We are also fans of PySft. It offers support for a very wide range of privacy enhancing machine learning tools. But where Flower and PySft differ is in focus. Federated learning is difficult and requires many technical moving parts all working together (e.g., secure aggregation, differential privacy, scalable simulation, device deployments, integration with conventional M…
Re: Launch HN: Flower (YC W23) – Train AI models on distributed or sensitive data
#25Re: Launch HN: Flower (YC W23) – Train AI models on distributed or sensitive data
#26Earlier quoted context omitted.
Thanks, glad you like it! One approach to increase the transparency on the client side (and build trust with the organization where the Flower clien is deployed) is to integrate a review step that asks the someone to confirm the update that gets send back to the server. On top of that, you should definitely use differential privacy. To quote Andrew Trask here: "friends don't let friends use FL without DP". Other appr…
What about MPC + DP? Are you planning to integrate any SMPC algorithms on flower or do you find any limitations for not doing so. I'm trying to apply federated learning to the medical domain too and I'm trying to define the best "stack" that guarantees privacy and compliance with regulations like the GDPR
Congrats on the launch Flower team!
Re: Launch HN: Flower (YC W23) – Train AI models on distributed or sensitive data
#27Earlier quoted context omitted.
I hate to ask a product comparison question, but why would I use this versus other projects like PySyft.
Thanks for the question, very natural to ask. We are also fans of PySft. It offers support for a very wide range of privacy enhancing machine learning tools. But where Flower and PySft differ is in focus. Federated learning is difficult and requires many technical moving parts all working together (e.g., secure aggregation, differential privacy, scalable simulation, device deployments, integration with conventional M…
Re: Launch HN: Flower (YC W23) – Train AI models on distributed or sensitive data
#28Earlier quoted context omitted.
Thanks, glad you like it! One approach to increase the transparency on the client side (and build trust with the organization where the Flower clien is deployed) is to integrate a review step that asks the someone to confirm the update that gets send back to the server. On top of that, you should definitely use differential privacy. To quote Andrew Trask here: "friends don't let friends use FL without DP". Other appr…
What about MPC + DP? Are you planning to integrate any SMPC algorithms on flower or do you find any limitations for not doing so. I'm trying to apply federated learning to the medical domain too and I'm trying to define the best "stack" that guarantees privacy and compliance with regulations like the GDPR
Re: Launch HN: Flower (YC W23) – Train AI models on distributed or sensitive data
#29Congratulations! Really excited for you! I love how you found a niche, valuable problem, built a framework, and are seeing a lot of success. A question (and I'm far from an expert so let me know if the assumptions are wrong): It seems to me that the federated users have to be coordinated around timing for this to work. Otherwise this could take weeks/lots of slack messages for a single model to train. E.G. one team i…
Flower tries to automate this as much as it can. In cases where multiple organizations are involved, the workload can run in a fully automated manner if that's fine for all organizations. If a review step is required, that can be integrated (either on the client side or on the server side) - the availability of reviewers will then become the bottleneck for end-to-end latency.
In the long run, we will evolve the permissioning system to allow workloads to be automatically executed if they fall within pre-approved boundaries, or require manual review if they don't. Pre-approved boundaries could, for example, be used to configure a particular combination of models and hyperparemter ranges that are ok to run without additional (manual) approvals.