A new ignore_restriction_reasons parameter has appeared in the test AppConfig.
It now contains two restriction reasons that the client should ignore:
× sensitive
× porn
This is directly related to restrictionReason. If the reason in a restriction matches a value from ignore_restriction_reasons, the client ignores that restriction.
This means content with restrictionReason porn or sensitive, which was previously blocked at the client level, will likely no longer be blocked due to this restriction when this config is enabled.
@telelakel