summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authordefault <nobody@localhost>2024-03-16 16:32:13 +0100
committerdefault <nobody@localhost>2024-03-16 16:32:13 +0100
commitdf08b880d13e26e68826652bd7725f729828cc6e (patch)
tree976686a935ada22c977a1e78f9059c84a4892182 /doc
parentf58cb00adaad713af7f35eea149a0a52de6fd818 (diff)
Updated documentation.
Diffstat (limited to 'doc')
-rw-r--r--doc/snac.815
1 files changed, 8 insertions, 7 deletions
diff --git a/doc/snac.8 b/doc/snac.8
index 8e207ce..e28c6fd 100644
--- a/doc/snac.8
+++ b/doc/snac.8
@@ -251,13 +251,14 @@ From version 2.50, post content can be filtered out by regular expressions.
These weapons of mass destruction can be written into the
.Ic filter_reject.txt
file in the server base directory, one per line; if this file exists,
-all posts' content will be matched against these regexes, one by one, and
-any match will make the post to be rejected. If you don't know about regular
-expressions, don't use this option (or learn about them in some tutorial,
-there are gazillions of them out there), as you and your users may start
-missing posts. Also, given that every regular expression implementation
-supports a different set of features, consider reading the documentation
-about the one implemented in your system.
+all posts' content will be matched (after being stripped of HTML tags)
+against these regexes, one by one, and any match will make the post to
+be rejected. If you don't know about regular expressions, don't use this
+option (or learn about them in some tutorial, there are gazillions of
+them out there), as you and your users may start missing posts. Also,
+given that every regular expression implementation supports a different
+set of features, consider reading the documentation about the one
+implemented in your system.
.Ss ActivityPub Support
These are the following activities and objects that
.Nm