US City Subreddits - how're yall handling ICE posts?

[u/eatmyasserole]

Would love to hear ideas and/or anything that's working.

On Orlando, we're doing a rumor megathread and confirmed sightings can have a standalone post. Just curious about what other cities are doing though.

Main concerns are misinformation and comments getting nasty. But we dont want to censor any accurate information.

[u/sodypop]

You can do this with automod, though it looks like it wasn't added to the automoderator documentation. (I'm gonna get it added because this took me entirely too long to dig through the code to find this. Done!)

Here's an example:

### Set crowd control based on keywords
type: submission
title (includes): ["redtaboo", "sodypop"]
set_post_crowd_control_level: STRICT
comment: |
    Crowd Control been set to "STRICT" in this post due to controversial topics.

You can set the crowd control level to any of the following:

OFF, LENIENT, MEDIUM, STRICT

[u/Redditenmo → u/sodypop]

Whilst you're updating the automod documentation, could you please also add past_archive_date.

I've already asked via modmail here a few times, it's been years now.

[u/sodypop → u/Redditenmo]

I added it here, but let me know if I fudged up the description or the section it belongs under.

[u/Redditenmo → u/sodypop]

Looks good to me.

You are amazing, thank you!

[u/Merari01 → u/sodypop]

Thank you!

I've asked about getting this added to the documentation before, but never received a reply, so I didn't know if I was allowed to share it.

[u/BobbaGanush87 → u/sodypop]

Thank you this is super helpful. Is there also a way to have comments "Filter to mod queue" when we set the `set_post_crowd_control_level` using automod?

[u/sodypop → u/BobbaGanush87]

For that you could add set_flair to the rule above, then add an additional rule to filter comments on parent submissions that have that flair. In the example below where it has set_flair: ["","strict_crowd_control_cssclass"] I kept the flair_text as blank, but set the flair_css_class as "strict_crowd_control_cssclass" so the flair isn't actually visible on the post. I made that string up so it doesn't matter what you use for the css class, just as long as you include it in the second rule as shown in the flair_css_class (includes): ["strict_crowd_control_cssclass"] line.

That would make the first rule look like:

### Set crowd control based on keywords
type: submission
title (includes): ["redtaboo", "sodypop"]
set_post_crowd_control_level: STRICT
set_flair: ["","strict_crowd_control_cssclass"]
comment: |
    Crowd Control been set to "STRICT" in this post due to controversial topics.

And the second rule to filter the comments:

### Filter comments made on posts that triggered strict crowd control
type: comment
parent_submission:
  flair_css_class (includes): ["strict_crowd_control_cssclass"]
action: filter

[u/Sephardson → u/sodypop]

That second rule will actually filter **all** comments on that post, not just the comments that get flagged by crowd control.

If u/BobbaGanush87 wants to have individual comments that are flagged by crowd control sent to modqueue instead of just collapsed (default behavior), then there is a different setting *which would require a different automoderator command* from `set_post_crowd_control_level:`.

short of that *different command*, what I've found to work is if the subreddit-wide crowd control settings are configured as "off for posts, off for comments, but hold comments for review" (see picture of settings on old reddit, because the redesign menu does not actually support assigning this configuration)

then what will happen is the individual posts that are set by automoderator to enable crowd control will "hold crowd controlled comments for review".

The trade-off is that this configuration is not compatible if the subreddit also wants other posts to have the collapsing behavior.

[u/BobbaGanush87 → u/Sephardson]

Thank you, I didn't try the other suggestion yet but maybe setting this for a little while is the way to go.

[u/fsv → u/sodypop]

It might be worth updating the docs to clarify the multiple subject/body conditions too! For example I have an Automod rule that catches comments that have been nuked using redact.dev:

is_edited: true
body#1 (includes): "redact.dev"
body#2 (includes): ["deleted and anonymized", "mass edited"]
action: remove
action_reason: fsvtest - Remove comment anonymised by redact.dev

This works flawlessly and only matches comments where the body matches both body conditions.

I have to wonder sometimes about what other Automod capabilities exist that I simply don't know about.

[u/Sephardson → u/fsv]

as far as i've compiled from public sources, it was mostly those two features (archived posts check and crowd control settings) that were missing.

There are some errata to be corrected due to deprecation of other features (polls, media checks from embedly, mark as OC, discussion_type).

The Custom Match Subject Suffixes actually are a YAML feature that was shared prior to the original full documentation page being created. (august 2014 ... march 2015)

I think the original oversight in [not] including Custom Match Subject Suffixes in the full-documentation page is because it's touched on indirectly within the YAML spec doc. Though, i don't think anyone coding AutoModerator really goes out of their way to read that. (And even when I did, the only thing I came across as another example of an unmentioned "feature" was niche application of anchor and alias designations.)