AngularJS services with promises best practice

I have an AngularJS application where I have services that calls $http resource and returns a promise that I resolve in my controller. Here's a sample of what I'm doing:

app.service('Blog', function($http, $q) {
  var deferred = $q.defer();
  $http.get('http://ift.tt/29D9jT4')
    .then(function(res) {
        // data massaging stuffs
      return deferred.resolve(res.data);
    }, function(err) {
        // may be some error message checking and beautifying error message
      return deferred.reject(err);
    });
    // chain if further more HTTP calls
  return deferred.promise;
});

But I could simply do the following as well:

app.service('Blog', function($http) {
  return $http.get('http://ift.tt/29D9jT4');
});

And then do the validation, error beautifying, chaining promises, etc. at the controller level.

My question is : Which is considered as 'best practice', if any, in terms of code resilience and flexibility? Or is there a better way to do it completely different than this ?