Rename 'ipfs object' to 'ipfs dag'

[wking]

@jbenet mentioned this in passing, and I thought I'd open a separate issue for it. Personally, I like ‘object’ better, since this command is about manipulating individual nodes and edges in the Merkle DAG. But I'm not clear on the motivation behind the rename, so maybe I'm missing something. For this issue:

• Why do we want the rename? Equivalently, how will we motivate this to users?
• How is the transition going to work? Will we support both forms through some deprecation period?

[jbenet]

on the motivation, some quotes from people i asked:

• "object is too generic, it's unclear"
• "ipfs dag is more clear-- you're manipulating the dag directly"
• "object is too much typing"
• "ipfs dag sounds cooler"'
• "ipfs dag makes more sense cause unixfs is also a set of objects, so ipfs object feels like like a parent of unixfs."

i agree with some of these but not all

---

on the transition, yeah probably support both forms and drop it before beta release.

---

btw, a similar thing will be to make ipfs files a thing, and have unixfs-specific cat, ls, get there. (still will want ipfs ls, ipfs cat, ipfs get in porcelain, but that may have to do with StackStream and so on, to be general enough to be global. not sure yet).

[daviddias]

Let's merge this thread into the main one #575