#FDroid prides itself with all the measures it takes not only to host great privacy respecting apps but also having a great client that's under the user control. The whole software ecosystem is built to be #decentralized, with multiple clients, repos and mirrors. This means we don't have visibility into how users chose to connect to our servers, be it directly, via a proxy, via Tor or some VPN.
#IPFS adds up on top of these, and we'd like to know: How do you feel about IPFS in F-Droid Client?
@fdroidorg IPFS proxy system is like having a very inefficient regular mirroring system. Keep it simple, add mirrors not software layers.
@esteban @fdroidorg In my humble opinion, IPFS is a good idea whose implementation needs a lot of work. One key benefit that it can provide now is a mirror where network observers cannot tell even what kinds of files are being downloaded, let alone that it is f-droid.org files. This is a nice privacy property for many use cases.
@eighthave @fdroidorg
This is not true unless you do full p2p embedding, for which you can just use magnet links and torrent/webtorrent instead which is way leaner and better.
In regular implementation you need a http proxy which sees every file and request in plain.
In the end the best is to add more regular mirrors and distribute the info, the IPFS extra layer is utterly useless as it's not web-native.