That’s where the user fields that you add in the UX are (they are actually a special kind of
user_custom_field
I see, that explains the variable naming. Thank you.
I think the /u/user.json endpoint only exposes public fields since it is publicly accessible. Due to the nature of the issue, i doubt people would want their NSFW preferences exposed on their user card. Thus i will look into using groups as a workaround first 