mirror of
https://akkoma.dev/AkkomaGang/akkoma.git
synced 2024-12-25 10:27:25 +00:00
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.ex | ||
anti_followbot_policy.ex | ||
anti_link_spam_policy.ex | ||
drop_policy.ex | ||
ensure_re_prepended.ex | ||
follow_bot_policy.ex | ||
force_bot_unlisted_policy.ex | ||
hashtag_policy.ex | ||
hellthread_policy.ex | ||
keyword_policy.ex | ||
media_proxy_warming_policy.ex | ||
mention_policy.ex | ||
no_empty_policy.ex | ||
no_op_policy.ex | ||
no_placeholder_text_policy.ex | ||
normalize_markup.ex | ||
object_age_policy.ex | ||
pipeline_filtering.ex | ||
policy.ex | ||
reject_non_public.ex | ||
simple_policy.ex | ||
steal_emoji_policy.ex | ||
subchain_policy.ex | ||
tag_policy.ex | ||
user_allow_list_policy.ex | ||
vocabulary_policy.ex |