ps. just gonna second everyone else who's saying being able to edit out incorrect data is very important, otherwise people are gonna be weary of reading repos they aren't already familiar with.
ps. just gonna second everyone else who's saying being able to edit out incorrect data is very important, otherwise people are gonna be weary of reading repos they aren't already familiar with.
Coming in a little late, I've got a blog where I write about my tech findings in brazillian Portuguese. Mostly short write ups about how I research a new technology or topic (though there are some non tech related stuff here and there).
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.
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!
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 transferred to the centralized server?
Thanks a lot for the project.
edit: Just to clarify I am aware of differential privacy, I'm talking more on a "how to convince a medical institution that we are not sending its images over the network" level.
People that create vscode extensions and customize their workflows also share that spirit.
This would also make it harder for the first adventurers and gradually easier for late comers (more bodies/more loot)
I wonder how they compare?
Installing yabai involves some fishy tinkering with system integrity protection and giving screen recording permission for some functionalities, which doesn't bother me while at my personal PC but is kinda troublesome for a work machine.
Also, does it include some sort of workspace style virtual monitors? Like i3 does for linux.
In this case I would love if it allowed me to load custom workspaces on boot, which is such a pain to get working on i3[2]. (I'm not sure if yabai handles workspaces).
1. https://github.com/koekeishiya/yabai 2.https://wiki.archlinux.org/title/I3 section 5.3.2 for example
Not really a curated list, but I would welcome projects that filter the existing blogs into categories and etc.
https://guilhermegarcia.dev/brcrawl