aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorgrunfink <grunfink@noreply.codeberg.org>2025-02-17 08:50:22 +0000
committergrunfink <grunfink@noreply.codeberg.org>2025-02-17 08:50:22 +0000
commitd40834edd1aa9d4fdb7cbcacb20edfe11734293f (patch)
tree6c20b996191c934fbb570ece5639fe7534a1b8ca
parent349d6603e4cd4a8baff1db718afa83413b0dae5f (diff)
parent0af0c28633f5c1788965861928edb8acd9f62ed2 (diff)
Merge pull request 'doc/snac8: elaborate regex blocking' (#305) from Menelmacar/snac2:master into master
Reviewed-on: https://codeberg.org/grunfink/snac2/pulls/305
-rw-r--r--doc/snac.85
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/snac.8 b/doc/snac.8
index 7a7352c..f1e5590 100644
--- a/doc/snac.8
+++ b/doc/snac.8
@@ -329,8 +329,9 @@ These weapons of mass destruction can be written into the
file in the server base directory, one per line; if this file exists,
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
+be rejected. Use lower case, the regex will be case insensitive by default.
+If you don't know about regular expressions, don't use this
+option (or learn about them inw 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