When you say personal archives, I wonder a little about what we'd lose to filtering by people who know they're building an archive for posterity, versus people in the future rediscovering things that were safely forgotten for some long span of time.
At the delta of personal archives and projects like this, I imagine something a little like SETI or folding for home archival (is this just describing IPFS?), but I think one of the challenges is how we preserve the right kind of data. I did some spring-data-cleaning this year while building a new system, and one of my tasks was addressing duplicate files. This forced me to confront hundreds of gigabytes of VM images, snapshots, and massive piles of duplicate files from various installations of Ruby and Python.
But perhaps I underestimate the value of even the duplicate VM images or language installs. Perhaps, centuries hence, researchers will hopefully sift yottabyte of data looking for all of the dependencies to successfully resurrect applications they need to experience in order to understand references to them in well-stewarded tweets, posts, or articles.
As I've mentioned in another HN thread, I've been using youtube-dl to back up YouTube videos that are important to me since it's increasingly obvious that YouTube is merely a profit machine that would delete all of its user's videos in one fell swoop if they made an extra buck off it. I've also begun to back up some blogs that have vast mounts of great content, but I've found that HTTrack is... well, terrible. That's not to say it doesn't technically do its job, but it's way too aggressive. I wan't something that's easier to configure and can do a better job of taking "snapshots" of blog entries while blocking ads, javascripts, being able to resume properly if my power goes out, etc.