In this case how is the parameter for the API defined? Which cases would require more than 1 param?

Also, what are the benefits of this approach vs. the example I provided? In my version the array isn't needed, `resources` only needs to be specified once, and using the resource names as keys (to me) makes for a clearer grouping of config params. It also mirrors the hierarchy of the resources object in the context. As a refresher:

```js
$('#stream').paginate({
    resources: {
        "tumblr-stream": {
            // config
        }
    }
});
```

Something else I tried to achieve in my version was avoiding the use of the generic types listed in the README, rather I let the names of the parameters for each service express that, i.e. `max_tag_id` (Instagram), `offset` (Tumblr), `start-index` (YouTube). I think there's some merit to that approach, the keys adjacent that vary by the type of pagination are a bit vague though. With them I was trying to effectively provide a toolbox of "methods" to be used for getting and setting a value.