We could merge this, but it won't replace the jsonrpc function we
have in Fluidinfo because it customizes the onSuccess and onError
handlers so it can return a Deferred (which we need to make easily
make simultaneous network calls). My inclination is to leave this out
until we decide to add support for the comments API to fluidinfo.js
with explicit addComment, getComments, etc. methods.

+1. LGTM. Even if fluidinfo.com doesn't use this. It is useful for other clients or users.

@ntoll - what's your take on this? Should we merge it or shelve it? I have a slight preference for the former, but don't mind either way.

I think we should merge when we make the comment API available to the wider world (otherwise there's no point in having it in the library).

OK. I'll close the pull request. Thanks!