Using user_context.read as a constraint on messages collection

So this user_context.read, which is returned when you make a call to the API, it doesn't have a value stored some where but is calculated on the fly? is that the problem?

I am beginning to think a) wait for aurora and b) if I was going to do this I would be better to do it in and endpoint so the performance hit was on the server side.