On Sat, Nov 4, 2017 at 8:05 PM, Scfith Riseup scfith@riseup.net wrote:
I wonder if there is an option to start to use ipfs ( https://ipfs.io/ ) or something like it to permanently and resiliently store items for posterity?
Bib users would need a client to avoid abusing inproxy. Though a client would offload from the bib.
There doesn't seem to be much of a data loss issue now, papers with broken links are still refindable and fixable if searched for hard enough, no?
But it might be said there's organization, maintenance, and wider audience utility issues with current bibs.
However - Once a better bib gets made, someone should consider pushing the dataset into IPFS, gnunet, storj, whatever. Object hash deduplicated systems among them are storage efficient, no matter how many people push the same thing. - Since most video presentation data exists only on youtube (aka: google) at their whim, I assign high risk of loss to that community corpus. It's a mess. All projects should be publishing local copies of theirs for mirroring. Also, it's hard to autodedupe down from youtube since they embed uniques per download / view. - Projects should self host, or at least dual home themselves, in their own overlays. for reference and other uses.