Summary

The recent change in scripts/people.py that excludes minimized comments/replies from the FastAPI People statistics is incomplete for top-level discussions.

The GraphQL query now fetches minimizedReason for each discussion node, but DiscussionsNode does not model that field and get_discussions_experts() never checks it before processing the discussion's comments/replies.

As a result, a minimized discussion can still contribute participants to the People stats through its non-minimized replies/comments, even though the thread itself has already been moderation-minimized.

Relevant recent change

• Commit: 0227991 (🔨 Exclude spam comments from statistics in scripts/people.py)

What I observed

In scripts/people.py:

1. The GraphQL query includes minimizedReason on the discussion node itself.
2. DiscussionsNode only defines:
   • number
   • author
   • title
   • createdAt
   • comments
3. get_discussions_experts() filters comment.minimizedReason and reply.minimizedReason, but never filters the discussion/thread itself.

That means the top-level moderation state is fetched but ignored.

Why this matters

If a discussion is minimized for spam / abuse / off-topic / duplicate reasons, the script still traverses that discussion and can count participants from replies/comments under that thread.

So the recent fix is only partial: it excludes minimized comments, but not minimized discussions.

Expected behavior

If a discussion itself is minimized for one of the excluded reasons, the script should skip the entire discussion when computing People statistics.

Possible fix

• Add minimizedReason: LowerStr | None = None to DiscussionsNode
• In get_discussions_experts(), skip processing when:

if discussion.minimizedReason in MINIMIZED_COMMENTS_REASONS_TO_EXCLUDE:
    continue

Extra note

Because the GraphQL query already requests the field, this looks like an accidental omission rather than a design decision.