After thinking about it some more, I actually think it would be useful to have access to `timestamp` here, so you should leave it as it is.

One use case I had in mind is determining if node is "stuck". If you have access to `timestamp` it makes it easier to do that. You can just periodically call this function and check if `timestamp` attribute has changed.

To make it more clear and useful, you should do two things:

* Update the docstring and document which keys the return ``dict`` will always contain
* Parse the timestamp and return a `datetime` object (`libcloud.utils.iso8601.parse_date` should do the trick)