d6d838cbe8
To save on bandwith and avoid OOMs with large files. Ofc, this relies on the remote server (a) sending a content-length header and (b) being honest about the size. Common fedi servers seem to provide the header and (b) at least raises the required privilege of an malicious actor to a server infrastructure admin of an explicitly allowed host. A more complete defense which still works when faced with a malicious server requires changes in upstream Finch; see https://github.com/sneako/finch/issues/224 |
||
---|---|---|
.. | ||
activity_expiration_policy.ex | ||
anti_followbot_policy.ex | ||
anti_link_spam_policy.ex | ||
direct_message_disabled_policy.ex | ||
drop_policy.ex | ||
ensure_re_prepended.ex | ||
force_bot_unlisted_policy.ex | ||
hashtag_policy.ex | ||
hellthread_policy.ex | ||
inline_quote_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_newly_created_account_note_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 |