Get Filtered Items - Pagination - Inability to "Go Back", Changes to Cursor

I am in the midst of some very exciting development using the Tape API and have just hit a roadblock that I don’t think can be moved past at the moment.

I am using the “Get Filtered Items” API call. This call uses a “cursor” variable. The cursor appears to be a JWT that contains a bunch of information, including the current position of the most recent API call so that, on the next call of the API, you can fetch more items by the limit from that position.

This is perfect if all you want to do is go forward, however, if you wanted to build a paginated table with 10 pages and have the user be able to go to page 5 whenever they wanted, this is impossible. The concept of the cursor seems very confusing anyway, and having a method more like Podio’s version of ‘limit’ and ‘offset’ makes more sense so you can drop the needle wherever you want.

Is there a chance that there could be a v2 API call provided that uses this functionality instead? People can continue to use the original but would have this additional option also when required.