forked from AkkomaGang/akkoma
Hélène
8f140deb8f
* rejected_shortcodes is defined as a list of strings in the configuration description. As such, database-based configuration was led to handle those settings as strings, and not as the actually expected type, Regex. * This caused each message passing through this MRF, if a rejected shortcode was set and the emoji did not exist already on the instance, to fail federating, as an exception was raised, swiftly caught and mostly silenced. * This commit fixes the issue by introducing new behavior: strings are now handled as perfect matches for an emoji shortcode (meaning that if the emoji-to-be-pulled's shortcode is in the blacklist, it will be rejected), while still supporting Regex types as before. |
||
---|---|---|
.. | ||
activity_expiration_policy_test.exs | ||
anti_followbot_policy_test.exs | ||
anti_link_spam_policy_test.exs | ||
ensure_re_prepended_test.exs | ||
follow_bot_policy_test.exs | ||
force_bot_unlisted_policy_test.exs | ||
hashtag_policy_test.exs | ||
hellthread_policy_test.exs | ||
keyword_policy_test.exs | ||
media_proxy_warming_policy_test.exs | ||
mention_policy_test.exs | ||
no_empty_policy_test.exs | ||
no_placeholder_text_policy_test.exs | ||
normalize_markup_test.exs | ||
object_age_policy_test.exs | ||
reject_non_public_test.exs | ||
simple_policy_test.exs | ||
steal_emoji_policy_test.exs | ||
subchain_policy_test.exs | ||
tag_policy_test.exs | ||
user_allow_list_policy_test.exs | ||
vocabulary_policy_test.exs |