More prominently document MRF transparency and obfuscation
ci/woodpecker/pr/lint Pipeline failed Details
ci/woodpecker/pr/test unknown status Details
ci/woodpecker/pr/build-arm64 unknown status Details
ci/woodpecker/pr/build-amd64 unknown status Details
ci/woodpecker/pr/docs unknown status Details

And point to the cheat sheet for all other MRF policies
and their configuration details.
This commit is contained in:
Oneric 2024-01-28 23:12:59 +01:00
parent a352b04343
commit 48d95ac8d4
1 changed files with 26 additions and 0 deletions

View File

@ -61,6 +61,32 @@ config :pleroma, :mrf_simple,
The effects of MRF policies can be very drastic. It is important to use this functionality carefully. Always try to talk to an admin before writing an MRF policy concerning their instance.
## Hiding or Obfuscating Policies
You can opt out of publicly displaying all MRF policies or only hide or obfuscate selected domains.
To just hide everything set:
config :pleroma, :mrf,
transparency: false,
To hide or obfuscate only select entries, use:
config :pleroma, :mrf,
transparency_obfuscate_domains: ["", ""],
transparency_exclusions: [{"", "even a fragment is too spoopy for humans"}]
## More MRF Policies
See the [documentation cheatsheet](
for all available MRF policies and their options.
## Writing your own MRF Policy
As discussed above, the MRF system is a modular system that supports pluggable policies. This means that an admin may write a custom MRF policy in Elixir or any other language that runs on the Erlang VM, by specifying the module name in the `policies` config setting.