Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think ipfs is very interesting, and will hopefully evolve to become a viable archive solution - but that'll only happen once you have a few serious organizations running their own redundant ipfs "intranet" storage networks, with geographical redundancy (or at least good local availability). Then we might see "archive peering" between such organizations.

The time horizon of "archival storage" probably starts at a hundred years - that will need some structure to have a likelihood of persisting for so long.



> The time horizon of "archival storage" probably starts at a hundred years - that will need some structure to have a likelihood of persisting for so long.

This reminds me of one of the principles of camlistore's data schema, which explicitly says that they made their schemas overly-explicit so that future digital archeologists can re-create the schema purely from examples[1].

It's a shame that camlistore feels more like a very long experiment over a polished and usable backup/archive system.

[1]: https://camlistore.org/doc/principles ; There used to be a more explicit explanation, but I couldn't find it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: