IPFS auto-updating

[jbenet]

(( related to #169 ))

One of the things that made Chrome (and now FF) an excellent web browser was the ability to stay at the edge of web developments: auto-updating.

This is not seen with command line tools, because hackers want their tools to be static and not change under their feet (unless asked to explicitly). This sounds like a good default to me in terms of major backwards-incompatible changes. But in terms of minor/patch (semver terminology), I wish these would happen automatically. Package managers like npm, and editors like sublime and atom have pushed the boundaries on this.

In addition to being self-updating, I think that IPFS should also be the first auto-updating filesystem. This will require quite a bit of work to make sure it is a positive UX, and not something annoying. This means:

• signed releases to ensure user safety
• ask user before updating (maybe a config opt).
• ability to turn it off (ipfs config version.autoupdate never or something)
• detailed ipfs update log, with the new entries being dumped out after an auto update.

Of course, auto-updating should be optional, with something like these options:

• never - do not auto-update
• patch - auto-update on new patch versions
• minor - auto-update on new minor (or patch) versions (Default)
• major - auto-update on any new version

[whyrusleeping]

somewhat related, i think we should have a logs dir at .go-ipfs/logs where various different logs will be stored fairly permanently

[jbenet]

Agreed. Added as #175