News for hackers. Stuff that matters.
Re:Launch HN: Flower (YC W23) – Train AI models on distribut... by danieljanes on Wednesday March 22, 2023 @11:24AM (#35262468)
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 approaches like Secure Aggregation can also help, depending on what kind of exposure your clients are concerned about.

My general take is that the best way to solve for transparency and trust is to tackle it on multiple layers of the stack.

Re:Launch HN: Flower (YC W23) – Train AI models on distribut... by jorgeili on Wednesday March 22, 2023 @11:57AM (#35263060)
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 distribut... by williamtrask on Wednesday March 22, 2023 @01:42PM (#35264508)
I can’t speak for Flower’s core dev roadmap, but PySyft is in the process of integrating Flower and some Secure Enclave options which would let you do this.

Congrats on the launch Flower team!

Re:Launch HN: Flower (YC W23) – Train AI models on distribut... by danieljanes on Wednesday March 22, 2023 @04:53PM (#35266955)
Thanks! We're huge fans of the work that PySyft is doing, and we're very supportive of the Flower PySyft integration.
Re:Launch HN: Flower (YC W23) – Train AI models on distribut... by danieljanes on Wednesday March 22, 2023 @01:45PM (#35264563)
Agreed that this is an interesting direction. The core Flower abstractions are "federated learning agnostic", which means that they can be used for different kinds of distributed/federated workloads, not just federated learning. We'll add examples for more approaches (like SMPC) in the future, we just don't have the bandwidth to do it immediately.
Re:Launch HN: Flower (YC W23) – Train AI models on distribut... by guites on Wednesday March 22, 2023 @12:58PM (#35263902)
A review steps sounds like a good idea. Our implementation involves very little interaction on the client side, besides setting up the datasets etc, so maybe a way to log information sent for later inspection would help.

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 distribut... by ngneer on Wednesday March 22, 2023 @02:52PM (#35265535)
Cool. I saw a proposal to use TEEs for secure aggregation. OpenFL uses Gramine for that. Not sure if that provides sufficient protection, really, but worth having on the radar.

https://arxiv.org/abs/2105.06413 https://openfl.readthedocs.io/en/latest/index.html https://gramineproject.io/

Re:Launch HN: Flower (YC W23) – Train AI models on distribut... by niclane7 on Wednesday March 22, 2023 @08:08PM (#35268852)
Flower has an agreement to develop interoperable components with OpenFL. This is part of the broader plan by Intel to work with a consortium of players (that includes Flower Labs) and have the output code sit with the Linux Foundation. Enabling TEE support within OpenFL for SA assessible to Flower users is precisely the type of opportunities we seek to make possible by working with Intel on this.

This is the official press release for those who are interesed: https://www.intel.com/content/www/us/en/newsroom/news/transi...

More broadly, in regards too your comment -- our current SA support does not require hardware support, which is what we targeted first, so that can be broadly adopted in many potential hosts of FL aggregation servers. It is suitable for most applications in need of privacy, although still requires certain assumptions to be met such as the number of nodes within a round, and other factors.