This is standard behavior with AngularJS. When you navigate away from a view, it’s controller is destroyed. When you come back to that same view, the controller is reinitialized. So, your $scope will get reset.
The solution to this is not necessarily local storage. Local storage is for maintaining info between starts of the entire app. Say on a phone the user closes your app and reopens it days later. Local Storage is great for that.
Local Storage can also solve your problem, but it is not required.
For your problem, you need to be using a service. The service will stay in memory for as long as the app is still open. On your feed view, your controller should ask the service for the data to put on the scope. The service should do the $http call to get the data. If service should keep the response in memory in a variable. When the user navigates to an article, the service will not lose the previously fetched info.
Once the user returns to the list, the controller will have no data. So, it should request it from the service again. Because the service kept the previous results in a variable, it will return them to the controller.
So, your paging issue should be solved.
Do that help?