The basic idea of Lifestreams is good for its metaphor but a lot of important implementation problems are ignored: ballooning storage from "clone" operations for every edit, ever increasing "view" query time, lack of a provenance back pointer. I think a lot of this can be solved with an SQL store, git style content hashes but there are still leaks to plug. One big one is how to resolve hashes given the content stores can move or disappear? Here I am assuming the system does not attempt to intern and reinvent git, github, dropbox, Maildir, etc? Then there is the huge footprint of how to collect inputs. Plugins for browser, email, git, perhaps even file system. It's all rather daunting to contemplate yet also feels like such a workable system is just within reach.