3 ms·

I'm considering using IPFS for storing metadata (in a similar way that DOI tracks publications) for accessioning genomics and wetlab microbiology data. The data

I'm considering using IPFS for storing metadata (in a similar way that DOI tracks publications) for accessioning genomics and wetlab microbiology data. The data will still be stored in the institution (b/c of data governance laws). The reason I really like that IPFS exists is bc it's a really convenient, mostly cheap and mostly reliable place to put stuff for quick access, even more than running my own server (ew), or paying for hosting and/or using Supabase, Firebase, etc. Basically using IPFS as a convenient k/v store. The data is still stored locally, but it's just much less convenient to access. Is anyone else doing this kind of setup?

kfarr 5y ago
To be clear, and perhaps why you’re being downvoted, IPFS stores nothing. It only guarantees that a given file will result in a certain hash id and that perhaps if there are servers available with assets that match that hash they might serve it. Hence the existence of pinning services which are paid platforms that do the actual hosting.
encryptluks2 5y ago
> The reason I really like that IPFS exists is bc it's a really convenient, mostly cheap and mostly reliable place to put stuff for quick access, even more than running my own server (ew), or paying for hosting and/or using Supabase, Firebase, etc. I think you're confusing pinning services or something else and it is actually quite a bit more expensive than Google Drive and other sync and storage solutions. IPFS doesn't store anything. You could just as easily setup Syncthing and it would perform the same functionality it you just want to address your files elsewhere.