Looks like a very useful thing for multibooting without worries on getting the correct ISO images.
Not sure how much problems this could cause with Windows ISO images since they would be easily uploaded/downloaded/shared by any IPFS client.
Let me understand the difference.
Till now, if you want to boot from - say - this or that version of Ubuntu you:
1) use a web browser and google to find the Ubuntu site
2) you find a download link for a suitable .iso
3) you (slowly) download it, saving it locally
4) you (hopefully) boot (quickly) to it, do the whatever prompted you to boot from it, and then go to bed
5) the day after you decide to boot again the Ubuntu, you select the locally stored .iso and boot (quickly) to it
In a hypothetical IPFS scenario:
1) use a web browser and google to find a site with the IPFS id/token/whatever
2) you find a IPFS id/token/whatever for a suitable .iso
3) you (slowly) download it, saving it locally
4) you (hopefully) boot (quickly) to it, do the whatever prompted you to boot from it, and then go to bed
5) the day after you decide to boot again the Ubuntu, you select the locally stored .iso and boot (quickly) to it
In the new revolutionary paradigm:
1) use a web browser and google to find a site where the IPFS files are listed
2) you find a download link for a suitable .iso
3) you download it (slowly) while at the same time booting to it, do the whatever prompted you to boot from it, and then go to bed
4) the day after you decide to boot again the Ubuntu, provided that you manage to find it locally, you quickly boot to it, more likely you loop to #1
As said I can understand the potentiality of a semi-de-centralized web, i.e. IPFS, it is only the actual IPFSpxe booting that seems to me like - besides the limited and experimental status of the thingy - like not particularly useful
Wonko