https://authzed.com logo
Join Discord
Powered by
Hi In 1254 the allowed characters in
# spicedb
c
Hi! In #1254 the allowed characters in ObjectID-s has been extended. Is there a plan to add support for more characters? Eg. dot (.) or % seem to be more-or-less trivial to me.
v
👋 no plans, what's the use-case?
c
host / domain names.
Also would make it possible to map any non-supported character in URL notation form. Eg. adding permission to 
authzed@spicedb.com
could be represented as 
authzed%40spicedb.com
or 
authzed%40spicedb%2Ecom
in spicedb so that clients can trivially encode/decode writes, checks and lookup results, human readability is kept and the possibility of unintentional collision is minimized (can also be enforced on client side).
v
we've been recommending folks to use base64 encoding when special characters are used. Readability can be addressed by decoding in the client side. I do think however URL Encoding could be useful, we would only need to add 
+
and 
%
characters (
.
would also be URL encoded).
If that'd be useful for you, feel free to open an issue!
for reference, this is the original issue where we discussing extending the regexps https://github.com/authzed/spicedb/issues/1210
y
@ciastko7568 my understanding is that there's a desire to use Roaring Bitmaps to implement a fast ACL filtering cache, and the larger the character set is, the worse that optimization will perform, so there's a desire to keep the character set as small as possible. i don't know if that's the primary motivation here tho.
4 Views
PreviousNext
Powered by