<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Scripting News - Latest Comments in Once again, future-safe archives (Scripting News)</title><link>http://scripting.disqus.com/</link><description></description><atom:link href="https://scripting.disqus.com/once_again_future_safe_archives_scripting_news/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 14 Oct 2009 21:42:14 -0000</lastBuildDate><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-20085274</link><description>&lt;p&gt;sam@online&lt;a href="http://-legacy.com" rel="nofollow noopener" target="_blank" title="-legacy.com"&gt;-legacy.com&lt;/a&gt; is&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mediadancer</dc:creator><pubDate>Wed, 14 Oct 2009 21:42:14 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19981112</link><description>&lt;p&gt;Have you looked through what the Library of Congress is up to? &lt;a href="http://www.digitalpreservation.gov" rel="nofollow noopener" target="_blank" title="www.digitalpreservation.gov"&gt;www.digitalpreservation.gov&lt;/a&gt; My guess is they would need a lot of support and funding to ramp the system up to the level you are talking about.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">EthanInDC</dc:creator><pubDate>Tue, 13 Oct 2009 13:22:39 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19945042</link><description>&lt;p&gt;Very much an interesting problem! I've run most of my online life from my own server, so I'm not tied to the whims of others.&lt;/p&gt;&lt;p&gt;I'm more of the opinion that the online "me" would be archived in some offline manner, since at some point I will be very much offline as well! The problem is of course how to best store it all? I agree the process very much matches what libraries, etc. have to deal with, and I think some key ideas might be:&lt;/p&gt;&lt;p&gt;1. Pick the best. This is very subjective, but what is Ansel Adams know for? Thousands of good images? Nope, just a few outstandingly great ones! What are the stand-out milestones of your life's work? With all our ways of getting metrics, this shouldn't be too hard to figure out.&lt;/p&gt;&lt;p&gt;2. Diversify. Not just putting content in various online locations, but also in various media. Figure out what you want to spend, and how you expect your loved ones to be able to get to it. Your guess is as good as mine, but hopefully one or more will work.&lt;/p&gt;&lt;p&gt;3. Share. There is such a thing as too much centralization. So often throughout history we find gems of historical documents squirreled away in someone's attic, even though the originals are gone. Get your results from step #2 into as many hands as are interested in having it.&lt;/p&gt;&lt;p&gt;I'll be watching with great interest to see what comes of an online solution!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">la5rocks</dc:creator><pubDate>Mon, 12 Oct 2009 23:39:25 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19928587</link><description>&lt;p&gt;Interesting we had a discussion at #twuttle about what happens to your online data and id after you die.&lt;/p&gt;&lt;p&gt;@fellowcreative has a project called deathbook which is aimed at asking questions in the UK about how people can ask for their online data and id to be handled after death - i.e delete/archived/split up and passed on etc etc.&lt;/p&gt;&lt;p&gt;ATM an email address may just get reused if you pass away perhaps passing on some data (think the twitter hack). What happens to your facebook account - should it stay around so people can still post to your wall or be removed asap as it it causing distress....&lt;/p&gt;&lt;p&gt; &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">rob ocallaghan</dc:creator><pubDate>Mon, 12 Oct 2009 18:01:46 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19925044</link><description>&lt;p&gt;Interesting discussion. Here are some 'crazy' ideas...&lt;br&gt;1. How about storing them on a  p2p network of computers dedicated to this purpose. Legal issues and abuse need to be controlled by some one. A Wikipedia like non-profit structure may last longer.&lt;/p&gt;&lt;p&gt;2. A few timecapsules with the information around the world and may be in the moon as well :-) [if everything fails ]&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AAfter Search</dc:creator><pubDate>Mon, 12 Oct 2009 16:46:02 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19895898</link><description>&lt;p&gt;how about nypl, they have a digital collection of picture of nyc 1900's. or the smithison who also have the tech knowlege to achive your goal. by the way what happen to ap pictures they do not apear any longer. my window to the rest of the world.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jimmason</dc:creator><pubDate>Mon, 12 Oct 2009 09:57:49 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19892761</link><description>&lt;p&gt;I would be more than willing to help with this. I'm always amazed at the timing of things I come across and how the big picture becomes fairly attainable by coincidence... I just registered on &lt;a href="http://Ancestry.com" rel="nofollow noopener" target="_blank" title="Ancestry.com"&gt;Ancestry.com&lt;/a&gt;.. and was thinking the same thing.. how will those after me know that I have a picture site, or a blog? Granted, I know that my daughter will know, but will she be interested in maintaining it, or having access to it etc? It's a very interesting paradox - I almost think it will be much easier to lose our collective histories over time if we're not careful... and how do these electronic archives get maintained? I believe in some ways it's even more critical figuring this problem out as we move away from paper in an almost permenant way.&lt;/p&gt;&lt;p&gt;I like the idea of academics being a part of it.. but what about an organization such as the Smithsonian, or something along those lines? Heck,dare I say an org like Google? While it has been mentioned that legal and financial are huge considerations - when it's all said and done, the underlying architecture, security, dr/coop and maintenance should be focal. And, while I kinda like the thought of my "knowledge" and life experience being immortal, it will only remain this way as long as someone is interested in having access to my stuff :)&lt;/p&gt;&lt;p&gt;So yes, I would be happy to volunteer - and while I'm not an tech-uber-geek (which I fondly call "TUGS", I've got a knack for planning needs based on user functionality liasoning with the TUGS, and I'm a phenominal organizer / scribe, albeit a modest one ;) &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">SassyPoppet</dc:creator><pubDate>Mon, 12 Oct 2009 09:03:50 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19886382</link><description>&lt;p&gt;Dave, what do you think will be the volume of data you want to archive and what timeframe do you expect?&lt;br&gt;1 TB for the next 50 years or something like 100 TB for 300 years. I think its the timeframe thats the real problem. Technology and financing set aside, there are a very few private projects that have such a stamina. &lt;br&gt;Perhaps its my european thinking but I can not imagine any private istitution that could asure an archive over such a long period.&lt;/p&gt;&lt;p&gt;Martin&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Martin Petersen</dc:creator><pubDate>Mon, 12 Oct 2009 04:22:01 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19867501</link><description>&lt;p&gt;This may not be the service Dave imagines, although I could misunderstand him:&lt;/p&gt;&lt;p&gt;I'm astonished nobody proposed national libraries. Most national libraries get their contents by legal deposit: two copies of every book or other publication (map, “something”) published must be given to the library.  There's no reason not to extend the concept of a (hopefully voluntary) legal deposit on web publications.&lt;/p&gt;&lt;p&gt;In fact the National Library of Germany is bound by law to exactly that: to collect and archive &lt;a href="http://www.d-nb.de/eng/netzpub/index.htm" rel="nofollow noopener" target="_blank" title="http://www.d-nb.de/eng/netzpub/index.htm"&gt;online publications&lt;/a&gt;. It's obiously not perfect (nothing could be) and they are still developing procedures and won't collect for some time but what I see look's promising: static content, strong metadata, persistent identifier and in the future automatical harvesting using open protocols of the Open Archive Initiative. If you just want to get archived and don't particulary care for continious service (like Dave seems to wish), this should be quite good enough.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim</dc:creator><pubDate>Sun, 11 Oct 2009 18:55:04 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19865943</link><description>&lt;p&gt;When we were planning Legacy Locker the idea of building a feature wherein users could invest in their digital archives came up numerous times.  Our fundamental flaw with the vision is the inability to guarantee anything into "forever".  We figured out all sorts of models around annuity structures that were "theoretically forever", but then there's a terms of service issue.  How can you guarantee it?  Bottom line is you can't...  Even if you start with a ridiculous amount of money, there's no "automatic forever" solution - human intervention is completely required for it to work.  And if you are going to involve people in the management/processing, we decided it wasn't a "tech" problem to solve...&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jeremy toeman</dc:creator><pubDate>Sun, 11 Oct 2009 17:58:16 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19864351</link><description>&lt;p&gt;Yes. Financial and legal. I will run the question by a friend who's a good wills &amp;amp; trusts attorney, see what ideas pop into his head.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stanley_Krute</dc:creator><pubDate>Sun, 11 Oct 2009 16:58:30 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19864250</link><description>&lt;p&gt;Having just read about Microsoft/Danger's massive loss of Sidekick data (&lt;a href="http://tr.im/BsU8)" rel="nofollow noopener" target="_blank" title="http://tr.im/BsU8)"&gt;http://tr.im/BsU8)&lt;/a&gt;, and considering Murphy's law, Twitter/GMail/Everyone else's occassional outages,  the idea of placing such priceless data  into centralized, coorporate hands is scary. (the information age has now lasted long enough that data is now as much of an heirloom as jewelry, art, furniture, and soon to be much much more commonplace an heirloom). And scary not primarily for privacy concerns, but for archival concerns.&lt;br&gt;  Dave, your post has touched on a huge issue. One that's only just emerging. The answer must be distributed, open source, and secure. Until such a solution exists, printing on archival paper is still the safest bet.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">elasticthreads</dc:creator><pubDate>Sun, 11 Oct 2009 16:53:25 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19864128</link><description>&lt;p&gt;A business model similar to a cemetery's might be one possible solution to support the costs indefinitely.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joe Moreno</dc:creator><pubDate>Sun, 11 Oct 2009 16:47:54 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19855917</link><description>&lt;p&gt;I'm totally down for formally archiving all materials I've ever produced and even merely recorded.  I've been uploading my avchd footage to EBS on Amazon, and I've been considering using Kaltura to provide a way to attach metadata to the 'stuff.'&lt;/p&gt;&lt;p&gt;Currently, Kaltura charges quite a bit for Akamai level storage of data.  I propose leveraging s3/cloudfront and &lt;a href="http://archive.org" rel="nofollow noopener" target="_blank" title="archive.org"&gt;archive.org&lt;/a&gt; to provide levels of access based upon public interest in the archived data.  Some sort of co-op should be formed to provide access to data while respecting non-commercial licensing (really any desired licensing) for the duration of copyright to gracefully preserve the value of works.&lt;/p&gt;&lt;p&gt;The easiest way I see of achieving this is by creating some sort of redirection engine (I'd rather not say url shortener) that drives multiple content delivery networks.  Redirect to &lt;a href="http://archive.org" rel="nofollow noopener" target="_blank" title="archive.org"&gt;archive.org&lt;/a&gt; when the data is accessed sporadically, redirect to ad supported(?) cloudfront for more popular data, redirect to akamai  for data that's too hot to handle.  any revenue generated goes toward supporting the network with net income distributed to the copyright owners or their descendants.  The system would of course garbage collect itself to keep cost of s3/akamai distribution as low as possible.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">papyromancer</dc:creator><pubDate>Sun, 11 Oct 2009 14:56:14 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19855715</link><description>&lt;p&gt;That's the most concise way to put it. "Endow their continued existence."&lt;/p&gt;&lt;p&gt;It's more of a financial thing than a technical thing, isn't it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Sun, 11 Oct 2009 14:46:47 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19855548</link><description>&lt;p&gt;Yes, this is important stuff to work on. I'm currently putting ~5k photos on the 'net each year. I'd love to find a way to endow their continued existence. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Stanley_Krute</dc:creator><pubDate>Sun, 11 Oct 2009 14:40:08 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19853263</link><description>&lt;p&gt;Yahoo!'s choosing to shut down Geocities to save money. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Phil Wolff</dc:creator><pubDate>Sun, 11 Oct 2009 13:21:12 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19833213</link><description>&lt;p&gt;You aren't the only thinking about it, for sure. About a year ago, I worked on a proof-of-concept app for &lt;a href="http://emortal.com/" rel="nofollow noopener" target="_blank" title="http://emortal.com/"&gt;http://emortal.com/&lt;/a&gt; (I don't know the current status of the venture).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">adean</dc:creator><pubDate>Sun, 11 Oct 2009 00:22:03 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19829044</link><description>&lt;p&gt;I wonder if you could use DNS as a distributed storage system.  I hadn't known about the TXT type of record until someone mentioned it here, but...and this may be a bit out there...if you gave a subdomain to every image (&lt;a href="http://pic1.domain.com" rel="nofollow noopener" target="_blank" title="pic1.domain.com"&gt;pic1.domain.com&lt;/a&gt;) you could then store base64 encoded binary data in sequential sub-subdomains of the image (&lt;a href="http://part1.pic1.domain.com" rel="nofollow noopener" target="_blank" title="part1.pic1.domain.com"&gt;part1.pic1.domain.com&lt;/a&gt;, &lt;a href="http://part2.pic1.domain.com" rel="nofollow noopener" target="_blank" title="part2.pic1.domain.com"&gt;part2.pic1.domain.com&lt;/a&gt;, ...).  Since DNS files are replicated all over the 'net, your data would be stored in servers, routers, and firewalls all over so long as your domain stayed active.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AndrewBurton</dc:creator><pubDate>Sat, 10 Oct 2009 23:05:36 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19825556</link><description>&lt;p&gt;You might want to check out what the &lt;a href="http://archiveteam.org" rel="nofollow noopener" target="_blank" title="http://archiveteam.org"&gt;Archive Team&lt;/a&gt; guys are doing. Right now they're all frantically downloading Geocities as fast as they can before Yahoo closes it forever, but that's just the current project.&lt;/p&gt;&lt;p&gt;They're essentially a hobbyist group, so hardly the well-established institution you're looking for (and I'm looking for too, frankly), but I'm sure you'd find their work interesting.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Zacqary Adam Xeper</dc:creator><pubDate>Sat, 10 Oct 2009 22:25:04 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19820671</link><description>&lt;p&gt;Out of curiosity, is there any reason that data needs to be kept out of specific jurisdictions, or is it just that it needs to not be in only one jurisdiction? If it's the latter, it'd be interesting to try to mirror across several hosts that are in completely separate jurisdictions. For static data, file synchronization problems should be just about nonexistent, since there can't be conflicting updates.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ravi Pinjala</dc:creator><pubDate>Sat, 10 Oct 2009 19:50:28 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19818596</link><description>&lt;p&gt;I have little idea how to pull this off but assuming the content is OK for public domain then a distributed "vault" seems a brilliant solution.&lt;/p&gt;&lt;p&gt;I suppose i've got a bit torrent type of idea in mind.   Trackers run which you can point personal domains too.  e.g. &lt;a href="http://vault.scripting.com" rel="nofollow noopener" target="_blank" title="vault.scripting.com"&gt;vault.scripting.com&lt;/a&gt;..  The tracker has a list of clients, each with a bandwidth rating,  which hold the content of &lt;a href="http://vault.scripting.com" rel="nofollow noopener" target="_blank" title="vault.scripting.com"&gt;vault.scripting.com&lt;/a&gt; and in turn request from that IP and this is delivered to the user.  The great thing here is that your content can be stored by many hundreds of different sources, big or small all over the world.&lt;/p&gt;&lt;p&gt;It's a rough thought but it negates the need of any specific individual / company.  I think there is a major flaw in my idea because you could potentially compromise content if you're a client but im sure there are CRC checks or some levels of encryption you could employ&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">James</dc:creator><pubDate>Sat, 10 Oct 2009 18:34:42 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19806017</link><description>&lt;p&gt;In as much as I usually leave things I do not understand to others, here is a site &lt;a href="http://bit.ly/16GOpl" rel="nofollow noopener" target="_blank" title="http://bit.ly/16GOpl"&gt;http://bit.ly/16GOpl&lt;/a&gt; that was probably onto a similar idea (albeit, different requirements). As an architect, we could define the requirements, outcomes and use cases. For actors, we have both those gone and those left. I think the biggest challenge is the legal side. The technology is probably a no-brainer. Interesting project anyhow. Keep me posted since I could provide 2cents.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Derik</dc:creator><pubDate>Sat, 10 Oct 2009 16:18:55 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19804444</link><description>&lt;p&gt;I think about this all the time.  I'm the beginning of the digital age,, and all my photos are on Flickr, SmugMug, whatever, and on various drives. Many of those are pieces of history, some of more interest than others.  But the job of curating everyone's archives is overwhelming, and perhaps cost prohibitive.  An issue like this has to be managed by a team of historians, philosophers, librarians, and technologists, and perhaps professional curators. Will there be a career one day called "life curator," a person you can hire to work with you on what's worth saving from your life? Like the co-author of your memoir?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">hardaway</dc:creator><pubDate>Sat, 10 Oct 2009 15:47:50 -0000</pubDate></item><item><title>Re: Once again, future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2009/10/10/onceAgainFuturesafeArchive.html#comment-19804326</link><description>&lt;p&gt;DV's a secure, time-released password/data escrow service I've been playing with launching for a few years. There is another competitor in the space but they're doing it all wrong and it's something I need so I'm building it. Just trying to find good, rock solid hosting out of the jurisdiction of as many governments as possible. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jason DeFillippo</dc:creator><pubDate>Sat, 10 Oct 2009 15:43:49 -0000</pubDate></item></channel></rss>