not, it always succeeds, as with the case of github.

What is happening is that during the initial request, the lib tries to parse the response to extract 'next' and 'previous identifiers. Because they are invalid, nil is returned by the 'parse' method. The end result is that the readWithParams: method uses the 'default' parameter provider [limit and offset] as defined in the pipe configuration.

For cases of github and here reddit, this doesn't cause a problem, they always return the 'default' results even if invalid params are passed. For twitter test case though, an error occurs, that is, it doesn't understand the 'limit' and 'offset' params passes in the URL. 

'next' and 'previous' do succeed but they always return the same page. (and that's the reason for the comment here)