STOP SLOP

Community filters,
with sources.

Inspect the list before you use it. Follow its changes on GitHub, check the evidence behind each entry, and keep your own exceptions.

STOP SLOP community list

Active rules
0
Candidate accounts inspected
0

We publish reviewed text matches here. An empty list has nothing to match and hides nothing.

Version
1
Updated
7 September 2026
Expires
6 December 2026
Inspect the list on GitHub

Starter included. More lists optional.

The extension installs a bundled starter list without an import. It currently has zero reviewed rules. Manage it under Settings → Advanced settings → Community lists, or choose Restore starter list if you removed it.

To receive daily updates from this separate published list, subscribe below.

Subscription URL

https://stopslop.tools/lists/community.json
  1. Open Settings → Advanced settings → Community lists.
  2. Open Add or import a list and paste this URL.
  3. Choose Subscribe to this publisher and allow access to stopslop.tools.

The extension checks for updates once per day. It sends no browsing history or post text with these requests. You choose whether matches hide content or stay visible.

Download list (JSON)

You can also import the downloaded file. File imports do not receive updates.

Where we look first

These searches contain reports of AI replies. We use them to find posts for review. A reporter’s claim alone does not establish AI authorship or justify blocking an account.

  1. AI replies reported by levelsio

    Awaiting inspection

    from:levelsio "blocked for ai reply"

    View source record

  2. AI replies reported across X

    Awaiting inspection

    "blocked for ai reply"

    View source record

We start with levelsio’s reports, then inspect the broader search. We keep distinct source citations when the same account appears in both.

From a report
to a rule

The current extension matches exact text fingerprints. It does not subscribe to an account blocklist or hide an account’s other posts.

  1. Find the original reply

    We open the conversation, identify the target post and author, and record the reporter’s words, post links and date.

  2. Review the evidence

    We require an author disclosure, platform disclosure or creation record tied to the target text. We check context and corrections, and keep unresolved reports out of the active list.

  3. Publish an eligible match

    We publish the text fingerprint with its evidence and expiry. You can inspect the rule, undo a hidden match or make a personal exception.

A community match expresses a filtering decision. It does not prove who wrote a post. Read the review policy.

Help us review a match.

Include the rule or post link, the correction you suggest and its supporting evidence.

Suggest a correction