← Page history
Review report Review 1 of 2 · Sep 21, 2026

How the Sep 21, 2026 review of Reddit API protests by moderators/users went

An AI review agent read the finished page and checked it. It runs separately from the agent that wrote the page but is configured by the same maintainer, so it is not an outside review. Every finding it raised is listed below with what happened to it.

What happened, step by step

  1. Step 1

    Snapshot the page

    The reviewer sees only the page's text and its sources, not drafting notes or how it was written.

    Which version of the page was reviewed: not recorded.

  2. Step 2

    Checks, each run separately

    • Tone 1 finding
    • Unsupported claim 2 findings
    • Consistency 1 finding
    • Collection placement 1 finding

    Which checks ran was not recorded, so a check with no findings is not listed.

  3. Step 3

    Fix or explain

    Each finding is fixed, dismissed with a written reason, or left open.

    • Fixed5
  4. Result

    Nothing left open

    Every finding was fixed or dismissed with a written reason.

How this review ran

Reviewer model
Not recorded
Separation from the writer
A separate AI session that did not write the page and saw only the finished text. Same maintainer and AI model family as the writer.
Fixes made by
Not recorded
Approved by
Not recorded
Why it ran
Not recorded
Previous review
None — this was the first review

What this review does not do

It does not check every claim against its cited source, and a clean result is not a guarantee that the page is correct. Readers can report a problem on any page.

Report a problem on the page

All 5 findings

Quoted text is from the version of the page the reviewer saw.

Fixed · 5

  • FixedTone · low

    Before “highlighting tensions between platform governance and community power”

    After “Reddit moderators and users organize widespread protests against API pricing changes that also forced the shutdown of many third-party apps.”

    Why it was flagged

    This clause in the description is interpretive commentary rather than a factual statement of what happened — it frames the event's significance rather than describing an observable action.

    What was done

    Replaced the editorializing clause with a factual detail supported by the cited sources (third-party app shutdowns).

  • FixedUnsupported claim · low

    Before “archiveDate: "2026-09-02"”

    After “archiveDate: "2023-06-12"”

    Why it was flagged

    The archiveUrl encodes a Wayback Machine timestamp of 20230612014356 (12 June 2023), and the source notes confirm the archived capture read was from 12 June 2023, but archiveDate was set to 2026-09-02 (the accessDate convention) rather than the actual capture date.

    What was done

    Corrected archiveDate to 2023-06-12 to match the Wayback Machine capture timestamp encoded in archiveUrl and confirmed by the source notes.

  • FixedUnsupported claim · low

    Before “places: - title: "San Francisco" slug: "san-francisco"”

    After “places: - title: "Online" slug: "online"”

    Why it was flagged

    None of the four cited sources mention San Francisco or ground any part of the protest there; the API blackout was an online/distributed action already tagged separately as 'Online'.

    What was done

    Removed the unsupported San Francisco place tag; the event retains the 'Online' place tag which is supported by the sources.

  • FixedConsistency · low

    Before “movements: - title: "Open internet advocates" slug: "open-internet-advocates"”

    After “(movements field removed)”

    Why it was flagged

    The referenced movement's canonical name (Open Internet Movement frontmatter `name`) is 'Open Internet Movement', not 'Open internet advocates'. The timeline event's embedded title does not match the target entity's canonical name.

    What was done

    Resolved by removing the movements link entirely (see the related relevance-checker finding on this same reference) — the mismatched title no longer appears in the file.

  • FixedCollection placement · medium

    Before “movements: - title: "Open internet advocates" slug: "open-internet-advocates"”

    After “(movements field removed)”

    Why it was flagged

    Open Internet Movement scopes itself specifically to legislative/regulatory campaigns (SOPA/PIPA, FCC net neutrality) run by civil-society organizations like EFF. None of the four sources cited on this Reddit API-pricing timeline event mention EFF, net neutrality, SOPA/PIPA, or any legislative/regulatory angle — the Reddit blackout was a moderator/user response to a corporate pricing decision by Reddit, Inc., not a legislative-advocacy campaign. Tagging this event to open-internet-advocates groups it with an unrelated movement and is not supported by the cited sources.

    What was done

    Removed the movements field/link to open-internet-advocates. The movement page is explicitly scoped to legislative/regulatory campaigns (SOPA/PIPA, net neutrality repeal) with sourcing from EFF, FCC, and NY AG filings — none of which cover platform-pricing disputes. No better-fitting movement entity exists in the Movements pages for a single-platform pricing/API protest, so the reference was dropped rather than replaced.

This site is under active development. Content and features may change.