# Thirty years

2018-11-04

> Longaccess offered exactly that: users would pay in advance for 30 years of storage and upload any file they wanted to archive. Archives were client-side encrypted and immutable (once uploaded, no one can add, delete or update files).

> And each archive corresponded to a "certificate": a simple text file containing the archive ID and the random encryption key that had been used to encrypt the archive. We recommended that our users printed the archive certificate, to make sure technological obsolescence doesn’t make it unusable in the future (because if the certificate is lost, there is no way to recover the specific archive).

> Shutting down longaccess (cache)

Very close to what I was thinking the other day related to digital preservation. Documented failures are invaluable. Thank you so much!

Discovered via Simon Willison (cache).

Other articles in English: On caching links, Bushcraft retrospective, Into the Raft, Into the Bugs, Meritocracy crisis, The Seller, the Teacher and the Wise, Into the Good, Into the Mice, Into the Camp, Into the Wind, Into the Snow, Into the Cold, Async Python Frameworks, Distributed teams, Into the Wild, Without JavaScript, Inclusive Python, Micro-cultures and governance, Resilient Web and Tools, Bitcoin and energy, Team building, Inclusive developer, Cultural Intimacy, Tools and teams, Senior developer, Slow Data, Inclusive communities, Delivery and value(s), Collaboration debt, Communities and leadership, Specifications and APIs. Oh, and most of the 2018 thoughts.