I toyed with that idea a few times, but this now strikes me as a problem for two reasons: 1. it's a security liability. some content i load in a web browser is

I toyed with that idea a few times, but this now strikes me as a problem for two reasons: 1. it's a security liability. some content i load in a web browser is private and I don't want to archive or duplicate it anywhere 2. it means a lot of crap. part of archiving content is curating what gets archived and what doesn't. i didn't touch on this in the article, but it's a key idea archivists need to address. for example, archiving the page I'm typing in right now (news.y.com/reply) makes no sense at all because it's solely dynamic content and would mean nothing when browsed later. So instead I send specific links I want to keep in my bookmarks system, as I mentioned in the article. It's far from ideal, but it's a much better compromised than archiving every time I visit my weather service page. ;)