be careful using rm
in a loop and/or with variable arguments, things can go very wrong :)
when i'm writing a complicated command line involving rm
i often write and run it first with echo
in place of rm
just to be sure i am getting the results i expect. also when i re-run it actually using rm
, i tend to use the -v
option (which tells rm
to print what it is doing) to reassure myself that i've just deleted what i wanted to and nothing else.
Yes, something you're missing is that it was your (our) instance which removed the word from your comment. I believe the slur filters are effectively a combination of the configured filters on the writer's instance, the reader's instance, and the community's instance.
If you view this thread from other other users' instances (via the
link on their comments in the web view), you will see that the word which was removed from your comment is not removed from comments by users on some other instances (despite that it is also removed from their comments when viewed from our instance). HTH.
(imo false positives from the slur filter are annoying, but so are the people casually using slurs who are prevented from doing so by it; it's a tradeoff i don't feel strongly about. although i do think it would be much better if the writer-side version of it could notify users of the impending bowdlerization prior to posting.)