Hi @vlatko.s: the issue is marked with that priority primarily because it is still in the "needs discussion" state; once we have community buy-in on the feature, then it'll be reprioritized. I suspect at this point it is a matter of "when", not "if" we'll build it In terms of community involvement, we welcome involvement at any and all levels! The ideal is getting a design partner for the feature: someone who needs the feature, can work with us actively on the design, testing and feedback. We can schedule a call if you feel this might be something you're interesting in doing. > Has someone maybe successfully remodelled their domain for such use-cases (filtering a list + pagination) so that they can performantly use SpiceDB without Lookup Watch API & Tiger Cache Today this really depends on what information you have available and what your numbers look like: if you can filter in the database down to a reasonable working set, then you can issue Checks in parallel for the sorted results to filter out any that might be not visible to the current user. If, on the other hand, you know the set of results for an individual user will be smaller, but the database is very large, then you can issue a LookupResources API call to get the full set of objects the user can view, and then pass that to your database. The only scenario in which the current solutions don't work well today is if you have a very large number of resources that a user can view and a database that is itself very large: for that, the proposal is the anticipated long-term solution

Hey @Joey. Thanks for the detailed answer. Everything you wrote makes perfect sense. I'm definitely interested in seeing whether we can be a design partner for the feature as we would definitely try it out, test and provide feedback. Let me know if we can schedule a call to discuss this possibility.

definitely. https://authzed.com/contact has a a calendly for you to grab a time if you like