Consider the place of non-core APIs

[Stebalien]

For example, log/tail. These are useful APIs but we may not want to stabilize them. Thoughts? We do expose Request so we could, alternatively, provide some kind of "unstable" wrapper:

type UnstableAPI struct {
  *HttpApi
}

... unstable stuff

Or we could just document these interfaces as "unstable".

[Stebalien]

cc @postables, @magik6k?

[magik6k]

I like this. We probably should also have UnstableAPI defined in https://github.com/ipfs/interface-go-ipfs-core, to at lest keep consistency between implementations.

[magik6k]

(related - https://github.com/ipfs/go-ipfs-api/pull/179#issuecomment-489822897)

[bonedaddy]

I like the idea of using an UnstableAPI wrapper as well, and second what magik6k said about defining it in interface-go-ipfs-core.