<@!808354231005872148> yep! makes sense. REST-base...
# spicedb
j
@User yep! makes sense. REST-based API that does it for you sounds like a reasonable solution. As I said, we're investigating what it would be like for frontend-based access, but the key issue is preventing not only miswriting, but also information leakage in general (not just what you can access, but what you can see to check what you can access)