Should Algolia provide a native cursor-based pagination token for geo-bounded searches?
Goal: Enable efficient retrieval of deep result pages when a geo‑bounding box is applied to an Algolia index. Constraint: Algolia’s current pagination uses offset‑based page and hitsPerPage (or offset / length ) parameters; the insideBoundingBox filter is applied before the offset/limit step, so each request recomputes the full filtered set and latency grows