Hashes in output

#### Version information:
N/A

#### Type:
Misc.

#### Severity:
Very Low
#### Description:
This is less of an issue and more of a question.
Should hashes being output by various commands be prefixed or not? As it is now, commands just output bare hashes like this:

```
>ipfs add -r -n --progress=false empty
added QmUNLLsPACCz1vLxQVkXqqLX5R1X345qqfHbsf67hvA3Nn empty
>ipfs key list -l
Qm............................................ self
```

would it be preferable to output something like this:

```
>ipfs add -r -n --progress=false empty
added /ipfs/QmUNLLsPACCz1vLxQVkXqqLX5R1X345qqfHbsf67hvA3Nn empty
>ipfs key list -l
/ipns/Qm............................................ self
```
or does that seem unnecessary?

I'm curious about the future where there are potentially even more types of hashes being mentioned by IPFS through various protocols or other somesuch. As well as the relation between other programs(maybe via pipes) and other IPFS commands. I know `ipfs get` will currently accept at least bare IPFS hashes(interpreted as IPFS paths), prefixed IPFS canonical paths, and prefixed IPNS paths; with IPNS paths the `/ipns/` prefix is required.

I'm unsure myself if this would be a beneficial feature (either by default or optionally), but I felt like it might be worth bringing up for consideration.