Hello ! I'm using SpiceDB for our members and owners "store" in our app. meaning, the full list of members and owner is only present in SpiceDB. when listing members or owners, we use LookupSubject. one of our spaces has a LOT of members (more than 300K) with the obvious error that this thows (message is more than 4Mo, and is expectedly slow) I tried to use the cursor approach (we basically want to list 1000 users, and if there is more, just indicate that and in the user listing, only enumerate that 1000 at a time, and disable sorting and other functionalities of the same kind and enable searching by filtering the users in db via names or email and then batch check in spiceDB to show or not the user in the list. BUT, when trying the cursor approach, I get a

UNIMPLEMENTED : concrete limit is not yet supported

so.... obviously, that doesn't work... I checked the issues on github, and did not find a ticket for that. Am I the first one to have this issue ? to move forward, I set up the readRelationship (the not optimised, not cached, very flexible lookup) but I'd like to avoid that. So is there an alternative ? and in the meantime, is there a way to check the amount of entities with a relation on an item to use lookup when small enough, and falling back to the readRelationships ?