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](https://t.me/telelakel)